Changeset 197 for palm/trunk/DOC/app/chapter_4.1.html

Timestamp:

Sep 16, 2008 3:29:03 PM (16 years ago)

Author:

raasch

Message:

further adjustments for SGI and other small changes

File:

• palm/trunk/DOC/app/chapter_4.1.html (modified) (8 diffs)

palm/trunk/DOC/app/chapter_4.1.html

@@ -5510 +5510 @@
 
 
-    <tr>
+    <tr><td style="vertical-align: top;"><p><a name="humidity"></a><b>humidity</b></p></td><td style="vertical-align: top;">L</td><td style="vertical-align: top;"><i>.F.</i></td><td style="vertical-align: top;"><p>Parameter to
+switch on the prognostic equation for specific
+humidity q.<br>
+
+
+
+
+
+
+ </p>
+
+
+
+
+
+
+ 
+      
+      
+      
+      
+      
+      
+      <p>The initial vertical
+profile of q can be set via parameters <a href="chapter_4.1.html#q_surface">q_surface</a>, <a href="chapter_4.1.html#q_vertical_gradient">q_vertical_gradient</a>
+and <a href="chapter_4.1.html#q_vertical_gradient_level">q_vertical_gradient_level</a>.&nbsp;
+Boundary conditions can be set via <a href="chapter_4.1.html#q_surface_initial_change">q_surface_initial_change</a>
+and <a href="chapter_4.1.html#surface_waterflux">surface_waterflux</a>.<br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+If the condensation scheme is switched on (<a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
+= .TRUE.), q becomes the total liquid water content (sum of specific
+humidity and liquid water content).</td></tr><tr><td style="vertical-align: top;"><span style="font-weight: bold;"><a name="inflow_damping_height"></a>inflow_damping_height</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">from precursor run</span></td><td style="vertical-align: top;">Height below which the turbulence signal is used for turbulence recycling (in m).<br><br>In case of a turbulent inflow (see <a href="chapter_4.1.html#turbulent_inflow">turbulent_inflow</a>),
+this parameter defines the vertical thickness of the turbulent layer up
+to which the turbulence extracted at the recycling plane (see <a href="chapter_4.1.html#recycling_width">recycling_width</a>)
+shall be imposed to the inflow. Above this level the turbulence signal
+is linearly damped to zero. The transition range within which the
+signal falls to zero is given by the parameter <a href="chapter_4.1.html#inflow_damping_width">inflow_damping_width</a>.<br><br>By default, this height is set as the height of the convective boundary layer as calculated from a precursor run. See <a href="chapter_3.9.html">chapter 3.9</a> about proper settings for getting this CBL height from a precursor run. </td></tr><tr><td style="vertical-align: top;"><span style="font-weight: bold;"><a name="inflow_damping_width"></a>inflow_damping_width</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">0.1 * <a href="chapter_4.1.html#inflow_damping_height">inflow_damping</a></span><a href="chapter_4.1.html#inflow_damping_height"><br style="font-style: italic;"><span style="font-style: italic;">_height</span></a></td><td style="vertical-align: top;">Transition range within which the turbulance signal is damped to zero (in m).<br><br>See <a href="chapter_4.1.html#inflow_damping_height">inflow_damping_height</a> for explanation.</td></tr><tr>
 
 
@@ -6022 +6072 @@
 must be switched of in the equation of motion&nbsp; for w (this
 requires the user to comment out the call of <span style="font-family: monospace;">buoyancy</span> in the
-source code of <span style="font-family: monospace;">prognostic_equations.f90</span>).</p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Values may be
+source code of <span style="font-family: monospace;">prognostic_equations.f90</span>).</p></ul>
+
+
+
+
+
+
+ 
+      
+      
+      
+      
+      
+      
+      <p style="font-style: italic;">'read_data_for_recycling'</p><p style="font-style: normal; margin-left: 40px;">Here,
+3d-data from a precursor run are read by the initial (main) run. The
+precursor run is allowed to have a smaller domain along x and y
+compared with the main run. Also, different numbers of processors can
+be used for these two runs. Limitations are that the precursor run must
+use cyclic horizontal boundary conditions and that the subdomains of
+the main run must not be larger than the subdomains of the precursor
+run. If the total domain of the main run is larger than that of the precursor
+run, the domain is filled by cyclic repetition&nbsp;of the (cyclic)
+precursor data. This initialization method is recommended if a
+turbulent inflow is used (see <a href="chapter_4.1.html#turbulent_inflow">turbulent_inflow</a>). 3d-data must be made available to the run by activating an appropriate file connection statement for local file BININ. See <a href="chapter_3.9.html">chapter 3.9</a> for more details, where usage of a turbulent inflow is explained. </p><p style="font-style: normal;">Values may be
 combined, e.g. <b>initializing_actions</b> = <span style="font-style: italic;">'set_constant_profiles
 initialize_vortex'</span>, but the values of <span style="font-style: italic;">'set_constant_profiles'</span>,
