source: palm/trunk/DOC/app/chapter_4.5.2.html @ 5

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

html-documentation added

File size: 11.4 KB
Line 
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
2<html>
3<head>
4  <meta content="text/html; charset=windows-1252"
5 http-equiv="CONTENT-TYPE">
6  <title>PALM chapter 4.5.2</title>
7  <meta content="StarOffice 7  (Win32)" name="GENERATOR">
8  <meta content="Siegfried Raasch" name="AUTHOR">
9  <meta content="20041022;12155949" name="CREATED">
10  <meta content="20041117;11232134" name="CHANGED">
11  <meta content="parallel LES model" name="KEYWORDS">
12  <style>
13        <!--
14                @page { size: 21cm 29.7cm }
15        -->
16        </style>
17</head>
18<body lang="en-US" dir="ltr">
19<h4 style="line-height: 100%;"><font size="4">4.5.2 Plots of vertical
20profiles with profil</font></h4>
21<p style="line-height: 100%;">Output of vertical
22profile data is enabled by providing values for the run parameters <a
23 href="chapter_4.2.html#dt_dopr"><u>dt_dopr</u></a><span
24 style="text-decoration: none;">
25and </span><a href="chapter_4.2.html#data_output_pr">data_output_pr</a>
26<span style="text-decoration: none;">which specify the temporal
27interval of the output times (in s) and the quantities for which output
28is to be made.</span> Output times cannot be defined
29directly but only via the output time interval, starting from the
30beginning of the initial 3d run (t=0, but no profiles are
31written at the time t=0; exceptions see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>).
32By default, vertical profiles represent an instantaneous horizontal
33average of the
34total model domain at the respective output time. Temporal averaging
35can be initiated with
36the run parameter <a href="chapter_4.2.html#averaging_interval_pr">averaging_interval_pr</a>.
37Beyond that, an output of profiles for user-defined subdomains is
38possible via the
39initialization parameter <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>.</p>
40<p style="line-height: 100%;">Output of desired profiles (temperature,
41velocity, etc.) is steered with the run parameter <a
42 href="chapter_4.2.html#data_output_pr">data_output_pr</a>.
43If this parameter is not set by the user, then, independently of the
44value of <b>dt_dopr</b>, there will be no output! PALM
45creates the local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
46which must be linked with a permanent file (see e.g. <a
47 href="chapter_3.2.html">chapter
483.2</a>) via a file connection statement in the <b>mrun</b>
49configuration file. At the end of the run the local file is copied
50to this file. Such a statement can look like this: </p>
51<ul>
52  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font size="2"
53 style="font-size: 10pt;">PLOT1D_DATA   out:loc:tr   pr   ~/PLOT/$fname   _pr_in.</font></pre>
54</ul>
55<p style="line-height: 100%;">If the respective <b>mrun</b> call is
56like<br>
57</p>
58<ul>
59  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font size="2"
60 style="font-size: 10pt;">mrun -d test -r “pr” …</font></pre>
61</ul>
62<p style="line-height: 100%;">then the local f<span
63 style="text-decoration: none;">ile
64</span><tt><span style="text-decoration: none;"><font size="2"
65 style="font-size: 10pt;">PLOT1D_DATA</font></span></tt><span
66 style="text-decoration: none;"><font size="2" style="font-size: 10pt;">
67</font>is copied to the permanent file </span><tt><span
68 style="text-decoration: none;"><font size="2" style="font-size: 10pt;">~/PLOT/test/test_pr_in</font></span></tt><span
69 style="text-decoration: none;">.
70However, the character string <font size="2" style="font-size: 10pt;">“</font></span><tt><span
71 style="text-decoration: none;"><font size="2" style="font-size: 10pt;">pr</font></span></tt><span
72 style="text-decoration: none;"><font size="2" style="font-size: 10pt;">”</font>
73activating the file connection statement </span><span
74 style="text-decoration: none;">(see third column of the statement) </span><span
75 style="text-decoration: none;">must be given in the <b>mrun</b>
76call as argument of the
77option -r (and/or -o)<b>.</b> If t</span>his is
78forgotten by mistake, the model outputs the data to the local file, but
79this is
80not copied to the permanent file and thus the data are not available
81for the user after the run has finished. </p>
82<p style="line-height: 100%;">The created data file can be
83directly used as input file for the plot software <b>profil</b>.
84<b>profil</b> needs another file, the so-called parameter file, which
85specifies the plot layout. This file is created by PALM under the local
86name <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>
87and also needs a file connection statement, e.g.: </p>
88<ul>
89  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font size="2"
90 style="font-size: 10pt;">PLOT1D_PAR out:loc:tr    pr ~/PLOT/$fname   _pr_par.</font></pre>
91</ul>
92<p style="line-height: 100%;">If you are in the directory
93<tt><font size="2" style="font-size: 10pt;">~/PLOT/test</font>,</tt>the
94data can be plotted by entering </p>
95<ul>
96  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font size="2"
97 style="font-size: 10pt;">profil -d test_pr_in -p test_pr_par</font></pre>
98</ul>
99<p style="line-height: 100%;">The default plot layout as
100specified in the parameter file is as follows: the profiles of the
101different quantities are plottet into
102one or more coordinate systems (panels). Every profile is plotted only
103once,
104however several profiles of different quantities can be plottet into
105the same panel. If case of this, the different quantities are
106marked by different styles of lines. Which variables
107are drawn into which coordinate system is specified by the user via
108the run parameter <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>.
109It is very important to note that only profiles are plottet, which are
110assigned to
111a coordinate system via <b>cross_profiles</b>. If a certain
112variable is selected by <b>data_output_pr</b> but not assigned to a coordinate
113system via <b>cross_profiles</b>, then the appropriate profile data
114are written to the file PLOT1D_DATA but they are not plotted! All
115panels for which data
116exist are plotted. For example, if only the profiles of the potential
117temperature are
118to be plottet in a panel but output of potential temperature is not set
119via
120<b>data_output_pr</b>, then the respective panel is not drawn
121(thus no 'empty' panels appear in the plot). The
122parameters <a href="chapter_4.2.html#profile_columns">profile_columns</a>
123and <a href="chapter_4.2.html#profile_rows">profile_rows</a>
124determine how the panels are arranged in columns and rows. The panels
125are plotted in the order given by <span style="font-weight: bold;">data_output_pr</span>
126starting in the top row from left to right.
127If the number of panels to be plotted is larger than the
128product <b>profile_columns</b> * <b>profile_rows</b>, then the plot
129is continued on a second page. </p>
130<p style="line-height: 100%;">During a model run output of profiles to
131file PLOT1D_DATA is usually carried out for several times (as
132determined by <span style="font-weight: bold;">dt_dopr</span>)<font
133 size="2" style="font-size: 10pt;">.</font>
134All of these profiles belonging to the same quantity are plotted in the
135same panel. The different output times are marked by different line
136colors. All profiles of a certain output time have the
137same color, even if they are plotted into different panels. Beyond
138that, a legend entry is made for each, containing the name of the
139respective quantity and the output time.
140This legend string is taken from file PLOT1D_DATA
141in which a comment line is placed ahead of each profile data. </p>
142<p style="line-height: 100%;">For identification, each plot is
143provided with a title, which contains the model version number, the
144run identifier (base file name + number of the restart run), the name
145of the host where the run was executed, the date and time of the
146beginning
147of the run as well as the averaging domain (by default: <span
148 style="font-style: italic;">'total
149domain'</span>). If the profiles are additionally temporally averaged,
150each panel gets an appropriate sub-label (<span
151 style="font-style: italic;">'time
152averaged over… s'</span>). The axes labels of the x axes of the
153individual panels are specified with the run parameter
154<a href="chapter_4.2.html#cross_xtext">cross_xtext</a>,
155the y axes always have the label <span style="font-style: italic;">'height
156in m'</span>. For better
157comparison, the profiles can be normalized with respect to different
158quantities
159(see <a href="chapter_4.2.html#cross_normalized_x">cross_normalized_x</a>
160and <a href="chapter_4.2.html#cross_normalized_y">cross_normalized_y</a>).
161The respective normalization is noted in the axes label. </p>
162<p style="line-height: 100%;"><font color="#000000">As already
163mentioned, the profiles of a quantity
164for all output times are plotted into the same panel. This is not
165possible if a simulation needs restart runs, since the restart runs
166write the
167profile data to separate files (with appropriate cycle numbers) and
168create own parameter files. Thus by default profiles can only be drawn
169separately for each respective run. However there is a possibility to
170plot
171all profiles of a quantity in one plot, regardless of the number of
172restart runs. For this
173purpose the configuration file must be changed such that for restart
174runs the profile data are appended to already existing<font
175 color="#000000">
176data</font> (thus all data are output into one file). Then the
177configuration file has two entries for </font><tt><font color="#000000">PLOT1D_DATA</font></tt><font
178 color="#000000">:
179</font></p>
180<ul>
181  <pre style="line-height: 100%;"><font size="2"
182 style="font-size: 10pt;">PLOT1D_DATA out:loc:tr  pr# ~/PLOT/$fname _pr_in</font><br><font
183 size="2" style="font-size: 10pt;">PLOT1D_DATA out:loc:tra prf ~/PLOT/$fname _pr_in.</font></pre>
184</ul>
185<p style="line-height: 100%;">The first run of the job chain is now </p>
186<ul>
187  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font size="2"
188 style="font-size: 10pt;">mrun - D test - r “pr#…</font></pre>
189</ul>
190<p style="line-height: 100%;">For the restart runs, the "#" in the <span
191 style="font-weight: bold;">mrun</span>
192call is automatically replaced by an "f". At the end of the job chain
193there will only be one data file containing the complete profile data.
194The file connection statement for the parameter file
195<font size="3">PLOT1D_PAR</font> has not changed, thus a new cycle of
196the respective permanent file is created for each run. To plot
197the combined data with the parameter file created by the last run of
198the job chain, the run parameter
199<a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a>
200= <i>.TRUE.</i> must be additionally set for the restart runs. If this
201is
202forgotten, the parameter file is useless and the data cannot
203be plotted. </p>
204<p style="line-height: 100%;">The default layout of the plots of
205vertical profiles can be changed by editing the
206parameter file. For a detailed description of the <span
207 style="font-weight: bold;">profil</span> parameters see the
208<a
209 href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>
210manual (only in German). <br>
211</p>
212<hr>
213<p style="line-height: 100%;"><br>
214<font color="#000080"><font color="#000080"><a href="chapter_4.5.html"><font
215 color="#000080"><img width="32" height="32" border="2" align="bottom"
216 name="Grafik1" src="left.gif"></font></a><a href="index.html"><font
217 color="#000080"><img width="32" height="32" border="2" align="bottom"
218 name="Grafik2" src="up.gif"></font></a><a href="chapter_4.5.3.html"><font
219 color="#000080"><img width="32" height="32" border="2" align="bottom"
220 name="Grafik3" src="right.gif"></font></a></font></font></p>
221<p style="line-height: 100%;"><span style="font-style: italic;">Last
222change:</span> 19/04/05 (SR)&nbsp;</p>
223</body>
224</html>
Note: See TracBrowser for help on using the repository browser.