[5] | 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.0</title> |
---|
| 7 | <meta name="GENERATOR" content="StarOffice 7 (Win32)"> |
---|
| 8 | <meta name="AUTHOR" content="Marcus Oliver Letzel"> |
---|
| 9 | <meta name="CREATED" content="20040723;15213734"> |
---|
| 10 | <meta name="CHANGED" content="20041112;13170538"> |
---|
| 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 | <h2 style="font-style: normal; line-height: 100%;"><font size="4">3.0 |
---|
| 20 | Execution of model runs</font></h2> |
---|
| 21 | <p style="line-height: 100%;">Given that the model was |
---|
| 22 | installed by the user (look at <a href="chapter_5.0.html">chapter |
---|
| 23 | 5.0</a>) and that it is clear, which phenomenon is to be simulated, |
---|
| 24 | there is a whole set of questions which must be answered before |
---|
| 25 | executing |
---|
| 26 | the actual application run, e.g.: </p> |
---|
| 27 | <ul> |
---|
| 28 | <li> |
---|
| 29 | <p |
---|
| 30 | style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">How |
---|
| 31 | large does the model domain have to be and what grid size does |
---|
| 32 | phenomenon to be simulated require? </p> |
---|
| 33 | </li> |
---|
| 34 | <li> |
---|
| 35 | <p |
---|
| 36 | style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">How |
---|
| 37 | long is the time which should be simulated, i.e. which typical time |
---|
| 38 | scale does the phenomenon have? </p> |
---|
| 39 | </li> |
---|
| 40 | <li> |
---|
| 41 | <p |
---|
| 42 | style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">Which |
---|
| 43 | boundary conditions and initial conditions are to be selected? </p> |
---|
| 44 | </li> |
---|
| 45 | <li> |
---|
| 46 | <p style="font-style: normal; line-height: 100%;">Which model |
---|
| 47 | output data are necessary at which points in time, in order to be able |
---|
| 48 | to analyze the phenomenon afterwards? </p> |
---|
| 49 | </li> |
---|
| 50 | </ul> |
---|
| 51 | <p style="line-height: 100%;">The answers to these questions |
---|
| 52 | substantially determine the choice of values for the most important |
---|
| 53 | model parameters, with which the model run is steered. All possible |
---|
| 54 | parameters are described in chapters <a href="chapter_4.1.html">4.1</a>, |
---|
| 55 | <a href="chapter_4.2.html">4.2</a> |
---|
| 56 | and <a href="chapter_4.3.html">4.3</a>. |
---|
| 57 | The basic steering of the model with these parameters is explained in |
---|
| 58 | the introduction to <a href="chapter_4.0.html">chapter |
---|
| 59 | 4</a>. The user will rarely use all model parameters, since many are |
---|
| 60 | preset with consistent default values and therefore do not have to be |
---|
| 61 | changed by the user. Some of the most important parameters are not |
---|
| 62 | preset with default values and must be adjusted by the user in each |
---|
| 63 | case. Such a typical, minimum parameter set is described in <a |
---|
| 64 | href="chapter_4.4.html">chapter |
---|
| 65 | 4.4</a>. For the subsequent analysis of model runs, graphical |
---|
| 66 | visualization of model data is particularly important. <a |
---|
| 67 | href="chapter_4.5.html">Chapter |
---|
| 68 | 4.5</a> describes, how such outputs are produced with the model. </p> |
---|
| 69 | <p style="line-height: 100%;">The selected parameters and their values |
---|
| 70 | have to be supplied to the model as an input file. The |
---|
| 71 | structure of this file is described in the introduction to <a |
---|
| 72 | href="chapter_4.0.html">chapter |
---|
| 73 | 4</a>. The data, produced by the model, are located in a number of |
---|
| 74 | different output files. The model works with relative file names |
---|
| 75 | (i.e. without absolute path information). Thus all input and output |
---|
| 76 | files are |
---|
| 77 | expected and put in the directory, in which the actual model (the |
---|
| 78 | executable program created from the FORTRAN source code) is started |
---|
| 79 | (but also see next paragraph). |
---|
| 80 | All user-relevant input and output files are described in <a |
---|
| 81 | href="chapter_3.4.html">chapter |
---|
| 82 | 3.4</a>. </p> |
---|
| 83 | <p style="line-height: 100%;">The actual model (the executable |
---|
| 84 | program) is not started directly via the user, but with the help of |
---|
| 85 | the shell script <a |
---|
| 86 | href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun</a>,which |
---|
| 87 | can be called by the user. This script takes over the entire pre- and |
---|
| 88 | postprocessing work, which is necessary for a model run. In addition |
---|
| 89 | to this, it generates e.g. automatically batch jobs for model runs on |
---|
| 90 | remote computers, provides for the appropriate file transfers of the |
---|
| 91 | input and output files to these computers, secures data on existing |
---|
| 92 | archives systems, starts if necessary restart jobs, and much more. |
---|
| 93 | <span style="font-weight: bold;">mrun</span> allows to specify |
---|
| 94 | individual path names for each simulation and |
---|
| 95 | for the different types of input/output files. The start of model runs |
---|
| 96 | with <b>mrun</b> is described in <a href="chapter_3.1.html">chapter |
---|
| 97 | 3.1</a>. </p> |
---|
| 98 | <p style="line-height: 100%;">The implementation of user code |
---|
| 99 | extensions in |
---|
| 100 | the model is made possible by a set of defined interfaces. You will |
---|
| 101 | find references to the programming of such extensions in <a |
---|
| 102 | href="chapter_3.5.html">chapter |
---|
| 103 | 3.5</a>. Frequently errors arise during the execution of the model |
---|
| 104 | after such changes, which can often be found only by interactive |
---|
| 105 | model steering and error tracing (debugging), which are described in |
---|
| 106 | <a href="chapter_3.6.html">chapter |
---|
| 107 | 3.6</a>. </p> |
---|
| 108 | <hr> |
---|
| 109 | <p style="font-style: normal; line-height: 100%;"><br> |
---|
| 110 | <font color="#000080"><font color="#000080"><a href="chapter_2.0.html"><font |
---|
| 111 | color="#000080"><img src="left.gif" name="Grafik1" align="bottom" |
---|
| 112 | border="2" height="32" width="32"></font></a><a href="index.html"><font |
---|
| 113 | color="#000080"><img src="up.gif" name="Grafik2" align="bottom" |
---|
| 114 | border="2" height="32" width="32"></font></a><a href="chapter_3.1.html"><font |
---|
| 115 | color="#000080"><img src="right.gif" name="Grafik3" align="bottom" |
---|
| 116 | border="2" height="32" width="32"></font></a></font></font> |
---|
| 117 | <br> |
---|
| 118 | </p> |
---|
| 119 | <p style="font-style: normal; line-height: 100%;"><span |
---|
| 120 | style="font-style: italic;">Last change:</span> 14/04/05 (SR)<br> |
---|
| 121 | </p> |
---|
| 122 | </body> |
---|
| 123 | </html> |
---|