@@ -6069 +6115 @@
       
       
-      <p style="font-style: italic;"> </p>
+      
 
 
@@ -6749 +6795 @@
 
 
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="humidity"></a><b>humidity</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>.F.</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Parameter to
-switch on the prognostic equation for specific
-humidity q.<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>The initial vertical
-profile of q can be set via parameters <a href="chapter_4.1.html#q_surface">q_surface</a>, <a href="chapter_4.1.html#q_vertical_gradient">q_vertical_gradient</a>
-and <a href="chapter_4.1.html#q_vertical_gradient_level">q_vertical_gradient_level</a>.&nbsp;
-Boundary conditions can be set via <a href="chapter_4.1.html#q_surface_initial_change">q_surface_initial_change</a>
-and <a href="chapter_4.1.html#surface_waterflux">surface_waterflux</a>.<br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-If the condensation scheme is switched on (<a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
-= .TRUE.), q becomes the total liquid water content (sum of specific
-humidity and liquid water content).</td>
-
-
-
-
-
-
- </tr>
+ 
 
 
@@ -7809 +7751 @@
 
 
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="npex"></a><b>npex</b></p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Number of processors
-along x-direction of the virtual
-processor
-net.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>For parallel runs, the total
-number of processors to be used
-is given by
-the <span style="font-weight: bold;">mrun</span>
-option <a href="http://www.muk.uni-hannover.de/software/mrun_beschreibung.html#Opt-X">-X</a>.
-By default, depending on the type of the parallel computer, PALM
-generates a 1d processor
-net (domain decomposition along x, <span style="font-weight: bold;">npey</span>
-= <span style="font-style: italic;">1</span>) or a
-2d-net (this is
-favored on machines with fast communication network). In case of a
-2d-net, it is tried to make it more or less square-shaped. If, for
-example, 16 processors are assigned (-X 16), a 4 * 4 processor net is
-generated (<span style="font-weight: bold;">npex</span>
-= <span style="font-style: italic;">4</span>, <span style="font-weight: bold;">npey</span>
-= <span style="font-style: italic;">4</span>).
-This choice is optimal for square total domains (<a href="#nx">nx</a>
-= <a href="#ny">ny</a>),
-since then the number of ghost points at the lateral boundarys of
-the subdomains is minimal. If <span style="font-weight: bold;">nx</span>
-nd <span style="font-weight: bold;">ny</span>
-differ extremely, the
-processor net should be manually adjusted using adequate values for <span style="font-weight: bold;">npex</span> and <span style="font-weight: bold;">npey</span>.&nbsp; </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p><b>Important:</b> The value of <span style="font-weight: bold;">npex</span> * <span style="font-weight: bold;">npey</span> must exactly
-correspond to the
-value assigned by the <span style="font-weight: bold;">mrun</span>-option
-      <tt>-X</tt>.
-Otherwise the model run will abort with a corresponding error
-message.&nbsp; <br>
-
-
-
-
-
-
-
-Additionally, the specification of <span style="font-weight: bold;">npex</span>
-and <span style="font-weight: bold;">npey</span>
-may of course
-override the default setting for the domain decomposition (1d or 2d)
-which may have a significant (negative) effect on the code performance.
-      </p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="npey"></a><b>npey</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Number of processors
-along y-direction of the virtual
-processor
-net.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>For further information see <a href="#npex">npex</a>.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
+    
+
+
+
+
+
+
+ 
 
 
@@ -11530 +11241 @@
 
 
- <tr>
+ <tr><td style="vertical-align: top;"><span style="font-weight: bold;"><a name="recycling_width"></a>recycling_width</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">0.1 * <a href="chapter_4.1.html#nx">nx</a> * <a href="chapter_4.1.html#dx">dx</a></span></td><td style="vertical-align: top;">Distance of the recycling plane from the inflow boundary (in m).<br><br>This
+parameter sets the horizontal extension (along the direction of the
+main flow) of the so-called recycling domain which is used to generate
+a turbulent inflow (see <a href="chapter_4.1.html#turbulent_inflow">turbulent_inflow</a>). <span style="font-weight: bold;">recycling_width</span> must be larger than the grid spacing (dx) and smaller than the length of the total domain (nx * dx).</td></tr><tr>
 
 
@@ -14376 +14090 @@
 = <a href="#scalar_advec">scalar_advec</a>
 = '<i>pw-scheme'</i>, <a href="chapter_4.2.html#psolver">psolver</a>
