source: palm/tags/release-3.7a/DOC/app/chapter_4.5.2.html @ 4141

Last change on this file since 4141 was 62, checked in by raasch, 17 years ago

Id string added to all html files

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