Changeset 129 for palm/trunk/DOC/app


Ignore:
Timestamp:
Oct 30, 2007 12:12:24 PM (15 years ago)
Author:
letzel
Message:

prognostic_equations include the respective wall_*flux in the parameter list of
calls of diffusion_s. Same as before, only the values of wall_heatflux(0:4)
can be assigned. At present, wall_humidityflux, wall_qflux, wall_salinityflux,
wall_scalarflux are kept zero. diffusion_s uses the respective wall_*flux
instead of wall_heatflux. This update serves two purposes:

  • it avoids errors in calculations with humidity/scalar/salinity and prescribed

non-zero wall_heatflux,

  • it prepares PALM for a possible assignment of wall fluxes of

humidity/scalar/salinity in a future release.

Bugfix: assignment of fluxes at walls

Updates to documentation:
chapter_4.2.html#mode_dvrp
chapter_3.5.4.html#time_series

Default for mrun options -q and -n is "sla3" for lctit. Queues bes1 and bes2
removed. DOC/misc/Tsubame.html updated.

Modified default paths (/work/...) for lctit in .mrun.config.default

Location:
palm/trunk/DOC/app
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • palm/trunk/DOC/app/chapter_3.5.4.html

    r89 r129  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    22<html><head>
    3 <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM chapter 3.5.5</title> <meta name="GENERATOR" content="StarOffice 7 (Win32)"> <meta name="AUTHOR" content="Siegfried Raasch"> <meta name="CREATED" content="20040802;14050943"> <meta name="CHANGED" content="20041117;12180008"> <meta name="KEYWORDS" content="parallel LES model"> <style>
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM chapter 3.5.4</title> <meta name="GENERATOR" content="StarOffice 7 (Win32)"> <meta name="AUTHOR" content="Siegfried Raasch"> <meta name="CREATED" content="20040802;14050943"> <meta name="CHANGED" content="20041117;12180008"> <meta name="KEYWORDS" content="parallel LES model"> <style>
    44<!--
    55@page { size: 21cm 29.7cm }
     
    1313quantities which are not part of PALM's standard output. The basic user
    1414interface includes a number of subroutines which allow the calculation
    15 of user-defined quantities and output of these quantities as time series, (horizontally averaged) vertical profile, 2d cross
    16 section or 3d volume data. The respective subroutines
     15of user-defined quantities and output of these quantities as (horizontally averaged) <a href="#vertical_profiles">vertical profiles</a>, <a href="#time_series">time series</a>, <a href="#2D_and_3D">2d cross
     16section</a> or <a href="#2D_and_3D">3d volume data</a>. The respective subroutines
    1717contain sample code lines (written as comment lines) for defining, calculating and
    1818output of such quantities.<br><br>Output times, averaging intervals, etc. are steered by the same variables as used for the standard PALM output quantities, e.g. <a href="chapter_4.2.html#dt_data_output">dt_data_output</a>.<br><br>The
    1919rest of this chapter explains step-by-step how to modify/extend the
    20 default file user_interface.f90 in order to generate the respective output.<br><br><br><h4>Output of vertical profiles</h4>This example shows the output of the
     20default file user_interface.f90 in order to generate the respective output.<br><br><br><h4><a name="vertical_profiles"></a>Output of vertical profiles</h4>This example shows the output of the
    2121quantity "turbulent resolved-scale horizontal momentum flux" (u*v*). If more than one user-defined
    2222quantity shall be output, the following steps have to be carried out in the
     
    4949calculation is stored in array <span style="font-family: Courier New,Courier,monospace;">sums_l</span>.
    5050The second index of this array is the identification number of the
    51 profile which must match the one given in the previous step 2.</li></ol><br><h4>Output of timeseries</h4>still to be added<br>&nbsp;<br><h4><span style="font-weight: bold;">Output of 2d cross sections or 3d volume data</span></h4><br>This example shows the output of the
     51profile which must match the one given in the previous step 2.</li></ol><br><h4><a name="time_series"></a>Output of timeseries</h4>This example shows the output of  two time series for the absolut extremal values of the horizontal velocities <span style="font-style: italic;">u</span> and <span style="font-style: italic;">v</span>. If more than one user-defined
     52quantity shall be output, the following steps have to be carried out in the
     53same way for each of the quantities.<br><br><ol><li>For each time series quantity you have to give a label and a unit  (subroutine <a href="chapter_3.5.1.html#user_init">user_init</a>), which will be used for the NetCDF file. They must not contain more than seven characters. The value of <code>dots_num</code> has to be increased by the number of new time series quantities. Its old value has to be stored in <code>dots_num_palm</code>.<br><br><code>&nbsp;&nbsp;&nbsp; dots_label(dots_num<span style="color: rgb(255, 0, 0);">+1</span>) = '<span style="color: rgb(255, 0, 0);">abs_umx</span>'<br>&nbsp;&nbsp;&nbsp; dots_unit(dots_num<span style="color: rgb(255, 0, 0);">+1</span>)&nbsp; = '<span style="color: rgb(255, 0, 0);">m/s</span>'<br>&nbsp;&nbsp;&nbsp; dots_label(dots_num<span style="color: rgb(255, 0, 0);">+2</span>) = '<span style="color: rgb(255, 0, 0);">abs_vmx</span>'<br>&nbsp;&nbsp;&nbsp; dots_unit(dots_num<span style="color: rgb(255, 0, 0);">+2</span>)&nbsp; = '<span style="color: rgb(255, 0, 0);">m/s</span>'<br><br>&nbsp;&nbsp;&nbsp; dots_num_palm = dots_num<br>&nbsp;&nbsp;&nbsp; dots_num = dots_num <span style="color: rgb(255, 0, 0);">+ 2</span><br><br></code>Only those parts in <span style="color: rgb(255, 0, 0);">red</span> have to be adjusted by the user.<br><br></li><li>These quantities are&nbsp;calculated and output in subroutine <a href="chapter_3.5.1.html#user_statistics">user_statistics</a> for every statistic region <code>sr</code> defined by the user,&nbsp;but at least for the region <span style="font-style: italic;">"total domain"</span>:<br>&nbsp;<br><code>&nbsp;&nbsp;&nbsp; ts_value(dots_num_palm+1,sr) = ABS( u_max )<br>&nbsp;&nbsp;&nbsp; ts_value(dots_num_palm+2,sr) = ABS( v_max )<br></code>&nbsp;<br></li></ol><h4><span style="font-weight: bold;"><a name="2D_and_3D"></a>Output of 2d cross sections or 3d volume data</span></h4><br>This example shows the output of the
    5254quantity "square of the u-component" (<span style="font-weight: bold;">Note:</span> this quantity
    5355could of course easily be calculated from the u-component by
  • palm/trunk/DOC/app/chapter_4.2.html

    r127 r129  
    1068210682(cross sections), and <span style="font-style: italic;">'particles'</span>.
    1068310683Within the strings the hash character ("#") has to be replaced by a
    10684 digit &le;9. Up to 10 objects
    10685 can be assigned at the same time, e.g. :&nbsp; </p>
     10684digit 1&le;#&le;9. Up to 10 objects
     10685can be assigned at the same time, e.g.:&nbsp; </p>
    1068610686
    1068710687
     
    1070010700      <p>In this
    1070110701case one isosurface, two cross sections, and particles
    10702 will be created. The quantities for which an isosurface are to be
     10702will be created. The quantities for which isosurfaces or cross sections are to be
    1070310703created have to be selected with
    10704 the parameter <a href="#data_output">data_output</a>,
    10705 those for cross sections with <a href="#data_output">data_output</a>
    10706 (<span style="font-weight: bold;">data_output</span>
     10704the parameter <a href="#data_output">data_output</a> (<span style="font-weight: bold;">data_output</span>
    1070710705also determines the
    10708 orientation of the cross section, thus xy, xz, or yz). Since for <span style="font-weight: bold;">data_output</span> and <span style="font-weight: bold;">data_output</span> lists of
     10706orientation of the cross section, thus xy, xz, or yz). Since for <span style="font-weight: bold;">data_output</span> <span style="font-weight: bold;"></span>lists of
    1070910707variables may be
    1071010708assigned, the digit at the end of the <span style="font-weight: bold;">mode_dvrp</span>-string
    1071110709selects the quantity, which is given
    1071210710at the respective position in the respective list (e.g. <span style="font-style: italic;">'isosurface2'</span>
    10713 selects the quantity
    10714 given in the second position of <span style="font-weight: bold;">data_output</span>).
    10715 If e.g. <span style="font-weight: bold;">data_output</span>
    10716 and <span style="font-weight: bold;">data_output</span>
    10717 are assigned as <b>data_output</b> = <span style="font-style: italic;">'u_xy'</span><i>,
    10718 'w_xz', 'v_yz'</i> and <b>data_output</b> = <span style="font-style: italic;">'pt'</span><i>,
    10719 'u', 'w' </i>are
    10720 indicated, then - assuming the above assignment of <span style="font-weight: bold;">mode_dvrp</span> - an
     10711selects the second 3D quantity
     10712of <span style="font-weight: bold;">data_output</span>,  <span style="font-style: italic;">'slicer1'</span> selects the first 2D quantity
     10713of <span style="font-weight: bold;">data_output</span>).
     10714If e.g. <span style="font-weight: bold;">data_output</span> is assigned as <b>data_output</b> = <span style="font-style: italic;">'u_xy'</span><i>,
     10715'w_xz', 'v_yz'</i>, <span style="font-style: italic;">'pt'</span><i>,
     10716'u', 'w'</i>, then - assuming the above assignment of <span style="font-weight: bold;">mode_dvrp</span> - an
    1072110717isosurface of u, a
    1072210718horizontal cross section of u and
    10723 a vertical cross section (xz) of w is created. For locations of the
     10719a vertical cross section (xz) of w are created. For locations of the
    1072410720cross sections see <a href="#data_output">data_output</a>.
    1072510721The theshold value for which the isosurface is
     
    1073810734
    1073910735
    10740  </p>
    10741 
    10742 
    10743 
    10744      
    10745      
    10746       <p>The vertical extension of the displayed domain is given by <a href="#nz_do3d">nz_do3d</a>. </p>
    10747 
    10748 
    10749  
    10750      
    10751      
    10752       <p><b>Assignments
     10736 </p><p><b>Assignments
    1075310737of mode_dvrp must correspond to those of data_output
    1075410738and
    10755 data_output! </b>If e.g. <b>data_output</b> = <span style="font-style: italic;">'pt_xy'</span>
    10756 and <b>data_output</b>
    10757 = 'w'<i> </i>was set, then only the digit "1" is allowed
     10739data_output! </b>If e.g. <b>data_output</b> = <span style="font-style: italic;">'pt_xy'</span>,<span style="font-style: italic;"> 'w'</span><i> </i>was set, then only the digit "1" is allowed
    1075810740for <b>mode_dvrp</b>,
    1075910741thus <span style="font-style: italic;">'isosurface1'</span>
    10760 and/or <span style="font-style: italic;">'slicer1'</span><i>.</i>&nbsp;
     10742and/or <span style="font-style: italic;">'slicer1'</span><i>.</i>
    1076110743      </p>
    1076210744
Note: See TracChangeset for help on using the changeset viewer.