-= <i>'poisfft'</i> or '<i>poisfft_hybrid'</i>,
+/= <i>'sor</i><i>'</i>,
       <i>&nbsp;</i><a href="#alpha_surface">alpha_surface</a>
-= 0.0, <a href="#bc_lr">bc_lr</a> = <a href="#bc_ns">bc_ns</a> = <span style="font-style: italic;">'cyclic'</span>,&nbsp;<a style="" href="#galilei_transformation">galilei_transformation</a>
+= 0.0,<span style="font-style: italic;"></span>&nbsp;<a style="" href="#galilei_transformation">galilei_transformation</a>
 = <span style="font-style: italic;">.F.</span>,&nbsp;<a href="#cloud_physics">cloud_physics&nbsp;</a> = <span style="font-style: italic;">.F.</span>,&nbsp; <a href="#cloud_droplets">cloud_droplets</a> = <span style="font-style: italic;">.F.</span>,&nbsp;&nbsp;<a href="#humidity">humidity</a> = <span style="font-style: italic;">.F.</span>, and <a href="#prandtl_layer">prandtl_layer</a> = .T..<br>
 
@@ -14952 +14666 @@
 
 
-    <tr>
+    <tr><td style="vertical-align: top;"><a name="turbulent_inflow"></a><span style="font-weight: bold;">turbulent_inflow</span></td><td style="vertical-align: top;">L</td><td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td><td style="vertical-align: top;">Generates a turbulent inflow at side boundaries using a turbulence recycling method.<br><br>Turbulent inflow is realized using the turbulence recycling method from Lund et al. (1998, J. Comp. Phys., <span style="font-weight: bold;">140</span>, 233-258) modified by Kataoka and Mizuno (2002, Wind and Structures, <span style="font-weight: bold;">5</span>, 379-392).<br><br>A turbulent inflow requires Dirichlet conditions at the respective inflow boundary. <span style="font-weight: bold;">So far, a turbulent inflow is realized from the left (west) side only, i.e. </span><a style="font-weight: bold;" href="chapter_4.1.html#bc_lr">bc_lr</a><span style="font-weight: bold;">&nbsp;=</span><span style="font-style: italic; font-weight: bold;"> 'dirichlet/radiation'</span><span style="font-weight: bold;"> is required!</span><br><br>The initial (quasi-stationary) turbulence field should be generated by a precursor run and used by setting <a href="chapter_4.1.html#initializing_actions">initializing_actions</a> =<span style="font-style: italic;"> 'read_data_for_recycling'</span>.<br><br>The distance of the recycling plane from the inflow boundary can be set with parameter <a href="chapter_4.1.html#recycling_width">recycling_width</a>.
+The heigth above ground above which the turbulence signal is not used
+for recycling and the width of the layer within&nbsp;the magnitude of
+the turbulence signal is damped from 100% to 0% can be set with
+parameters <a href="chapter_4.1.html#inflow_damping_height">inflow_damping_height</a> and <a href="chapter_4.1.html#inflow_damping_width">inflow_damping_width</a>.<br><br>The detailed setup for a turbulent inflow is described in <a href="chapter_3.9.html">chapter 3.9</a>.</td></tr><tr>