Changeset 62 for palm/trunk/DOC/app/chapter_3.2.html
- Timestamp:
- Mar 13, 2007 2:52:40 AM (18 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
palm/trunk/DOC/app/chapter_3.2.html
r54 r62 1 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> 2 <html> 3 <head> 4 <meta http-equiv="CONTENT-TYPE" 5 content="text/html; charset=windows-1252"> 6 <title>PALM chapter 3.2</title> 7 <meta name="GENERATOR" content="StarOffice 7 (Win32)"> 8 <meta name="AUTHOR" content="Marcus Oliver Letzel"> 9 <meta name="CREATED" content="20040726;13164873"> 10 <meta name="CHANGED" content="20050119;9245042"> 11 <meta name="KEYWORDS" content="parallel LES model"> 12 <style> 13 <!-- 14 @page { size: 21cm 29.7cm } 15 --> 16 </style> 17 </head> 18 <body dir="ltr" lang="en-US"> 19 <h3 style="line-height: 100%;">3.2 Example of a minimum configuration 2 <html><head> 3 <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM 4 chapter 3.2</title> <meta name="GENERATOR" content="StarOffice 7 (Win32)"> <meta name="AUTHOR" content="Marcus Oliver Letzel"> <meta name="CREATED" content="20040726;13164873"> <meta name="CHANGED" content="20050119;9245042"> <meta name="KEYWORDS" content="parallel LES model"> <style> 5 <!-- 6 @page { size: 21cm 29.7cm } 7 --> 8 </style></head> 9 10 <body style="direction: ltr;" lang="en-US"><h3 style="line-height: 100%;">3.2 Example of a minimum 11 configuration 20 12 file</h3> 21 <p style="line-height: 100%;">In this chapter a sample configuration 13 <p style="line-height: 100%;">In this chapter a sample 14 configuration 22 15 file is described. It contains only instructions which are really 23 16 necessary for the execution of a simple model run (configuration 24 17 files can be much more complex). The example presented here is stored 25 in an appropriate <a 26 href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/.mrun.config">example 27 file</a> (containing more than the configuration data presented here) 28 and can be used, together with the <a 29 href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/example_p3d">parameter 18 in an appropriate <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/.mrun.config">example 19 file</a> (containing more than the configuration data presented 20 here) 21 and can be used, together with the <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/example_p3d">parameter 30 22 file</a> presented in <a href="chapter_4.4.html">chapter 31 4.4</a>, for the execution of a simple model run. In chapter 4.4 the 32 complete <b>mrun</b> options which are necessary for the appropriate 23 4.4</a>, for the execution of a simple model run. In chapter 4.4 24 the 25 complete <b>mrun</b> options which are necessary for the 26 appropriate 33 27 parameter file are described. Furthermore not all details of the 34 28 configuration file are described here. Therefore you should take a 35 look at the <a 36 href="http://www.muk.uni-hannover.de/%7Eraasch/Software/mrun_beschreibung.html">mrun</a> 29 look at the <a href="http://www.muk.uni-hannover.de/%7Eraasch/Software/mrun_beschreibung.html">mrun</a> 37 30 documentation (sorry: this is only available in German, so far. If you 38 31 think that you 39 32 would profit from an English version, please give a message to the PALM 40 33 group). </p> 41 <p style="line-height: 100%;">The following configuration data 34 <p style="line-height: 100%;">The following configuration 35 data 42 36 exclusively applies to model runs on the IBM Regatta hanni of the 43 37 HLRN when using several processing elements (i.e. for the parallel 44 38 version of the model). The proper installation of the model is 45 39 presumed (see <a href="chapter_5.0.html">chapter 46 5.0</a>). Furthermore it is supposed that the user is located in the 40 5.0</a>). Furthermore it is supposed that the user is located in 41 the 47 42 directory <tt><font style="font-size: 10pt;" size="2">$HOME/palm/current_version/SOURCE</font></tt> 48 43 on its local computer. There are the FORTRAN source codes of the 49 44 model (<tt><font style="font-size: 10pt;" size="2">*.f90</font></tt>) 50 45 as 51 well as the configuration file (name: <tt><font 52 style="font-size: 10pt;" size="2">.mrun.config</font></tt>) 46 well as the configuration file (name: <tt><font style="font-size: 10pt;" size="2">.mrun.config</font></tt>) 53 47 and the make file (name: <tt><font style="font-size: 10pt;" size="2">Makefile</font></tt>). 54 48 The configuration file has the following contents (among other things): 55 <br> 56 57 </p> 58 <pre style="line-height: 100%;"><font style="font-size: 10pt;" size="2">% source_path <i>$HOME/palm/current_version/SOURCE</i></font><br><font 59 style="font-size: 10pt;" size="2">% mainprog <i>palm.f90</i></font><br><font 60 style="font-size: 10pt;" size="2">% use_makefile <i>true</i></font><br><font 61 style="font-size: 10pt;" size="2">% fopts <i>-O3:-g:-qrealsize=8:-Q:-q64:-qmaxmem=-1:-qtune=pwr4:-qarch=pwr4:-qnosave:-qnoescape ibmh parallel<span 62 style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span></i></font><br><font 63 style="font-size: 10pt;" size="2">% lopts <span 64 style="font-style: italic;">-O3:-g:-qrealsize=8:-Q:-q64:-qmaxmem=-1:-qtune=pwr4:-qarch=pwr4:-qnosave:-qnoescape:-lesslsmp ibmh parallel</span></font><br><font 65 style="font-size: 10pt;" size="2">#</font><br><font 66 style="font-size: 10pt;" size="2">EC:[[ \$locat = execution]] & & <i>cat </i>RUN_CONTROL </font><br><font 67 style="font-size: 10pt;" size="2">#</font><br><a 68 href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN</font></a><font 69 style="font-size: 10pt;" size="2"> in:job:npe d3# ~/palm/current_version/JOBS/$fname/INPUT _p3d</font><br><font 70 style="font-size: 10pt;" size="2">#</font><br><a 71 href="chapter_3.4.html#RUN_CONTROL"><font style="font-size: 10pt;" 72 size="2">RUN_CONTROL</font></a><font style="font-size: 10pt;" size="2"> out:loc:tr d3# ~/palm/current_version/JOBS/$fname/MONITORING _rc</font><br><a 73 href="chapter_3.4.html#HEADER"><font style="font-size: 10pt;" size="2">HEADER</font></a><font 74 style="font-size: 10pt;" size="2"> out:loc:tr d3# ~/palm/current_version/JOBS/$fname/MONITORING _header</font><br><a 75 href="chapter_3.4.html#PLOT1D_PAR"><font style="font-size: 10pt;" 76 size="2">PLOT1D_PAR</font></a><font style="font-size: 10pt;" size="2"> out:loc:tr pr# ~/palm/current_version/JOBS/$fname/OUTPUT _pr_par</font><br><a 77 href="chapter_3.4.html#PLOT1D_DATA"><font style="font-size: 10pt;" 78 size="2">PLOT1D_DATA</font></a><font style="font-size: 10pt;" size="2"> out:loc:tr pr# ~/palm/current_version/JOBS/$fname/OUTPUT _pr_in</font></pre> 49 <br> 50 </p><pre style="line-height: 100%;"><font style="font-size: 10pt;" size="2">% source_path <i>$HOME/palm/current_version/SOURCE</i></font><br><font style="font-size: 10pt;" size="2">% mainprog <i>palm.f90</i></font><br><font style="font-size: 10pt;" size="2">% use_makefile <i>true</i></font><br><font style="font-size: 10pt;" size="2">% fopts <i>-O3:-g:-qrealsize=8:-Q:-q64:-qmaxmem=-1:-qtune=pwr4:-qarch=pwr4:-qnosave:-qnoescape ibmh parallel<span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span></i></font><br><font style="font-size: 10pt;" size="2">% lopts <span style="font-style: italic;">-O3:-g:-qrealsize=8:-Q:-q64:-qmaxmem=-1:-qtune=pwr4:-qarch=pwr4:-qnosave:-qnoescape:-lesslsmp ibmh parallel</span></font><br><font style="font-size: 10pt;" size="2">#</font><br><font style="font-size: 10pt;" size="2">EC:[[ \$locat = execution]] & & <i>cat </i>RUN_CONTROL </font><br><font style="font-size: 10pt;" size="2">#</font><br><a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN</font></a><font style="font-size: 10pt;" size="2"> in:job:npe d3# ~/palm/current_version/JOBS/$fname/INPUT _p3d</font><br><font style="font-size: 10pt;" size="2">#</font><br><a href="chapter_3.4.html#RUN_CONTROL"><font style="font-size: 10pt;" size="2">RUN_CONTROL</font></a><font style="font-size: 10pt;" size="2"> out:loc:tr d3# ~/palm/current_version/JOBS/$fname/MONITORING _rc</font><br><a href="chapter_3.4.html#HEADER"><font style="font-size: 10pt;" size="2">HEADER</font></a><font style="font-size: 10pt;" size="2"> out:loc:tr d3# ~/palm/current_version/JOBS/$fname/MONITORING _header</font><br><a href="chapter_3.4.html#PLOT1D_PAR"><font style="font-size: 10pt;" size="2">PLOT1D_PAR</font></a><font style="font-size: 10pt;" size="2"> out:loc:tr pr# ~/palm/current_version/JOBS/$fname/OUTPUT _pr_par</font><br><a href="chapter_3.4.html#PLOT1D_DATA"><font style="font-size: 10pt;" size="2">PLOT1D_DATA</font></a><font style="font-size: 10pt;" size="2"> out:loc:tr pr# ~/palm/current_version/JOBS/$fname/OUTPUT _pr_in</font></pre> 79 51 <p style="line-height: 100%;"><font face="Thorndale, serif">The first 80 52 five lines specify values of 81 so-called environment variables. Such lines begin with a %- 82 sign. After at least one blank the name of the variable</font> <font 83 face="Thorndale, serif">(e.g. 84 </font><tt><i><font face="Thorndale, serif">source_path</font></i></tt><font 85 face="Thorndale, serif">) 53 so-called environment variables. Such lines begin with a 54 “%”- 55 sign. After at least one blank the name of the variable</font> <font face="Thorndale, serif">(e.g. 56 </font><tt><i><font face="Thorndale, serif">source_path</font></i></tt><font face="Thorndale, serif">) 86 57 follows and then seperated by at least one blank the value of the 87 58 variable. Again separated by blank t<font face="Thorndale, serif">he 88 59 so-called validity domain</font> can be indicated (later more). 89 With the first three variables <b>mrun</b> gets to know in which 90 directory the source code lies (</font><tt><i><font 91 face="Thorndale, serif">source_path</font></i></tt><font 92 face="Thorndale, serif">), 93 the file name of the main program (</font><tt><i><font 94 face="Thorndale, serif">mainprog</font></i></tt><font 95 face="Thorndale, serif">) 96 and that the <font face="Thorndale, serif">make mechanism should be 60 With the first three variables <b>mrun</b> gets to know in 61 which 62 directory the source code lies (</font><tt><i><font face="Thorndale, serif">source_path</font></i></tt><font face="Thorndale, serif">), 63 the file name of the main program (</font><tt><i><font face="Thorndale, serif">mainprog</font></i></tt><font face="Thorndale, serif">) 64 and that the <font face="Thorndale, serif">make mechanism 65 should be 97 66 used </font>for compiling (</font><tt><font face="Thorndale, serif"><i>use_makefile 98 67 =</i> <i>true</i></font></tt><font face="Thorndale, serif">). <b>mrun 99 </b>needs these information, <font color="#000000">because for each 68 </b>needs these information, <font color="#000000">because 69 for each 100 70 model run the executable is created by compiling the source files.</font> 101 71 Normally, only the main program (palm.f90) will be compiled while all … … 104 74 model 105 75 (see </font><a href="chapter_5.0.html"><font face="Thorndale, serif">chapter 106 5.0</font></a><font face="Thorndale, serif">). <b>mrun</b> uses 76 5.0</font></a><font face="Thorndale, serif">). 77 <b>mrun</b> uses 107 78 certain standard options for the compilation process. Beyond that you 108 79 can 109 declare additional options with the environment variable </font><tt><i><font 110 face="Thorndale, serif">fopts</font></i></tt><font 111 face="Thorndale, serif">. 80 declare additional options with the environment variable </font><tt><i><font face="Thorndale, serif">fopts</font></i></tt><font face="Thorndale, serif">. 112 81 Within the value assignment of an environment variable in the 113 82 configuration file no blanks must be 114 83 used. If blanks are necessary they must <font face="Thorndale, serif">be 115 replaced </font>by colons (:). <b>mrun</b> will 84 replaced </font>by colons (“:”). <b>mrun</b> 85 will 116 86 interpret these colons as blanks (2 colons written one behind the 117 other will be interpreted as a colon). Thus in the example above </font><tt><font 118 face="Thorndale, serif">fopts 119 has the value </font></tt><font 120 style="font-size: 10pt; font-family: monospace;" size="2"><i>-O3 -g 87 other will be interpreted as a colon). Thus in the example above </font><tt><font face="Thorndale, serif">fopts 88 has the value </font></tt>“<font style="font-size: 10pt; font-family: monospace;" size="2"><i>-O3 89 -g 121 90 -qrealsize=8 -Q -q64 -qmaxmem=-1 -qtune=pwr4 -qarch=pwr4 -qnosave 122 -qnoescape</i></font><tt><i><font face="Thorndale, serif"><font 123 color="#000000"></font></font></i></tt><font face="Thorndale, serif"><font 124 color="#000000">. 125 Thus a PALM executable is generated using high level optimization (</font></font><font 126 color="#000000"><span 127 style="font-style: italic; font-family: monospace;">-O3</span></font><font 128 face="Thorndale, serif"><font color="#000000">).</font></font><font 129 color="#000000"><font face="Thorndale, serif"> For all other options 130 see the compiler manual on the IBM (</font><font size="2"><font 131 face="Cumberland, monospace">man</font></font></font><tt><font 132 color="#000000"> 133 <font size="2"><font face="Cumberland, monospace">f90</font></font></font></tt><font 134 face="Thorndale, serif"><font color="#000000">). Additional libraries 91 -qnoescape</i></font><tt><i><font face="Thorndale, serif"><font color="#000000">”</font></font></i></tt><font face="Thorndale, serif"><font color="#000000">. 92 Thus a PALM executable is generated using high level optimization (</font></font><font color="#000000"><span style="font-style: italic; font-family: monospace;">-O3</span></font><font face="Thorndale, serif"><font color="#000000">).</font></font><font color="#000000"><font face="Thorndale, serif"> 93 For all other options 94 see the compiler manual on the IBM (</font><font size="2"><font face="Cumberland, monospace">man</font></font></font><tt><font color="#000000"> 95 <font size="2"><font face="Cumberland, monospace">f90</font></font></font></tt><font face="Thorndale, serif"><font color="#000000">). 96 Additional libraries 135 97 which the compiler should use are described by 136 the environment variable </font></font><tt><font size="2"><font 137 face="Cumberland, monospace"><font color="#000000">lopts</font></font></font></tt><font 138 color="#000000"> 139 <font face="Thorndale, serif">(loader options).</font></font><font 140 color="#800000"> 98 the environment variable </font></font><tt><font size="2"><font face="Cumberland, monospace"><font color="#000000">lopts</font></font></font></tt><font color="#000000"> 99 <font face="Thorndale, serif">(loader options).</font></font><font color="#800000"> 141 100 </font><font face="Thorndale, serif"><font color="#000000">Here you 142 101 have to indicate a special IBM library (ESSL, </font></font>Engineering 143 and Scientific Subroutine Library)<font face="Thorndale, serif"><font 144 color="#000000">.</font><font color="#800000"> </font>On the 145 IBM-Regatta, all compiler options have also to be given to the linker.</font><font 146 color="#000000"><font face="Thorndale, serif"> </font></font> 147 </p> 148 <p style="line-height: 100%;"><font color="#000000">Compiler and 102 and Scientific Subroutine Library)<font face="Thorndale, serif"><font color="#000000">.</font><font color="#800000"> 103 </font>On the 104 IBM-Regatta, all compiler options have also to be given to the linker.</font><font color="#000000"><font face="Thorndale, serif"> </font></font> 105 </p><p style="line-height: 100%;"><font color="#000000">Compiler and 149 106 loader options usually differ from computer to computer. In the 150 107 configuration file therefore several value assignments for the 151 variables </font><tt><font style="font-size: 10pt;" size="2"><font 152 color="#000000">fopts</font></font></tt><font color="#000000"> 153 and </font><tt><font style="font-size: 10pt;" size="2"><font 154 color="#000000">lopts</font></font></tt><font color="#000000"> 155 exist which become active for different computers.</font><font 156 color="#800000"> 157 <font color="#000000">Which value assignment is used is described by 108 variables </font><tt><font style="font-size: 10pt;" size="2"><font color="#000000">fopts</font></font></tt><font color="#000000"> 109 and </font><tt><font style="font-size: 10pt;" size="2"><font color="#000000">lopts</font></font></tt><font color="#000000"> 110 exist which become active for different computers.</font><font color="#800000"> 111 <font color="#000000">Which value assignment is used is 112 described by 158 113 the so-called validity domain which follows in the appropriate 159 variable lines after the value of variables.</font></font><font 160 color="#000000"> 161 In the example above the entry </font><font color="#000000"><font 162 style="font-size: 11pt; font-style: italic; font-family: monospace;" 163 size="2">ibmh</font></font><tt><font color="#000000"><span 164 style="font-style: italic; font-family: monospace;"> 165 </span></font><font color="#000000"><i><font style="font-size: 11pt;" 166 size="2">parallel</font></i></font></tt><font color="#000000"> 167 stands for </font><tt><font style="font-size: 10pt;" size="2"><font 168 color="#000000">fopts</font></font></tt><font color="#000000"> 169 and </font><tt><font style="font-size: 10pt;" size="2"><font 170 color="#000000">lopts</font></font></tt><font color="#000000">. 114 variable lines after the value of variables.</font></font><font color="#000000"> 115 In the example above the entry “</font><font color="#000000"><font style="font-size: 11pt; font-style: italic; font-family: monospace;" size="2">ibmh</font></font><tt><font color="#000000"><span style="font-style: italic; font-family: monospace;"> 116 </span></font><font color="#000000"><i><font style="font-size: 11pt;" size="2">parallel</font></i></font></tt><font color="#000000">” 117 stands for </font><tt><font style="font-size: 10pt;" size="2"><font color="#000000">fopts</font></font></tt><font color="#000000"> 118 and </font><tt><font style="font-size: 10pt;" size="2"><font color="#000000">lopts</font></font></tt><font color="#000000">. 171 119 These lines only become active if a run on the parallel computer of 172 the HLRN (</font><tt><i><font style="font-size: 10pt;" size="2">ibmh</font></i></tt><font 173 color="#000000">) 174 on several <font color="#000000">(</font><tt><i><font 175 style="font-size: 10pt;" size="2"><font color="#000000">parallel</font></font></i></tt><font 176 color="#000000">) 120 the HLRN (</font><tt><i><font style="font-size: 10pt;" size="2">ibmh</font></i></tt><font color="#000000">) 121 on several <font color="#000000">(</font><tt><i><font style="font-size: 10pt;" size="2"><font color="#000000">parallel</font></font></i></tt><font color="#000000">) 177 122 </font>processors is started. The activation takes place when you 178 123 appropriately specify the <span style="font-weight: bold;">mrun</span> 179 options </font><tt><font color="#000000">-h</font></tt><font 180 color="#000000"> 181 and </font><tt><font color="#000000">-K</font></tt><font 182 color="#000000"> 124 options </font><tt><font color="#000000">-h</font></tt><font color="#000000"> 125 and </font><tt><font color="#000000">-K</font></tt><font color="#000000"> 183 126 (see below). This way, the validity domain can be limited also for all 184 127 other environment-variables. If no validity domain 185 128 is indicated then the given values of variables are valid on all 186 129 computers. </font> 187 </p> 188 <p style="line-height: 100%;">After the value assignment for the 189 variables the so-called error commands follow which have to begin with <tt><font 190 style="font-size: 11pt;" size="2">EC:</font></tt> 191 in the first column (comment lines begin with <tt>#</tt>). Directly 130 </p><p style="line-height: 100%;">After the value 131 assignment for the 132 variables the so-called error commands follow which have to begin with 133 “<tt><font style="font-size: 11pt;" size="2">EC:</font></tt>” 134 in the first column (comment lines begin with “<tt>#</tt>”). 135 Directly 192 136 after the colon Unix commands follow (korn shell syntax) which are 193 137 processed by <b>mrun</b> if errors arise during 194 the model run. The command described in the example (<tt><font 195 style="font-size: 10pt;" size="2">cat 138 the model run. The command described in the example (<tt><font style="font-size: 10pt;" size="2">cat 196 139 RUN_CONTROL</font></tt>) is executed thereby only on the 197 condition that errors during the execution of the model (<tt><font 198 style="font-size: 10pt;" size="2">execution</font></tt>) 199 arise. An <b>mrun </b>internal environment variable whichindicates140 condition that errors during the execution of the model (<tt><font style="font-size: 10pt;" size="2">execution</font></tt>) 141 arise. An <b>mrun </b>internal environment variable which 142 indicates 200 143 the 201 respective abort place in case of errors is <tt><a 202 href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#locat">locat</a></tt>. 144 respective abort place in case of errors is <tt><a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#locat">locat</a></tt>. 203 145 In order to determine the actual value of this variable at the 204 execution of <b>mrun</b> the <tt>$</tt> - prefix 205 must be protected by a \ since the configuration file has been 206 already interpreted once when reading in through <b>mrun</b> and the 146 execution of <b>mrun</b> the “<tt>$</tt>” 147 - prefix 148 must be protected by a “\” since the configuration 149 file has been 150 already interpreted once when reading in through <b>mrun</b> 151 and the 207 152 value from 208 <tt>locat</tt> would then supply the empty character string. If 153 <tt>locat</tt> would then supply the empty character 154 string. If 209 155 errors arise during the model run this command 210 156 copies the data written by the model up to then to the local file 211 157 <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a> 212 158 on the standard output where they can be checked after 213 job end.<font color="#000000"> RUN_CONTROL is an output file of the 159 job end.<font color="#000000"> RUN_CONTROL is an output 160 file of the 214 161 model which has to be copied according to the default configuration 215 162 file 216 163 (see below) after the end of the model run to a permanent file of the 217 164 user but this action would not be performed in case of errors 218 in the model run, so that the file content would be lost.</font> With 165 in the model run, so that the file content would be lost.</font> 166 With 219 167 the help of the error command one can secure it nevertheless. </p> 220 168 <p style="line-height: 100%;">Before and/or after … … 222 170 and/or output commands which are implemented before and/or after the 223 171 model run. </p> 224 <p style="line-height: 100%;">After the output commands<font 225 color="#000000"> 226 <font color="#000000">in the example file t</font>he so-called file 227 connection statements</font> <font color="#000000">follow </font>via 228 which tell <span style="font-weight: bold;">mrun</span> how to connect 172 <p style="line-height: 100%;">After the output commands<font color="#000000"> 173 <font color="#000000">in the example file t</font>he 174 so-called file 175 connection statements</font> <font color="#000000">follow 176 </font>via 177 which tell <span style="font-weight: bold;">mrun</span> 178 how to connect 229 179 the local files in the temporary working 230 180 directory of the model with the respective permanent files of the user. 231 <b>mrun</b> copies the input and output files in accordance with the 181 <b>mrun</b> copies the input and output files in accordance 182 with the 232 183 data in these connection statements. The file connection statements are 233 184 explained in detail in the <b>mrun</b> 234 description (<a 235 href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#chapter6.3">chapter 185 description (<a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#chapter6.3">chapter 236 186 6.3</a>, in German) and are described here only as far as being 237 187 necessary. A … … 243 193 the start of the line. In the second column the so-called file 244 194 attributes 245 are given. These determine whether the file is an input file (<tt><font 246 style="font-size: 10pt;" size="2">in</font></tt>) 247 or an output file (<tt><font size="2">out</font></tt>), whether output 248 files are to be transferred to the local computer of the user (<tt><font 249 style="font-size: 10pt;" size="2">tr</font></tt>) 250 or whether they are to be archived (<font size="2"><font 251 face="Cumberland, monospace">fl</font></font>). 252 If a file has several attributes then they are separated by a <font 253 color="#000000">colon 195 are given. These determine whether the file is an input file (<tt><font style="font-size: 10pt;" size="2">in</font></tt>) 196 or an output file (<tt><font size="2">out</font></tt>), 197 whether output 198 files are to be transferred to the local computer of the user (<tt><font style="font-size: 10pt;" size="2">tr</font></tt>) 199 or whether they are to be archived (<font size="2"><font face="Cumberland, monospace">fl</font></font>). 200 If a file has several attributes then they are separated by a <font color="#000000">colon 254 201 in each case .</font> </p> 255 <p style="line-height: 100%;">With the entries in the third column one 202 <p style="line-height: 100%;">With the entries in the 203 third column one 256 204 specifies the conditions under which a file connection statement 257 205 becomes active i.e. under … … 260 208 character strings registered in column 3 (again two or more character 261 209 strings have to be separated from each other by a colon) is 262 indicated within the mrun <b>call</b> by the option <a 263 href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Opt-r">-r</a>. 210 indicated within the mrun <b>call</b> by the option <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Opt-r">-r</a>. 264 211 Thus a call of the form </p> 265 <ul> 266 <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font 267 style="font-size: 10pt;" size="2">mrun - h ibmh -d abcde -r d3</font></pre> 268 </ul> 269 <p style="line-height: 100%;">would lead to the fact that the input 212 <ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">mrun - h ibmh -d abcde -r d3</font></pre></ul> 213 <p style="line-height: 100%;">would lead to the fact that 214 the input 270 215 file with the local name PARIN is made available and the output files 271 216 RUN_CONTROL and HEADER are copied to permanent files. The output 272 217 files PLOT1D_PAR and PLOT1D_DATA are not copied so that their 273 218 contents are not available to the user after the end of the job. If 274 these files are to be copied of <b>mrun</b> then the call must be</p> 275 <ul> 276 <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font 277 style="font-size: 10pt;" size="2">mrun -h ibmh -d abcde -r "d3 pr"</font></pre> 278 </ul> 279 <p style="line-height: 100%;">Instead of the option -r you can 219 these files are to be copied of <b>mrun</b> then the call 220 must be</p> 221 <ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">mrun -h ibmh -d abcde -r "d3 pr"</font></pre></ul> 222 <p style="line-height: 100%;">Instead of the option -r you 223 can 280 224 separately address the file connection statements for input and/or 281 225 output files with the options -i and -o. If one likes to make sure with … … 283 227 file all file connection statements are actually executed then 284 228 the call must be: </p> 285 <ul> 286 <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font 287 style="font-size: 10pt;" size="2">mrun -h ibmh -d abcde -i d3 -o "d3 pr"</font></pre> 288 </ul> 289 <p style="line-height: 100%;"><font color="#000000">The names of the 229 <ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">mrun -h ibmh -d abcde -i d3 -o "d3 pr"</font></pre></ul> 230 <p style="line-height: 100%;"><font color="#000000">The 231 names of the 290 232 local files assigned permanent files are build from the entries in 291 233 the 4th and 5th column of the file connection statements and the 292 value of the <span style="font-weight: bold;">mrun</span> option </font><tt><font 293 style="font-size: 10pt;" size="2"><font color="#000000">-d</font></font></tt><font 294 color="#000000"> 234 value of the <span style="font-weight: bold;">mrun</span> 235 option </font><tt><font style="font-size: 10pt;" size="2"><font color="#000000">-d</font></font></tt><font color="#000000"> 295 236 in the following way:</font><font color="#800000"> </font> 296 </p> 297 <ul> 298 <p style="line-height: 100%;">File name (inclusive path) = value of 299 the 4th column + value of the option <tt><font size="2">-d</font></tt> 300 + value of the 5th column.</p> 301 </ul> 302 <p style="line-height: 100%;">The 4th column contains the path name 303 whereby <tt><a 304 href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#fname">$fname</a></tt> 237 </p><ul> <p style="line-height: 100%;">File 238 name (inclusive path) = “value of 239 the 4th column” + “value of the option <tt><font size="2">-d</font></tt>” 240 + “value of the 5th column”.</p> 241 </ul><p style="line-height: 100%;">The 4th column 242 contains the path name 243 whereby <tt><a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#fname">$fname</a></tt> 305 244 is replaced by the value indicated for the option <tt><font size="2">-d</font></tt>. 306 245 The 5th column contains the so-called file name extension. The name 307 of the permanent file which was copied by <b>mrun</b> to the local 246 of the permanent file which was copied by <b>mrun</b> to 247 the local 308 248 file <tt>PARIN</tt> thereby reads: </p> 309 <ul> 310 <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font 311 style="font-size: 10pt;" size="2">~/palm/current_version/JOBS/abcde/INPUT/abcde_p3d.</font></pre> 312 </ul> 313 <p style="line-height: 100%;">In the same way the names of the 249 <ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">~/palm/current_version/JOBS/abcde/INPUT/abcde_p3d.</font></pre></ul> 250 <p style="line-height: 100%;">In the same way the names of 251 the 314 252 permanent files of the remaining <font color="#000000">file 315 253 connection statements </font>can be formed. </p> 316 <p style="line-height: 100%;">With this example configuration file 254 <p style="line-height: 100%;">With this example 255 configuration file 317 256 exactly one input file is copied into the temporary working directory 318 of the model. This file has the local name <a 319 href="chapter_3.4.html#PARIN">PARIN</a> 257 of the model. This file has the local name <a href="chapter_3.4.html#PARIN">PARIN</a> 320 258 and contains the steering parameters for the model and has to be 321 259 provided by the user for each model run. </p> 322 <p style="line-height: 100%;">The example configuration file also 323 instructs <b>mrun</b> to copy four output files of the model to 260 <p style="line-height: 100%;">The example configuration 261 file also 262 instructs <b>mrun</b> to copy four output files of the 263 model to 324 264 appropriate permanent files of the user at the end of the run. 325 There are timestep information (local file name <tt><a 326 href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a></tt>), 265 There are timestep information (local file name <tt><a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a></tt>), 327 266 the so-called header file, in which the values of the most selected 328 267 parameters for this run (<tt><a href="chapter_3.4.html#HEADER">HEADER</a></tt>) … … 330 269 vertical profiles 331 270 (<tt><a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a></tt>) 332 and an associated parameter file (<tt><a 333 href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a></tt>), 334 which can be used as input files for the plot program <a 335 href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>. 271 and an associated parameter file (<tt><a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a></tt>), 272 which can be used as input files for the plot program <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>. 336 273 A model run does not presuppose neither the file connection statements 337 274 for … … 339 276 them usually the data produced by the model 340 277 are lost after the end of the model run! </p> 341 <p style="line-height: 100%;">As already mentioned the configuration 278 <p style="line-height: 100%;">As already mentioned the 279 configuration 342 280 file offers a variety of further possibilities to steer the 343 281 execution of the model run. Some of them are described in the next 344 282 chapter. Same applies to possible other options of the <b>mrun</b> 345 call. For these please refer to the <a 346 href="http://www.muk.uni-hannover.de/%7Eraasch/Software/mrun_beschreibung.html">mrun</a> 347 documentation (in German). An <b>mrun </b>call for theexecution of a283 call. For these please refer to the <a href="http://www.muk.uni-hannover.de/%7Eraasch/Software/mrun_beschreibung.html">mrun</a> 284 documentation (in German). An <b>mrun </b>call for the 285 execution of a 348 286 model run 349 287 on several processors on the IBM Regatta "hanni" of the HLRN must be 350 288 supplemented by the following options in each case: </p> 351 <ul> 352 <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font 353 style="font-size: 10pt;" size="2">mrun - K parallel -X 354 -t 355 -m 356 </font></pre> 357 </ul> 358 <p style="line-height: 100%;">Only the indication of <tt><font 359 style="font-size: 11pt;" size="2">-K 360 parallel</font></tt> causes the parallel execution of the run on 289 <ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">mrun - K parallel -X … -t … -m …</font></pre></ul> 290 <p style="line-height: 100%;">Only the indication of <tt><font style="font-size: 11pt;" size="2">-K 291 parallel</font></tt> causes the parallel execution of the 292 run on 361 293 several processors (otherwise a scalar execution on one processor is 362 294 accomplished). In addition to this the number of the 363 295 processing elements which shall be used has to be pre-scribed with the 364 option <tt><font style="font-size: 10pt;" size="2">-X</font> </tt><font365 size="2">(</font><font style="font-size: 10pt;" size="2">e.g.366 </font><tt><font style="font-size: 10pt;" size="2">-X 4</font></tt><font367 size="2">).</font>296 option <tt><font style="font-size: 10pt;" size="2">-X</font> 297 </tt><font size="2">(</font><font style="font-size: 10pt;" size="2">e.g. 298 </font><tt><font style="font-size: 10pt;" size="2">-X 299 4</font></tt><font size="2">).</font> 368 300 In each case the permitted CPU time in seconds and the required memory 369 size in MB must be indicated by the options <tt><font 370 style="font-size: 11pt;" size="2">-t</font></tt> 301 size in MB must be indicated by the options <tt><font style="font-size: 11pt;" size="2">-t</font></tt> 371 302 and <tt><font style="font-size: 11pt;" size="2">-m</font></tt>, 372 303 respectively<font face="Thorndale, serif">.</font> 373 304 Alternatively, these can be set by the appropriate environment 374 305 variables in the configuration file: </p> 375 <blockquote style="line-height: 100%;"><tt><font 376 style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">% 377 memory <i>1630</i> ibmh parallel</font></font></tt><font 378 style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br> 379 </font></font><tt><font style="font-size: 10pt;" size="2"><font 380 face="Cumberland, monospace">% 306 <blockquote style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">% 307 memory <i>1630</i> ibmh parallel</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br> </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">% 381 308 cputime <i>1000</i> ibmh parallel</font></font></tt></blockquote> 382 <p style="line-height: 100%;">The values indicated there can be383 overridden with the values of the options <tt><font 384 style="font-size: 10pt;" size="2">-t</font></tt>309 <p style="line-height: 100%;">The values indicated there 310 can be 311 overridden with the values of the options <tt><font style="font-size: 10pt;" size="2">-t</font></tt> 385 312 and/or <tt><font style="font-size: 10pt;" size="2">-m</font></tt>, 386 313 respectivly. </p> 387 <hr> 388 <p style="line-height: 100%;"><br> 389 <font color="#000080"><font color="#000080"><a href="chapter_3.1.html"><font 390 color="#000080"><img src="left.gif" name="Grafik1" align="bottom" 391 border="2" height="32" width="32"></font></a><a href="index.html"><font 392 color="#000080"><img src="up.gif" name="Grafik2" align="bottom" 393 border="2" height="32" width="32"></font></a><a href="chapter_3.3.html"><font 394 color="#000080"><img src="right.gif" name="Grafik3" align="bottom" 395 border="2" height="32" width="32"></font></a></font></font></p> 396 <p style="line-height: 100%;"><i>Last change: </i> 14/04/05 (SR)</p> 397 </body> 398 </html> 314 <hr><p style="line-height: 100%;"><br> 315 <font color="#000080"><font color="#000080"><a href="chapter_3.1.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.3.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font></p><p style="line-height: 100%;"><i>Last change: </i> 316 $Id$</p> 317 </body></html>
Note: See TracChangeset
for help on using the changeset viewer.