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

Last change on this file since 1437 was 431, checked in by raasch, 14 years ago

small docu update

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