| [5] | 1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
|---|
| [62] | 2 | <html><head> |
|---|
| 3 | <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM |
|---|
| 4 | chapter 4.5.5</title> <meta name="GENERATOR" content="StarOffice 7 (Win32)"> <meta name="AUTHOR" content="Siegfried Raasch"> <meta name="CREATED" content="20041027;13094394"> <meta name="CHANGED" content="20041117;11561956"> <meta name="KEYWORDS" content="parallel LES model"> <style> |
|---|
| 5 | <!-- |
|---|
| 6 | @page { size: 21cm 29.7cm } |
|---|
| 7 | --> |
|---|
| 8 | </style></head> |
|---|
| 9 | |
|---|
| 10 | <body style="direction: ltr;" lang="en-US"><h4 style="line-height: 100%;"><font size="4">4.5.5 |
|---|
| 11 | Plots of 3d volume |
|---|
| [5] | 12 | data with AVS</font></h4> |
|---|
| [62] | 13 | <p style="line-height: 100%;">In contrast to the plot |
|---|
| 14 | output described |
|---|
| [5] | 15 | so far, which can be handled more or less automatically, the creation |
|---|
| 16 | of |
|---|
| [62] | 17 | plots with <b>AVS</b> requires programming a so-called |
|---|
| 18 | network by |
|---|
| 19 | using the <span style="font-weight: bold;">AVS</span> |
|---|
| 20 | network editor |
|---|
| [5] | 21 | to design the plot |
|---|
| 22 | layout. Details are not given here because it is assumed that the user |
|---|
| 23 | is familiar with <b>AVS</b>. </p> |
|---|
| [62] | 24 | <p style="line-height: 100%;"><font color="#000000">Output |
|---|
| 25 | of 3d volume |
|---|
| [5] | 26 | data requires to set at least two parameters: </font>first, the |
|---|
| 27 | temporal |
|---|
| [62] | 28 | interval of the output time (run parameter <a href="chapter_4.2.html#dt_do3d"><u>dt_do3d)</u></a><span style="text-decoration: none;"> |
|---|
| [5] | 29 | and second<span style="text-decoration: none;"></span> |
|---|
| [62] | 30 | the names of the quantities for which volume data output is wanted</span><span style="text-decoration: none;"><span style="text-decoration: none;"> (<a href="chapter_4.2.html#data_output">data_output</a></span></span>).<font color="#000000"> </font><font color="#000000"><span style="text-decoration: none;"></span></font><font color="#000000"><span style="text-decoration: none;"></span><span style="text-decoration: none;"></span></font><font color="#800000"> </font>The |
|---|
| [5] | 31 | parameter <a href="chapter_4.2.html#nz_do3d">nz_do3d</a> |
|---|
| 32 | can be used to limit data output in vertical direction up to a certain |
|---|
| 33 | grid |
|---|
| [62] | 34 | point. If no value has been assigned to <b>data_output</b> |
|---|
| 35 | or |
|---|
| [5] | 36 | if the value given for <b>dt_do3d </b>is |
|---|
| 37 | larger than the simulated time (see <a href="chapter_4.1.html#end_time">end_time</a>), |
|---|
| [62] | 38 | <b>then there will be no output!</b> By default, data is |
|---|
| 39 | output in |
|---|
| [5] | 40 | 32-bit real format. Alternatively, for parallel runs, data can also be |
|---|
| 41 | output in compressed format using 32-bit integers. This yields |
|---|
| 42 | a loss of accuracy, but the file size is clearly reduced. The output of |
|---|
| [62] | 43 | compressed data is described in more detail in <a href="chapter_4.5.6.html">chapter |
|---|
| [5] | 44 | 4.5.6</a>. </p> |
|---|
| 45 | <p style="line-height: 100%;">Data, whether compressed or |
|---|
| [62] | 46 | uncompressed, is output into the local file <a href="chapter_3.4.html#PLOT3D_DATA">PLOT3D_DATA</a>. |
|---|
| [5] | 47 | This file must be linked with a permanent file by |
|---|
| [62] | 48 | using a file connection statement in the <b>mrun</b> |
|---|
| 49 | configuration |
|---|
| [5] | 50 | file (see e.g. <a href="chapter_3.2.html">chapter |
|---|
| 51 | 3.2</a>). At the end of the run the local file is copied to this |
|---|
| 52 | file. Additionally, mrun creates a file containing some coordinate |
|---|
| 53 | informations about the 3d data, which also has to be copied. The |
|---|
| 54 | statements can look like this: </p> |
|---|
| [62] | 55 | <ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">PLOT3D_DATA out:loc:tr avs ~/PLOT/$fname _avs<br>PLOT3D_COOR out:loc:tr avs ~/PLOT/$fname _coor .</font></pre></ul> |
|---|
| 56 | <p style="line-height: 100%;">If the respective <b>mrun</b> |
|---|
| 57 | call is |
|---|
| [5] | 58 | like</p> |
|---|
| [62] | 59 | <ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">mrun -d test -r “avs”…</font></pre></ul> |
|---|
| 60 | <p style="line-height: 100%;">then the local file <tt><font style="font-size: 10pt;" size="2">PLOT3D_DATA</font></tt> |
|---|
| 61 | is copied to the permanent file <tt><font style="font-size: 10pt;" size="2">~/PLOT/test/test_avs</font></tt> |
|---|
| 62 | . |
|---|
| 63 | However, the character string “<tt><font style="font-size: 10pt;" size="2">avs</font></tt>” |
|---|
| [5] | 64 | activating the file connection staement (see third column of the |
|---|
| [62] | 65 | statement) must be given in the <b>mrun</b> call as |
|---|
| 66 | argument of the |
|---|
| 67 | option -r (and/or -o). <span style="text-decoration: none;">If |
|---|
| 68 | t</span>his |
|---|
| [5] | 69 | is forgotten by mistake, the model outputs the data to the local |
|---|
| 70 | file, but this is not copied to the permanent file and thus the data |
|---|
| 71 | are not available for the user after the run has finished.<br> |
|---|
| [62] | 72 | </p><p style="line-height: 100%;">The created data |
|---|
| 73 | file can be used as |
|---|
| [5] | 74 | input file for the plot software <span style="font-weight: bold;">AVS</span> |
|---|
| 75 | although for parallel runs another step is necessary which is |
|---|
| 76 | described at the end of this chapter. However, after starting <b>AVS</b> |
|---|
| [62] | 77 | (by executing the command “avs”), these data file |
|---|
| 78 | is not read |
|---|
| 79 | immediately<font color="#000000">. First, the user has to |
|---|
| 80 | load a |
|---|
| [5] | 81 | suitable network (created by the |
|---|
| [62] | 82 | network editor). This module usually contains the module</font> |
|---|
| 83 | “read |
|---|
| 84 | field”, which requires an input |
|---|
| [5] | 85 | file in the so-called "fld-format", which in turn refers to the two |
|---|
| 86 | files |
|---|
| 87 | specified above (containing the volume data and coordinate |
|---|
| 88 | informations) and describes their exact structure. This fld file is |
|---|
| 89 | also generated by PALM by creating two different |
|---|
| 90 | local files with the names <a href="chapter_3.4.html#PLOT3D_FLD">PLOT3D_FLD</a> |
|---|
| 91 | and <a href="chapter_3.4.html#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>, |
|---|
| [62] | 92 | which must be combined into one file by a so-called <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#chapter6.2">output |
|---|
| [5] | 93 | command</a>: </p> |
|---|
| [62] | 94 | <ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">OC:[[ -f PLOT3D_FLD ]] && cat PLOT3D_FLD_COOR >> PLOT3D_FLD</font></pre></ul> |
|---|
| 95 | <p style="line-height: 100%;">The new file PLOT3D_FLD also |
|---|
| 96 | needs a file |
|---|
| [5] | 97 | connection statement: </p> |
|---|
| [62] | 98 | <ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">PLOT3D_FLD out:loc:tr avs ~/PLOT/$fname _fld fld</font></pre></ul> |
|---|
| [5] | 99 | <p style="line-height: 100%;">The above <b>mrun </b>call |
|---|
| 100 | then copies the local file <tt><font style="font-size: 10pt;" size="2">PLOT3D_FLD</font></tt> |
|---|
| 101 | to the permanent file <tt><font style="font-size: 10pt;" size="2">~/PLOT/test/test_fld.fld</font> |
|---|
| [62] | 102 | </tt><font face="Thorndale, serif">.</font> In |
|---|
| 103 | this case the entry |
|---|
| 104 | “<tt><font style="font-size: 10pt;" size="2">fld</font></tt>” |
|---|
| [5] | 105 | in the sixth column of the file connection statement is |
|---|
| 106 | very important because this ensures that the permanent file name gets |
|---|
| [62] | 107 | the suffix ” <tt><font style="font-size: 10pt;" size="2">.fld</font></tt> |
|---|
| [5] | 108 | ". The <span style="font-weight: bold;">AVS</span> |
|---|
| [62] | 109 | module “read field” expects all files to have this |
|---|
| 110 | suffix. (Note: With |
|---|
| [5] | 111 | this file |
|---|
| [62] | 112 | connection statements files with cycle numbers receive the names |
|---|
| 113 | ”<tt><font style="font-size: 10pt;" size="2">… |
|---|
| 114 | _fld.<number of cycle>.fld</font></tt><font style="font-size: 10pt;" size="2"> |
|---|
| [5] | 115 | </font>".) </p> |
|---|
| [62] | 116 | <p style="line-height: 100%;"><font color="#000000">The |
|---|
| 117 | file |
|---|
| [5] | 118 | connection statements must guarantee that all three permanent files |
|---|
| 119 | (volume |
|---|
| 120 | data, coordinates, fld file) lie in the same directory. The names of |
|---|
| 121 | the volume data file and coordinate file may not be changed after |
|---|
| 122 | creation of the files, since they are registered in the fld file and |
|---|
| [62] | 123 | otherwise cannot be found </font>by the "read field" module. |
|---|
| 124 | Sometimes |
|---|
| [5] | 125 | it may happen<font color="#000000"> |
|---|
| 126 | that incorrect file names are registered into the fld file. In such |
|---|
| 127 | cases the user must edit and correct the fld file accordingly. </font> |
|---|
| [62] | 128 | </p><p style="line-height: 100%;"><font color="#800000"><font color="#000000">After |
|---|
| [5] | 129 | <font color="#000000">the <span style="font-weight: bold;">AVS</span> |
|---|
| [62] | 130 | module <font color="#000000">“read |
|---|
| 131 | fields” </font>has </font>read in the data, the |
|---|
| 132 | content of this |
|---|
| [5] | 133 | file is listed in a separate <span style="font-weight: bold;">AVS</span> |
|---|
| 134 | window where each quantity is represented by its name and output time.</font> |
|---|
| [62] | 135 | </font></p><p style="line-height: 100%;">With |
|---|
| 136 | parallel runs each PE outputs the |
|---|
| [5] | 137 | volume data of its subdomain to a separate file with the name |
|---|
| 138 | PLOT3D_DATA_<processor-Id>, |
|---|
| 139 | whereby <processor-Id> is a four digit number (e.g. |
|---|
| 140 | PLOT3D_DATA_0000). These files are not suitable for <b>AVS</b>, |
|---|
| 141 | but after the end of a run they can be combined to one file readable by |
|---|
| [62] | 142 | <span style="font-weight: bold;">AVS</span>. This is |
|---|
| 143 | done via a |
|---|
| [5] | 144 | further output command in the configuration file: </p> |
|---|
| [62] | 145 | <ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">OC:[[$ ( echo $localhost | cut -c1-3 ) = ibmh ]] && combine_plot_fields.x</font></pre></ul> |
|---|
| 146 | <p style="line-height: 100%;">The program <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt> |
|---|
| [5] | 147 | collects the data from the individual processor files and outputs it |
|---|
| 148 | into the local file <tt><font style="font-size: 10pt;" size="2">PLOT2D_DATA</font></tt> |
|---|
| 149 | which can be processed by <span style="font-weight: bold;">AVS</span>. |
|---|
| 150 | Using this call, possibly existing |
|---|
| 151 | files of 2d cross sections (xy, xz, yz) are |
|---|
| 152 | also combined. The tool writes |
|---|
| 153 | informative messages about the actions accomplished into the job |
|---|
| 154 | protocol, even if no files were found (i.e. the output command |
|---|
| 155 | may remain in the configuration file, even if no appropriate files |
|---|
| [62] | 156 | are created during the simulation). <span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span><tt><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span></tt><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span><tt><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span></tt><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span><tt><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span></tt><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span><br> |
|---|
| 157 | </p><p style="line-height: 100%;"> <b>Note:</b> |
|---|
| 158 | <span style="font-weight: bold;">AVS</span> can |
|---|
| 159 | process 64 arrays at maximum |
|---|
| [5] | 160 | in one file (with vector representations even |
|---|
| 161 | only 25). If more arrays should be output, surplus arrays must be |
|---|
| 162 | removed from the fld file (see <a href="chapter_3.4.html#PLOT3D_FLD">PLOT3D_FLD</a>) |
|---|
| 163 | manually. </p> |
|---|
| [62] | 164 | <hr><p style="line-height: 100%;"><br> |
|---|
| 165 | <font color="#000080"><font color="#000080"><a href="chapter_4.5.4.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.5.6.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font></p><p style="line-height: 100%;"> <i>Last |
|---|
| 166 | change: </i> $Id: chapter_4.5.5.html 62 2007-03-13 02:52:40Z fricke $</p> |
|---|
| 167 | </body></html> |
|---|
