source: palm/tags/release-3.2a/DOC/app/chapter_4.5.5.html

Last change on this file was 62, checked in by raasch, 15 years ago

Id string added to all html files

  • Property svn:keywords set to Id
File size: 11.2 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
4chapter 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
11Plots of 3d volume
12data with AVS</font></h4>
13<p style="line-height: 100%;">In contrast to the plot
14output described
15so far, which can be handled more or less automatically, the creation
16of
17plots with <b>AVS</b> requires programming a so-called
18network by
19using the <span style="font-weight: bold;">AVS</span>
20network editor
21to design the plot
22layout. Details are not given here because it is assumed that the user
23is familiar with <b>AVS</b>. </p>
24<p style="line-height: 100%;"><font color="#000000">Output
25of 3d volume
26data requires to set at least two parameters: </font>first, the
27temporal
28interval of the output time (run parameter <a href="chapter_4.2.html#dt_do3d"><u>dt_do3d)</u></a><span style="text-decoration: none;">
29and second<span style="text-decoration: none;"></span>
30the 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
31parameter <a href="chapter_4.2.html#nz_do3d">nz_do3d</a>
32can be used to limit data output in vertical direction up to a certain
33grid
34point. If no value has been assigned to <b>data_output</b>
35or
36if the value given for <b>dt_do3d </b>is
37larger than the simulated time (see <a href="chapter_4.1.html#end_time">end_time</a>),
38<b>then there will be no output!</b> By default, data is
39output in
4032-bit real format. Alternatively, for parallel runs, data can also be
41output in compressed format using 32-bit integers. This yields
42a loss of accuracy, but the file size is clearly reduced. The output of
43compressed data is described in more detail in <a href="chapter_4.5.6.html">chapter
444.5.6</a>. </p>
45<p style="line-height: 100%;">Data, whether compressed or
46uncompressed, is output into the local file <a href="chapter_3.4.html#PLOT3D_DATA">PLOT3D_DATA</a>.
47This file must be linked with a permanent file by
48using a file connection statement in the <b>mrun</b>
49configuration
50file (see e.g. <a href="chapter_3.2.html">chapter
513.2</a>). At the end of the run the local file is copied to this
52file. Additionally, mrun creates a file containing some coordinate
53informations about the 3d data, which also has to be copied. The
54statements can look like this: </p>
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>
57call is
58like</p>
59<ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">mrun -d test -r &ldquo;avs&rdquo;&hellip;</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>
61is copied to the permanent file <tt><font style="font-size: 10pt;" size="2">~/PLOT/test/test_avs</font></tt>
62.
63However, the character string &ldquo;<tt><font style="font-size: 10pt;" size="2">avs</font></tt>&rdquo;
64activating the file connection staement (see third column of the
65statement) must be given in the <b>mrun</b> call as
66argument of the
67option -r (and/or -o). <span style="text-decoration: none;">If
68t</span>his
69is forgotten by mistake, the model outputs the data to the local
70file, but this is not copied to the permanent file and thus the data
71are not available for the user after the run has finished.<br>
72</p><p style="line-height: 100%;">The created data
73file can be used as
74input file for the plot software <span style="font-weight: bold;">AVS</span>
75although for parallel runs another step is necessary which is
76described at the end of this chapter. However, after starting <b>AVS</b>
77(by executing the command &ldquo;avs&rdquo;), these data file
78is not read
79immediately<font color="#000000">. First, the user has to
80load a
81suitable network (created by the
82network editor). This module usually contains the module</font>
83&ldquo;read
84field&rdquo;, which requires an input
85file in the so-called "fld-format", which in turn refers to the two
86files
87specified above (containing the volume data and coordinate
88informations) and describes their exact structure. This fld file is
89also generated by PALM by creating two different
90local files with the names <a href="chapter_3.4.html#PLOT3D_FLD">PLOT3D_FLD</a>
91and <a href="chapter_3.4.html#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>,
92which 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
93command</a>: </p>
94<ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">OC:[[ -f PLOT3D_FLD ]] &amp;&amp; cat PLOT3D_FLD_COOR &gt;&gt; PLOT3D_FLD</font></pre></ul>
95<p style="line-height: 100%;">The new file PLOT3D_FLD also
96needs a file
97connection statement: </p>
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>
99<p style="line-height: 100%;">The above <b>mrun </b>call
100then copies the local file <tt><font style="font-size: 10pt;" size="2">PLOT3D_FLD</font></tt>
101to the permanent file <tt><font style="font-size: 10pt;" size="2">~/PLOT/test/test_fld.fld</font>
102</tt><font face="Thorndale, serif">.</font> In
103this case the entry
104&ldquo;<tt><font style="font-size: 10pt;" size="2">fld</font></tt>&rdquo;
105in the sixth column of the file connection statement is
106very important because this ensures that the permanent file name gets
107the suffix &rdquo; <tt><font style="font-size: 10pt;" size="2">.fld</font></tt>
108".&nbsp; The <span style="font-weight: bold;">AVS</span>
109module &ldquo;read field&rdquo; expects all files to have this
110suffix. (Note: With
111this file
112connection statements files with cycle numbers receive the names
113&rdquo;<tt><font style="font-size: 10pt;" size="2">&hellip;
114_fld.&lt;number of cycle&gt;.fld</font></tt><font style="font-size: 10pt;" size="2">
115</font>".) </p>
116<p style="line-height: 100%;"><font color="#000000">The
117file
118connection statements must guarantee that all three permanent files
119(volume
120data, coordinates, fld file) lie in the same directory. The names of
121the volume data file and coordinate file may not be changed after
122creation of the files, since they are registered in the fld file and
123otherwise cannot be found </font>by the "read field" module.
124Sometimes
125it may happen<font color="#000000">
126that incorrect file names are registered into the fld file. In such
127cases the user must edit and correct the fld file accordingly. </font>
128</p><p style="line-height: 100%;"><font color="#800000"><font color="#000000">After
129<font color="#000000">the <span style="font-weight: bold;">AVS</span>
130module <font color="#000000">&ldquo;read
131fields&rdquo; </font>has </font>read in the data, the
132content of this
133file is listed in a separate <span style="font-weight: bold;">AVS</span>
134window where each quantity is represented by its name and output time.</font>
135</font></p><p style="line-height: 100%;">With
136parallel runs each PE outputs the
137volume data of its subdomain to a separate file with the name
138PLOT3D_DATA_&lt;processor-Id&gt;,
139whereby &lt;processor-Id&gt; is a four digit number (e.g.
140PLOT3D_DATA_0000). These files are not suitable for&nbsp; <b>AVS</b>,
141but after the end of a run they can be combined to one file readable by
142<span style="font-weight: bold;">AVS</span>. This is
143done via a
144further output command in the configuration file: </p>
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 ]] &amp;&amp; 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>
147collects the data from the individual processor files and outputs it
148into the local file <tt><font style="font-size: 10pt;" size="2">PLOT2D_DATA</font></tt>
149which can be processed by <span style="font-weight: bold;">AVS</span>.
150Using this call, possibly existing
151files of 2d cross sections (xy, xz, yz) are
152also combined.&nbsp;The tool writes
153informative messages about the actions accomplished into the job
154protocol, even if no files were found (i.e. the output command
155may remain in the configuration file, even if no appropriate files
156are 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%;">&nbsp;<b>Note:</b>
158<span style="font-weight: bold;">AVS</span> can
159process 64 arrays at maximum
160in one file (with vector representations even
161only 25). If more arrays should be output, surplus arrays must be
162removed from the fld file (see <a href="chapter_3.4.html#PLOT3D_FLD">PLOT3D_FLD</a>)
163manually. &nbsp; </p>
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%;">&nbsp;<i>Last
166change:&nbsp;</i> $Id: chapter_4.5.5.html 62 2007-03-13 02:52:40Z banzhafs $</p>
167</body></html>
Note: See TracBrowser for help on using the repository browser.