source: palm/tags/release-3.1c/DOC/app/chapter_3.1.html @ 710

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

html-documentation added

File size: 6.4 KB
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
4  <meta http-equiv="CONTENT-TYPE"
5 content="text/html; charset=windows-1252">
6  <title>PALM chapter 3.1</title>
7  <meta name="GENERATOR" content="StarOffice 7  (Win32)">
8  <meta name="AUTHOR" content="Marcus Oliver Letzel">
9  <meta name="CREATED" content="20040806;13565279">
10  <meta name="CHANGED" content="20040806;13575492">
11  <meta name="KEYWORDS" content="parallel LES model">
13<body dir="ltr" lang="de-DE">
14<h3 style="line-height: 100%;">3.1 Job control with mrun</h3>
15<p style="line-height: 100%;">The start of model runs in principle
16takes place via executing the shell script <a
17 href="">mrun.</a>
18With this script it is possible to operate the model both
19interactively and in batch mode. Batch operation is possible on the
20local computer as well as on a remote computer (supposed that a batch
21queuing system is available). Here only the batch operation on a remote
22computer is
23described, because this represents the usual mode of operation due to
24the large computing time requirements of the model. The interactive
25execution differs only in some points and is described in <a
26 href="chapter_3.6.html">chapter
273.6</a>. </p>
28<p style="line-height: 100%;">By the call of <b>mrun </b>a complete
29batch job is produced, transferred to the user determined remote
31and submitted to its queuing system (LoadLeveler, PBS, etc.).
32After processing of the job, the so-called job protocol is sent back
33to the local computer of the user (the local computer is the
34computer, on which the user calls <b>mrun</b>). The following actions
35are implemented by the job, amongst other: </p>
37  <li>
38    <p style="margin-bottom: 0cm; line-height: 100%;">Change to a
39temporary working directory. </p>
40  </li>
41  <li>
42    <p style="margin-bottom: 0cm; line-height: 100%;">The input files
43needed by the model are copied into this directory. These files are
44transferred from the local computer. </p>
45  </li>
46  <li>
47    <p style="margin-bottom: 0cm; line-height: 100%;">Execute the
48model. </p>
49  </li>
50  <li>
51    <p style="margin-bottom: 0cm; line-height: 100%;">Copy the output
52files produced by the model into the directories determined by the user
53(these are also allowed to lie on the local computer). Depending on the
54choice of the user, the files may also be saved on an archiving system
55(if existing). </p>
56  </li>
57  <li>
58    <p style="margin-bottom: 0cm; line-height: 100%;">Delete the
59temporary working direction. </p>
60  </li>
61  <li>
62    <p style="line-height: 100%;">Transfer the job protocol to the
63local computer. </p>
64  </li>
66<p style="line-height: 100%;">From this list it becomes clear that two
67of the substantial functions of <b>mrun</b> are the supply of input
68files for the model and the storage of output files produced by the
69model. The model exclusively works with so-called local files, which
70lie in the temporary working directory created by <b>mrun.</b> The
71“local” names of these files are determined by the model
72(in the appropriate OPEN instructions). In <a href="chapter_3.4.html">chapter
733.4</a> all possible input and output filenames are specified. In
74contrast to this, the input files, made available by the user,
75usually lie in permanent directories (e.g. in the /home directory) and
76the output data, produced by the model, may also be
77stored there. The directory names are arbitrary. The actual file name
78(without path) of these input and output files is specified by an
79option of <b>mrun</b>. All input and output files of the model
80receive this file name (e.g. <i>abcde</i>), but each individual file
81is still provided with an extension (e.g. <i>abcde_par</i>, etc.
82<i>abcde_dat</i>) - otherwise the files would not be distinguishable.
83The linkage of local file names with the names of the permanent
84directories and the file name extensions takes place in a
85configuration file, which <b>mrun</b> expects to find in the
86respective current working directory of the user. A detailed
87description of this configuration file - which still offers a variety
88of further functions – is found in the
89documentation of the shell script <a
90 href="">mrun</a>
91(sorry: this is only available in German, so far. If you think that you
92would profit from an English version, please give a message to the PALM
94In the next chapter a simple example of a minimum configuration file
95is described. </p>
96<p style="line-height: 100%;">A simple call of <b>mrun</b> could read
97as follows: </p>
99  <p style="line-height: 100%;"><tt>mrun - h <i>ibmh</i> -d <i>abcde</i></tt></p>
101<p style="line-height: 100%;">The model is started by option -<tt>h
102<i>ibmh</i></tt> on the IBM Regatta hanni at the HLRN, i.e. on the
103local computer a batch job is generated, transferred to the remote
104computer (IBM) and submitted to a suitable queue of the queuing system.
105With the
106option <tt>-d</tt> the so-called basis file name (<i>abcde</i>) is
107specified, from which, together with the path names and file name
108extensions, the complete file names (including the path) of the
109permanent input and output files are <font color="#000000">formed.</font><font
110 color="#800000">
111</font>Usually the specification of a set of further options is
112necessary, e.g. the CPU time needed by the model and the memory size
113needed as well as, on parallel computers, the number of processing
114elements which are to be used (options <tt>-t</tt>, <tt>-m</tt> and
115<tt>-X</tt>). A precondition for the call of <b>mrun</b> of course is
116that the installation of the model on the local computer and the
117remote machine is complete (see <a href="chapter_5.0.html">chapter
1185.0</a>). </p>
119<p>Beyond these options a variety of further options for model
120steering can be used in the call of <b>mrun</b>. These are fully
121described in the <a
122 href="">mrun</a>
123documentation (in German). <br>
124&nbsp; </p>
126<p><a href="chapter_3.0.html"><font color="#000080"><img src="left.gif"
127 name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a
128 href="index.html"><font color="#000080"><img src="up.gif"
129 name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a
130 href="chapter_3.2.html"><font color="#000080"><img src="right.gif"
131 name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></p>
132<p><i>Last change:&nbsp;</i> 14/04/05 (SR)</p>
Note: See TracBrowser for help on using the repository browser.