Changeset 129 for palm/trunk/DOC
- Timestamp:
- Oct 30, 2007 12:12:24 PM (17 years ago)
- Location:
- palm/trunk/DOC
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
palm/trunk/DOC/app/chapter_3.5.4.html
r89 r129 1 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> 2 2 <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> 4 4 <!-- 5 5 @page { size: 21cm 29.7cm } … … 13 13 quantities which are not part of PALM's standard output. The basic user 14 14 interface 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 cross16 section or 3d volume data. The respective subroutines15 of 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 16 section</a> or <a href="#2D_and_3D">3d volume data</a>. The respective subroutines 17 17 contain sample code lines (written as comment lines) for defining, calculating and 18 18 output 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 19 19 rest 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 the20 default 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 21 21 quantity "turbulent resolved-scale horizontal momentum flux" (u*v*). If more than one user-defined 22 22 quantity shall be output, the following steps have to be carried out in the … … 49 49 calculation is stored in array <span style="font-family: Courier New,Courier,monospace;">sums_l</span>. 50 50 The 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> <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 51 profile 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 52 quantity shall be output, the following steps have to be carried out in the 53 same 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> dots_label(dots_num<span style="color: rgb(255, 0, 0);">+1</span>) = '<span style="color: rgb(255, 0, 0);">abs_umx</span>'<br> dots_unit(dots_num<span style="color: rgb(255, 0, 0);">+1</span>) = '<span style="color: rgb(255, 0, 0);">m/s</span>'<br> dots_label(dots_num<span style="color: rgb(255, 0, 0);">+2</span>) = '<span style="color: rgb(255, 0, 0);">abs_vmx</span>'<br> dots_unit(dots_num<span style="color: rgb(255, 0, 0);">+2</span>) = '<span style="color: rgb(255, 0, 0);">m/s</span>'<br><br> dots_num_palm = dots_num<br> 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 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, but at least for the region <span style="font-style: italic;">"total domain"</span>:<br> <br><code> ts_value(dots_num_palm+1,sr) = ABS( u_max )<br> ts_value(dots_num_palm+2,sr) = ABS( v_max )<br></code> <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 52 54 quantity "square of the u-component" (<span style="font-weight: bold;">Note:</span> this quantity 53 55 could of course easily be calculated from the u-component by -
palm/trunk/DOC/app/chapter_4.2.html
r127 r129 10682 10682 (cross sections), and <span style="font-style: italic;">'particles'</span>. 10683 10683 Within the strings the hash character ("#") has to be replaced by a 10684 digit ≤9. Up to 10 objects10685 can be assigned at the same time, e.g. 10684 digit 1≤#≤9. Up to 10 objects 10685 can be assigned at the same time, e.g.: </p> 10686 10686 10687 10687 … … 10700 10700 <p>In this 10701 10701 case one isosurface, two cross sections, and particles 10702 will be created. The quantities for which an isosurfaceare to be10702 will be created. The quantities for which isosurfaces or cross sections are to be 10703 10703 created 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> 10704 the parameter <a href="#data_output">data_output</a> (<span style="font-weight: bold;">data_output</span> 10707 10705 also 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 of10706 orientation 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 10709 10707 variables may be 10710 10708 assigned, the digit at the end of the <span style="font-weight: bold;">mode_dvrp</span>-string 10711 10709 selects the quantity, which is given 10712 10710 at 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 10711 selects the second 3D quantity 10712 of <span style="font-weight: bold;">data_output</span>, <span style="font-style: italic;">'slicer1'</span> selects the first 2D quantity 10713 of <span style="font-weight: bold;">data_output</span>). 10714 If 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 10721 10717 isosurface of u, a 10722 10718 horizontal cross section of u and 10723 a vertical cross section (xz) of w iscreated. For locations of the10719 a vertical cross section (xz) of w are created. For locations of the 10724 10720 cross sections see <a href="#data_output">data_output</a>. 10725 10721 The theshold value for which the isosurface is … … 10738 10734 10739 10735 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 10753 10737 of mode_dvrp must correspond to those of data_output 10754 10738 and 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 10739 data_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 10758 10740 for <b>mode_dvrp</b>, 10759 10741 thus <span style="font-style: italic;">'isosurface1'</span> 10760 and/or <span style="font-style: italic;">'slicer1'</span><i>.</i> 10742 and/or <span style="font-style: italic;">'slicer1'</span><i>.</i> 10761 10743 </p> 10762 10744 -
palm/trunk/DOC/misc/Tsubame.html
r127 r129 42 42 options are available:</p><table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"><tbody><tr><td><span style="font-weight: bold;">mrun</span> option</td><td>explanation</td><td>possible 43 43 values</td><td>default value</td></tr><tr><td><code>-q</code></td><td>queue 44 name for main job</td><td>novice, bes1, bes2,sla1, sla2,45 sla3, RAM64GB, RAM128GB</td><td> novice</td></tr><tr><td><code>-n</code></td><td>queue44 name for main job</td><td>novice, sla1, sla2, 45 sla3, RAM64GB, RAM128GB</td><td>sla3</td></tr><tr><td><code>-n</code></td><td>queue 46 46 name for "submitting job" (always runs on 1 PE only)</td><td>novice, 47 sla1, sla2, sla3</td><td> novice</td></tr><tr><td><code>-g</code></td><td>group number</td><td>name of the N1GE_GROUP that is required to utilize the bes or sla queues</td><td>none</td></tr></tbody></table><p>Note that the default value "novice" of the47 sla1, sla2, sla3</td><td>sla3</td></tr><tr><td><code>-g</code></td><td>group number</td><td>name of the N1GE_GROUP that is required to utilize the bes or sla queues</td><td>none</td></tr></tbody></table><p>Note that the default value "sla3" of the 48 48 <span style="font-weight: bold;">mrun</span> option <code>-q</code> may 49 only be suitable for code development, debugging or short test runs. 50 Production runs should use the respective production queues(see <a href="http://www.gsic.titech.ac.jp/%7Eccwww/tgc/q_e.html">http://www.gsic.titech.ac.jp/~ccwww/tgc/q_e.html</a> for details).</p><p>The <span style="font-weight: bold;">mrun</span> option <code><span style="font-family: Courier New,Courier,monospace;">-t</span></code> 49 not always be the best choice. For code development, debugging or short 50 test runs the value "novice" for both options may be suitable. 51 Production runs should use the respective production queues (see <a href="http://www.gsic.titech.ac.jp/%7Eccwww/tgc/q_e.html">http://www.gsic.titech.ac.jp/~ccwww/tgc/q_e.html</a> for details). </p><p>The computer center advised us that due to restrictions of the batch system the value "novice" should not be mixed with the other queues. Please specify either a combination of sla<span style="font-style: italic;">n</span> for <code>-n</code> and sla<span style="font-style: italic;">n</span> or RAM<span style="font-style: italic;">*</span> for <code>-q</code>, or specify the combination "novice" + "novice".<span style="font-style: italic;"></span></p><p>The <span style="font-weight: bold;">mrun</span> option <code><span style="font-family: Courier New,Courier,monospace;">-t</span></code> 51 52 contains the CPU time demand for the main job in s which will be 52 53 automatically converted into min for the <span style="font-weight: bold;">n1ge</span> command. The
Note: See TracChangeset
for help on using the changeset viewer.