source: palm/trunk/DOC/app/chapter_3.0.html @ 62

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

Id string added to all html files

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