source: palm/trunk/DOC/app/chapter_3.1.html @ 247

Last change on this file since 247 was 62, checked in by raasch, 18 years ago

Id string added to all html files

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