Changeset 62 for palm/trunk
- Timestamp:
- Mar 13, 2007 2:52:40 AM (18 years ago)
- Location:
- palm/trunk/DOC
- Files:
-
- 31 edited
Legend:
- Unmodified
- Added
- Removed
-
palm/trunk/DOC/app/chapter_1.0.html
r54 r62 1 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> 2 <html> 3 <head> 4 <meta content="text/html; charset=windows-1252" 5 http-equiv="CONTENT-TYPE"> 6 <title>PALM chapter 1.0</title> 7 <meta content="StarOffice 7 (Win32)" name="GENERATOR"> 8 <meta content="Marcus Oliver Letzel" name="AUTHOR"> 9 <meta content="20040719;13375546" name="CREATED"> 10 <meta content="20041112;13163393" name="CHANGED"> 11 <meta content="parallel LES model" name="KEYWORDS"> 12 <style> 13 <!-- 14 @page { size: 21cm 29.7cm } 15 --> 16 </style> 17 </head> 18 <body lang="de-DE" dir="ltr"> 19 <h2 style="line-height: 100%;"><font size="4">1.0 Introduction</font></h2> 20 <p style="line-height: 100%;">This documentation wants to give 2 <html><head> 3 <meta content="text/html; charset=windows-1252" http-equiv="CONTENT-TYPE"><title>PALM chapter 1.0</title> <meta content="StarOffice 7 (Win32)" name="GENERATOR"> <meta content="Marcus Oliver Letzel" name="AUTHOR"> <meta content="20040719;13375546" name="CREATED"> <meta content="20041112;13163393" name="CHANGED"> <meta content="parallel LES model" name="KEYWORDS"> <style> 4 <!-- 5 @page { size: 21cm 29.7cm } 6 --> 7 </style></head> 8 9 <body style="direction: ltr;" lang="de-DE"><h2 style="line-height: 100%;"><font size="4">1.0 10 Introduction</font></h2> 11 <p style="line-height: 100%;">This documentation wants to 12 give 21 13 assistance how to carry out runs with the large eddy simulation 22 model <span 23 style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">PALM.</span> 14 model <span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">PALM.</span> 24 15 It contains 25 16 <font color="#000000">instructions</font><font color="#800000"> </font>for 26 17 the installation of the model (<a href="chapter_5.0.html">chapter 27 5.0</a>), for the practical execution of application runs (<a 28 href="chapter_3.0.html">chapter 29 3.0</a>) and for the steering of the model by parameters (<a 30 href="chapter_4.0.html">chapter 18 5.0</a>), for the practical execution of application runs (<a href="chapter_3.0.html">chapter 19 3.0</a>) and for the steering of the model by parameters (<a href="chapter_4.0.html">chapter 31 20 4.0</a>). New users should first of all read <a href="chapter_2.0.html">chapters 32 21 2.0</a> and <a href="chapter_3.0.html">3.0</a> 33 22 (up to and including <a href="chapter_3.5.html">3.5</a>). 34 23 </p> 35 <p style="line-height: 100%;"><b>This documentation does not explain 36 the <font color="#000000">mathematical,</font> numerical and physical 24 <p style="line-height: 100%;"><b>This documentation 25 does not explain 26 the <font color="#000000">mathematical,</font> 27 numerical and physical 37 28 background of large eddy simulation models and it also does not 38 29 provide appropriate meteorological background knowledge. Good 39 30 knowledge concerning this is presupposed and is indispensable for a 40 31 successful application of the model.</b> In addition to this, 41 knowledge of the operating system<span 42 style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"> 43 Unix, </span>the <span 44 style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">Queueing 45 System (NQS, PBS, Load Leveler, etc.)</span> to generate batch jobs, 46 the basic functionality of <font color="#000000">parallel computers 47 </font>and the programming language <span 48 style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">FORTRAN90 32 knowledge of the operating system<span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"> 33 Unix, </span>the <span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">Queueing 34 System (NQS, PBS, Load Leveler, etc.)</span> to generate batch 35 jobs, 36 the basic functionality of <font color="#000000">parallel 37 computers 38 </font>and the programming language <span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">FORTRAN90 49 39 (particularly</span>, if code extensions are to be written by the 50 40 user) are presupposed. Programming user-defined software usually 51 41 requires exact knowledge of the internal model structure. First insight 52 herei<span 53 style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">n 42 herei<span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">n 54 43 <font color="#000000">is 55 44 given</font></span> in <a href="chapter_2.0.html">chapter 56 45 2.0</a> and in the <a href="../tec/index.html">technical/numerical 57 46 documentation</a>. The information obtained there is usually not 58 <font color="#000000">sufficient</font> and has to be accompanied by59 detailed study of the source code of the model. A<span 60 style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">dditional47 <font color="#000000">sufficient</font> and has to 48 be accompanied by 49 detailed study of the source code of the model. A<span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">dditional 61 50 </span>experience in parallel programming with the 62 message passing interface<span 63 style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"> 51 message passing interface<span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"> 64 52 (MPI)</span> maybe presupposed. </p> 65 <p style="line-height: 100%;">A documentation lives on criticism and 66 suggestions by users. T<font color="#000000">hi</font>s is expressly 53 <p style="line-height: 100%;">A documentation lives on 54 criticism and 55 suggestions by users. T<font color="#000000">hi</font>s 56 is expressly 67 57 requested. Please contact the PALM group 68 (<span 69 style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">see 70 <a 71 href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PALM_group.html#0">members</a></span>). 58 (<span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">see 59 <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PALM_group.html#0">members</a></span>). 72 60 The model documentation is regularly maintained and brought up-to-date 73 61 by the PALM group. The date of the last code … … 75 63 documentation. <br> 76 64 77 </p> 78 <hr><font color="#000080"><font color="#000080"><br> 79 <a href="index.html"><font color="#000080"><img width="32" height="32" 80 border="2" align="bottom" name="Grafik1" src="up.gif"></font></a><a 81 href="chapter_2.0.html"><font color="#000080"><img width="32" 82 height="32" border="2" align="bottom" name="Grafik2" src="right.gif"></font></a></font></font><br> 83 <br> 84 <span style="font-style: italic;">Last change:</span> 14/04/05 (SR)<br> 85 <br> 86 </body> 87 </html> 65 </p><hr><font color="#000080"><font color="#000080"><br> 66 <a href="index.html"><font color="#000080"><img name="Grafik1" src="up.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_2.0.html"><font color="#000080"><img name="Grafik2" src="right.gif" align="bottom" border="2" height="32" width="32"></font></a></font></font><br><br> 67 <span style="font-style: italic;">Last change:</span> 68 $Id$<br> 69 <br></body></html> -
palm/trunk/DOC/app/chapter_2.0.html
r54 r62 1 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> 2 <html> 3 <head> 4 <meta content="text/html; charset=windows-1252" 5 http-equiv="CONTENT-TYPE"> 6 <title>PALM chapter 2.0</title> 7 <meta content="StarOffice 7 (Win32)" name="GENERATOR"> 8 <meta content="Marcus Oliver Letzel" name="AUTHOR"> 9 <meta content="20040719;14534028" name="CREATED"> 10 <meta content="20041117;10385730" name="CHANGED"> 11 <meta content="parallel LES model" name="KEYWORDS"> 12 <style> 13 <!-- 14 @page { size: 21cm 29.7cm } 15 --> 16 </style> 17 </head> 18 <body lang="en-US" dir="ltr"> 19 <h2 style="line-height: 100%;"><font size="4">2.0 Basic techniques of 2 <html><head> 3 <meta content="text/html; charset=windows-1252" http-equiv="CONTENT-TYPE"><title>PALM chapter 2.0</title> <meta content="StarOffice 7 (Win32)" name="GENERATOR"> <meta content="Marcus Oliver Letzel" name="AUTHOR"> <meta content="20040719;14534028" name="CREATED"> <meta content="20041117;10385730" name="CHANGED"> <meta content="parallel LES model" name="KEYWORDS"> <style> 4 <!-- 5 @page { size: 21cm 29.7cm } 6 --> 7 </style></head> 8 9 <body style="direction: ltr;" lang="en-US"><h2 style="line-height: 100%;"><font size="4">2.0 10 Basic techniques of 20 11 the LES model and its parallelization </font> 21 </h2> 22 <p style="line-height: 100%;">LES modelsgenerally permit the12 </h2><p style="line-height: 100%;">LES models 13 generally permit the 23 14 simulation of turbulent flows, whereby those eddies, that carry the 24 15 main energy are resolved by the numerical grid. Only the … … 28 19 simulated directly (they are explicitly resolved) and their effects are 29 20 represented by the advection terms. </p> 30 <p style="font-style: normal; line-height: 100%;">PALM is based on the 21 <p style="font-style: normal; line-height: 100%;">PALM is 22 based on the 31 23 non-hydrostatic incompressible Boussinesq equations. It contains a 32 24 water cycle with cloud formation and takes into account infrared 33 25 radiative cooling in cloudy conditions. The model has six prognostic 34 quantities in total u,v,w, liquid water potential temperature 35 <font face="Thorndale, serif">Θ</font><sub>l </sub>(BETTS, 26 quantities in total – u,v,w, liquid water potential 27 temperature 28 <font face="Thorndale, serif">Θ</font><sub>l 29 </sub>(BETTS, 36 30 1973), total water content q and subgrid-scale turbulent kinetic energy 37 31 e. The … … 45 39 1993). The water cycle is closed by using a simplified version of 46 40 KESSLERs scheme (KESSLER, 1965; 1969) to parameterize precipitation 47 processes (M ÜLLER and CHLOND, 1996). Incompressibility is41 processes (MÜLLER and CHLOND, 1996). Incompressibility is 48 42 applied by means of a Poisson equation for pressure, which is solved 49 43 with a direct method (SCHUMANN and SWEET, 1988). The Poisson equation … … 58 52 horizontal directions. At the lower surface, either temperature/ 59 53 humidity or their respective fluxes can be prescribed. </p> 60 <p style="font-style: normal; line-height: 100%;">The advection terms 54 <p style="font-style: normal; line-height: 100%;">The 55 advection terms 61 56 are treated by the scheme proposed by PIACSEK and WILLIAMS (1970), 62 57 which conserves the integral of linear and quadratic quantities up to … … 66 61 with the third-order Runge-Kutta scheme. A second-order Runge-Kutta 67 62 scheme, a leapfrog scheme and an Euler scheme are also implemented.</p> 68 <p style="line-height: 100%;">By default, the time step is computed 63 <p style="line-height: 100%;">By default, the time step is 64 computed 69 65 with respect to the different criteria (CFL, diffusion) and adapted 70 66 automatically. In case of a non-zero geostrophic 71 67 wind the coordinate system can be moved along with the mean wind in 72 68 order to maximize the time step (Galilei-Transformation). </p> 73 <p style="font-style: normal; line-height: 100%;">In principle a model 69 <p style="font-style: normal; line-height: 100%;">In 70 principle a model 74 71 run is carried out in the following way: After reading the control 75 72 parameters given by the user, all prognostic variables are … … 90 87 corrected with the help of the pressure solver. Following this, all 91 88 diagnostic turbulence quantities including possible 92 Prandtl-layer quantities are computed. At the end of a time89 Prandtl-layer–quantities are computed. At the end of a time 93 90 step the data output requested by the user is made 94 91 (e.g. statistic of analyses for control purposes or profiles and/or 95 92 graphics data). If the given end-time was reached, binary data maybe 96 93 be saved for restart. </p> 97 <p style="font-style: normal; line-height: 100%;">The model is based 94 <p style="font-style: normal; line-height: 100%;">The 95 model is based 98 96 on the originally non-parallel LES model which has been operated at the 99 97 institute since 1989 … … 109 107 Users can choose between a two- and a one-dimensional domain 110 108 decomposition. A 1D-decomposition is preferred on machines with a 111 slow network interconnection. In case of a 1D-decomposition, the 109 slow network interconnection. In case of a 1D-decomposition, 110 the 112 111 grid points along x direction are 113 112 distributed among the individual processors, but in y- and z-direction 114 113 all respective grid points belong to the same PE. </p> 115 <p style="line-height: 100%;">The calculation of central differences or 114 <p style="line-height: 100%;">The calculation of central 115 differences or 116 116 non-local arithmetic operations (e.g. global 117 117 sums, FFT) demands communication and an appropriate data exchange … … 126 126 y-direction, the data which lie distributed on the individual central 127 127 processing elements, have to be collected and/or relocated before. 128 This happens by means of the routine <tt>MPI_ALLTOALLV</tt>. Certain 128 This happens by means of the routine <tt>MPI_ALLTOALLV</tt>. 129 Certain 129 130 global operations like e.g. the search for absolute maxima or minima 130 131 within the 3D-arrays likewise require the employment of special MPI 131 132 routines (<tt>MPI_ALLREDUCE</tt>). </p> 132 <p style="line-height: 100%;">Further details of the internal model 133 <p style="line-height: 100%;">Further details of the 134 internal model 133 135 structure are described in the <a href="../tec/index.html">technical/numerical 134 136 documentation</a>. <br> 135 137 </p> 136 <hr><font color="#000080"><font color="#000080"><br> 137 <a href="chapter_1.0.html"><font color="#000080"><img width="32" 138 height="32" border="2" align="bottom" name="Grafik1" src="left.gif"></font></a><a 139 href="index.html"><font color="#000080"><img width="32" height="32" 140 border="2" align="bottom" name="Grafik2" src="up.gif"></font></a><a 141 href="chapter_3.0.html"><font color="#000080"><img width="32" 142 height="32" border="2" align="bottom" name="Grafik3" src="right.gif"></font></a><br> 143 </font></font><br> 144 <p style="line-height: 100%;"><span style="font-style: italic;">Last 145 change: </span>14/04/05 (SR)<font color="#000080"><font color="#000080"><br> 146 </font></font></p> 147 </body> 148 </html> 138 <hr><font color="#000080"><font color="#000080"><br><a href="chapter_1.0.html"><font color="#000080"><img name="Grafik1" src="left.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img name="Grafik2" src="up.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_3.0.html"><font color="#000080"><img name="Grafik3" src="right.gif" align="bottom" border="2" height="32" width="32"></font></a><br> 139 </font></font><br><p style="line-height: 100%;"><span style="font-style: italic;">Last 140 change: </span>$Id$<font color="#000080"><font color="#000080"><br> 141 </font></font></p></body></html> -
palm/trunk/DOC/app/chapter_3.0.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.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 2 <html><head> 3 <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM 4 chapter 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 20 11 Execution of model runs</font></h2> 21 12 <p style="line-height: 100%;">Given that the model was 22 13 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, 14 5.0</a>) and that it is clear, which phenomenon is to be 15 simulated, 24 16 there is a whole set of questions which must be answered before 25 17 executing 26 18 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 19 <ul> <li> <p style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">How 31 20 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 21 phenomenon to be simulated require? </p> </li> <li> 22 <p style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">How 37 23 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 24 scale does the phenomenon have? </p> </li> <li> <p style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">Which 43 25 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 26 </li> <li> <p style="font-style: normal; line-height: 100%;">Which model 47 27 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 28 to analyze the phenomenon afterwards? </p> </li> 29 </ul><p style="line-height: 100%;">The answers to 30 these questions 52 31 substantially determine the choice of values for the most important 53 32 model parameters, with which the model run is steered. All possible … … 57 36 The basic steering of the model with these parameters is explained in 58 37 the introduction to <a href="chapter_4.0.html">chapter 59 4</a>. The user will rarely use all model parameters, since many are 38 4</a>. The user will rarely use all model parameters, since many 39 are 60 40 preset with consistent default values and therefore do not have to be 61 41 changed by the user. Some of the most important parameters are not 62 42 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 43 case. Such a typical, minimum parameter set is described in <a href="chapter_4.4.html">chapter 65 44 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 45 visualization of model data is particularly important. <a href="chapter_4.5.html">Chapter 68 46 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 47 <p style="line-height: 100%;">The selected parameters and 48 their values 70 49 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">chapter73 4</a>. The data, produced by the model, are located in a numberof50 structure of this file is described in the introduction to <a href="chapter_4.0.html">chapter 51 4</a>. The data, produced by the model, are located in a number 52 of 74 53 different output files. The model works with relative file names 75 54 (i.e. without absolute path information). Thus all input and output … … 78 57 executable program created from the FORTRAN source code) is started 79 58 (but also see next paragraph). 80 All user-relevant input and output files are described in <a 81 href="chapter_3.4.html">chapter 59 All user-relevant input and output files are described in <a href="chapter_3.4.html">chapter 82 60 3.4</a>. </p> 83 <p style="line-height: 100%;">The actual model (the executable 61 <p style="line-height: 100%;">The actual model (the 62 executable 84 63 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 64 the shell script <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun</a>,which 87 65 can be called by the user. This script takes over the entire pre- and 88 66 postprocessing work, which is necessary for a model run. In addition … … 91 69 input and output files to these computers, secures data on existing 92 70 archives systems, starts if necessary restart jobs, and much more. 93 <span style="font-weight: bold;">mrun</span> allows to specify 71 <span style="font-weight: bold;">mrun</span> allows 72 to specify 94 73 individual path names for each simulation and 95 74 for the different types of input/output files. The start of model runs 96 75 with <b>mrun</b> is described in <a href="chapter_3.1.html">chapter 97 76 3.1</a>. </p> 98 <p style="line-height: 100%;">The implementation of user code 77 <p style="line-height: 100%;">The implementation of user 78 code 99 79 extensions in 100 80 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 themodel81 find references to the programming of such extensions in <a href="chapter_3.5.html">chapter 82 3.5</a>. Frequently errors arise during the execution of the 83 model 104 84 after such changes, which can often be found only by interactive 105 85 model steering and error tracing (debugging), which are described in 106 86 <a href="chapter_3.6.html">chapter 107 87 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> 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$<br> 92 </p></body></html> -
palm/trunk/DOC/app/chapter_3.1.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.1</title> 7 <meta name="GENERATOR" content="StarOffice 7 (Win32)"> 8 <meta name="AUTHOR" content="Marcus Oliver Letzel"> 9 <meta name="CREATED" content="20040806;13565279"> 10 <meta name="CHANGED" content="20040806;13575492"> 11 <meta name="KEYWORDS" content="parallel LES model"> 12 </head> 13 <body dir="ltr" lang="de-DE"> 14 <h3 style="line-height: 100%;">3.1 Job control with mrun</h3> 15 <p style="line-height: 100%;">The start of model runs in principle 16 takes place via executing the shell script <a 17 href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun.</a> 2 <html><head> 3 <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM 4 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> 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 8 principle 9 takes place via executing the shell script <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun.</a> 18 10 With this script it is possible to operate the model both 19 11 interactively and in batch mode. Batch operation is possible on the … … 23 15 described, because this represents the usual mode of operation due to 24 16 the large computing time requirements of the model. The interactive 25 execution differs only in some points and is described in <a 26 href="chapter_3.6.html">chapter 17 execution differs only in some points and is described in <a href="chapter_3.6.html">chapter 27 18 3.6</a>. </p> 28 <p style="line-height: 100%;">By the call of <b>mrun </b>a complete 19 <p style="line-height: 100%;">By the call of <b>mrun 20 </b>a complete 29 21 batch job is produced, transferred to the user determined remote 30 22 computer … … 32 24 After processing of the job, the so-called job protocol is sent back 33 25 to the local computer of the user (the local computer is the 34 computer, on which the user calls <b>mrun</b>). The following actions 26 computer, on which the user calls <b>mrun</b>). The 27 following actions 35 28 are implemented by the job, amongst other: </p> 36 <ul> 37 <li> 38 <p style="margin-bottom: 0cm; line-height: 100%;">Change to a 39 temporary working directory. </p> 40 </li> 41 <li> 42 <p style="margin-bottom: 0cm; line-height: 100%;">The input files 29 <ul> <li> <p style="margin-bottom: 0cm; line-height: 100%;">Change to a 30 temporary working directory. </p> </li> <li> <p style="margin-bottom: 0cm; line-height: 100%;">The input 31 files 43 32 needed by the model are copied into this directory. These files are 44 transferred from the local computer. </p> 45 </li> 46 <li> 47 <p style="margin-bottom: 0cm; line-height: 100%;">Execute the 48 model. </p> 49 </li> 50 <li> 51 <p style="margin-bottom: 0cm; line-height: 100%;">Copy the output 33 transferred from the local computer. </p> </li> <li> 34 <p style="margin-bottom: 0cm; line-height: 100%;">Execute 35 the 36 model. </p> </li> <li> <p style="margin-bottom: 0cm; line-height: 100%;">Copy the 37 output 52 38 files produced by the model into the directories determined by the user 53 39 (these are also allowed to lie on the local computer). Depending on the 54 40 choice of the user, the files may also be saved on an archiving system 55 (if existing). </p> 56 </li> 57 <li> 58 <p style="margin-bottom: 0cm; line-height: 100%;">Delete the 59 temporary working direction. </p> 60 </li> 61 <li> 62 <p style="line-height: 100%;">Transfer the job protocol to the 63 local computer. </p> 64 </li> 65 </ul> 66 <p style="line-height: 100%;">From this list it becomes clear that two 67 of the substantial functions of <b>mrun</b> are the supply of input 41 (if existing). </p> </li> <li> <p style="margin-bottom: 0cm; line-height: 100%;">Delete the 42 temporary working direction. </p> </li> <li> <p style="line-height: 100%;">Transfer the job protocol to the 43 local computer. </p> </li> 44 </ul><p style="line-height: 100%;">From this list it 45 becomes clear that two 46 of the substantial functions of <b>mrun</b> are the supply 47 of input 68 48 files for the model and the storage of output files produced by the 69 49 model. The model exclusively works with so-called local files, which 70 lie in the temporary working directory created by <b>mrun.</b> The 71 local names of these files are determined by the model 50 lie in the temporary working directory created by <b>mrun.</b> 51 The 52 “local” names of these files are determined by the 53 model 72 54 (in the appropriate OPEN instructions). In <a href="chapter_3.4.html">chapter 73 55 3.4</a> all possible input and output filenames are specified. In … … 77 59 stored there. The directory names are arbitrary. The actual file name 78 60 (without path) of these input and output files is specified by an 79 option of <b>mrun</b>. All input and output files of the model 80 receive this file name (e.g. <i>abcde</i>), but each individual file 81 is still provided with an extension (e.g. <i>abcde_par</i>, etc. 82 <i>abcde_dat</i>) - otherwise the files would not be distinguishable. 61 option of <b>mrun</b>. All input and output files of the 62 model 63 receive this file name (e.g. <i>abcde</i>), but each 64 individual file 65 is still provided with an extension (e.g. <i>abcde_par</i>, 66 etc. 67 <i>abcde_dat</i>) - otherwise the files would not be 68 distinguishable. 83 69 The linkage of local file names with the names of the permanent 84 70 directories and the file name extensions takes place in a 85 configuration file, which <b>mrun</b> expects to find in the 71 configuration file, which <b>mrun</b> expects to find in 72 the 86 73 respective current working directory of the user. A detailed 87 74 description of this configuration file - which still offers a variety 88 of further functions is found in the 89 documentation of the shell script <a 90 href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun</a> 75 of further functions – is found in the 76 documentation of the shell script <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun</a> 91 77 (sorry: this is only available in German, so far. If you think that you 92 78 would profit from an English version, please give a message to the PALM … … 94 80 In the next chapter a simple example of a minimum configuration file 95 81 is described. </p> 96 <p style="line-height: 100%;">A simple call of <b>mrun</b> could read 82 <p style="line-height: 100%;">A simple call of <b>mrun</b> 83 could read 97 84 as follows: </p> 98 <ul> 99 <p style="line-height: 100%;"><tt>mrun - h <i>ibmh</i> -d <i>abcde</i></tt></p> 100 </ul> 101 <p style="line-height: 100%;">The model is started by option -<tt>h 102 <i>ibmh</i></tt> on the IBM Regatta hanni at the HLRN, i.e. on the 85 <ul> <p style="line-height: 100%;"><tt>mrun - 86 h <i>ibmh</i> -d <i>abcde</i></tt></p> 87 </ul><p style="line-height: 100%;">The model is 88 started by option -<tt>h 89 <i>ibmh</i></tt> on the IBM Regatta hanni at the 90 HLRN, i.e. on the 103 91 local computer a batch job is generated, transferred to the remote 104 92 computer (IBM) and submitted to a suitable queue of the queuing system. 105 93 With the 106 option <tt>-d</tt> the so-called basis file name (<i>abcde</i>) is 94 option <tt>-d</tt> the so-called basis file name (<i>abcde</i>) 95 is 107 96 specified, from which, together with the path names and file name 108 97 extensions, the complete file names (including the path) of the 109 permanent input and output files are <font color="#000000">formed.</font><font 110 color="#800000"> 98 permanent input and output files are <font color="#000000">formed.</font><font color="#800000"> 111 99 </font>Usually the specification of a set of further options is 112 100 necessary, e.g. the CPU time needed by the model and the memory size 113 101 needed as well as, on parallel computers, the number of processing 114 elements which are to be used (options <tt>-t</tt>, <tt>-m</tt> and 115 <tt>-X</tt>). A precondition for the call of <b>mrun</b> of course is 102 elements which are to be used (options <tt>-t</tt>, <tt>-m</tt> 103 and 104 <tt>-X</tt>). A precondition for the call of <b>mrun</b> 105 of course is 116 106 that the installation of the model on the local computer and the 117 107 remote machine is complete (see <a href="chapter_5.0.html">chapter 118 108 5.0</a>). </p> 119 109 <p>Beyond these options a variety of further options for model 120 steering can be used in the call of <b>mrun</b>. These are fully121 described in the <a 122 href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun</a>110 steering can be used in the call of <b>mrun</b>. These are 111 fully 112 described in the <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun</a> 123 113 documentation (in German). <br> 124 114 </p> 125 <hr> 126 <p><a href="chapter_3.0.html"><font color="#000080"><img src="left.gif" 127 name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a 128 href="index.html"><font color="#000080"><img src="up.gif" 129 name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a 130 href="chapter_3.2.html"><font color="#000080"><img src="right.gif" 131 name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></p> 132 <p><i>Last change: </i> 14/04/05 (SR)</p> 133 </body> 134 </html> 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: </i>$Id$</p> 117 </body></html> -
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> -
palm/trunk/DOC/app/chapter_3.3.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.3</title> 7 <meta name="GENERATOR" content="StarOffice 7 (Win32)"> 8 <meta name="AUTHOR" content="Marcus Oliver Letzel"> 9 <meta name="CREATED" content="20040728;14053490"> 10 <meta name="CHANGED" content="20041112;14150257"> 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.3 Initialization and restart runs</h3> 20 <p style="line-height: 100%;">A job started by <b>mrun</b> will 2 <html><head> 3 <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM 4 chapter 3.3</title> <meta name="GENERATOR" content="StarOffice 7 (Win32)"> <meta name="AUTHOR" content="Marcus Oliver Letzel"> <meta name="CREATED" content="20040728;14053490"> <meta name="CHANGED" content="20041112;14150257"> <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.3 Initialization and restart 11 runs</h3> 12 <p style="line-height: 100%;">A job started by <b>mrun</b> 13 will 21 14 - according to its requested computing time, its memory size 22 15 requirement and … … 35 28 very fast, jobs with higher requirements must wait longer (sometimes 36 29 several days). </p> 37 <p style="line-height: 100%;">Before the start of a model run the user 30 <p style="line-height: 100%;">Before the start of a model 31 run the user 38 32 must estimate how much CPU time the model will need for the simulation. 39 33 The necessary time in seconds has to be indicated with the mrun 40 <b>option</b> <tt><a 41 href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Opt-t">-t</a></tt> 34 <b>option</b> <tt><a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Opt-t">-t</a></tt> 42 35 and has an influence on the job class into which the job is queued. Due 43 36 to the fact that the model usually uses a variable … … 49 42 which normally leads to an abort of the job as soon as the available 50 43 CPU time is consumed. In principle one could solve this problem by 51 setting a very generously estimated value for <u><font 52 style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">-t</font></font></u>, 44 setting a very generously estimated value for <u><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">-t</font></font></u>, 53 45 but this will possibly lead to the disadvantage that the queued job has 54 46 to wait longer for execution.<br> 55 </p> 56 <p style="line-height: 100%;">To avoid this problem <b>mrun </b>offers 57 the possibility of so-called <b>restart runs</b>. During the model 47 </p><p style="line-height: 100%;">To avoid this 48 problem <b>mrun </b>offers 49 the possibility of so-called <b>restart runs</b>. During 50 the model 58 51 run PALM continuously examines how much time is left for the 59 52 execution of the job. If the run is not completed and finished shortly … … 75 68 first run of this chain (model start at t=0) is called 76 69 <b>initial run</b>. </p> 77 <p style="line-height: 100%;">Working with restart runs and their 78 generation through <b>mrun</b> requires certain entries in the 70 <p style="line-height: 100%;">Working with restart runs 71 and their 72 generation through <b>mrun</b> requires certain entries in 73 the 79 74 mrun-configuration file and in the parameter file, which are 80 75 described and explained in the following. The configuration file must 81 76 contain the following entries (example for the IBM Regatta of the 82 77 HLRN): </p> 83 <ul> 84 <pre style="line-height: 100%;"><font style="font-size: 10pt;" 85 size="2">%write_binary true restart</font><br><font 86 style="font-size: 10pt;" size="2">#</font><br><a 87 href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN</font></a><font 88 style="font-size: 10pt;" size="2"> in:job:npe d3# ~/palm/current_version/JOBS/$fname/INPUT _p3d</font><br><font 89 style="font-size: 10pt;" size="2">PARIN in:job:npe d3f ~/palm/current_version/JOBS/$fname/INPUT _p3df</font><br><a 90 href="chapter_3.4.html#BININ"><font style="font-size: 10pt;" size="2">BININ</font></a><font 91 style="font-size: 10pt;" size="2"> in:loc d3f ~/palm/current_version/JOBS/$fname/OUTPUT _d3d</font><br><font 92 style="font-size: 10pt;" size="2">#</font><br><a 93 href="chapter_3.4.html#BINOUT"><font style="font-size: 10pt;" size="2">BINOUT</font></a><font 94 style="font-size: 10pt;" size="2"> out:loc restart ~/palm/current_version/JOBS/$fname/OUTPUT _d3d</font></pre> 95 </ul> 96 <p style="line-height: 100%;">The <b>mrun</b> call for the 78 <ul> <pre style="line-height: 100%;"><font style="font-size: 10pt;" size="2">%write_binary true restart</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">PARIN in:job:npe d3f ~/palm/current_version/JOBS/$fname/INPUT _p3df</font><br><a href="chapter_3.4.html#BININ"><font style="font-size: 10pt;" size="2">BININ</font></a><font style="font-size: 10pt;" size="2"> in:loc d3f ~/palm/current_version/JOBS/$fname/OUTPUT _d3d</font><br><font style="font-size: 10pt;" size="2">#</font><br><a href="chapter_3.4.html#BINOUT"><font style="font-size: 10pt;" size="2">BINOUT</font></a><font style="font-size: 10pt;" size="2"> out:loc restart ~/palm/current_version/JOBS/$fname/OUTPUT _d3d</font></pre></ul> 79 <p style="line-height: 100%;">The <b>mrun</b> 80 call for the 97 81 initialization run of the job chain must look as follows: </p> 98 <ul> 99 <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font 100 style="font-size: 10pt;" size="2">mrun -h ibmh -d abcde -t 900 -r "d3# restart"</font></pre> 101 </ul> 102 <p style="line-height: 100%;">The specification of the environment 103 variable <tt><tt><font style="font-size: 10pt;" size="2">writ</font></tt></tt><tt><tt><font 104 style="font-size: 10pt;" size="2">e_binary</font><font 105 style="font-size: 11pt;" size="2">, </font></tt></tt>which must be 82 <ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">mrun -h ibmh -d abcde -t 900 -r "d3# restart"</font></pre></ul> 83 <p style="line-height: 100%;">The specification of the 84 environment 85 variable <tt><tt><font style="font-size: 10pt;" size="2">writ</font></tt></tt><tt><tt><font style="font-size: 10pt;" size="2">e_binary</font><font style="font-size: 11pt;" size="2">, </font></tt></tt>which 86 must be 106 87 assigned the value <tt><tt><font style="font-size: 10pt;" size="2">true</font></tt></tt>, 107 88 is essential. Only in this case the model writes 108 binary-coded data for a possible restart run to the local file <tt><tt><a 109 href="chapter_3.4.html#BINOUT">BINOUT</a></tt></tt> 89 binary-coded data for a possible restart run to the local file <tt><tt><a href="chapter_3.4.html#BINOUT">BINOUT</a></tt></tt> 110 90 at the end of the run. Then of course this output file must be stored 111 91 on a permanent file with an appropriate file connection statement 112 92 (last line of the example above). As you can see, both instructions 113 93 (variable declaration and connection statements) are only carried out 114 by <b>mrun</b>, if the character string <tt><tt><font 115 style="font-size: 10pt;" size="2">restart</font></tt></tt> 94 by <b>mrun</b>, if the character string <tt><tt><font style="font-size: 10pt;" size="2">restart</font></tt></tt> 116 95 is given for the option <tt><font style="font-size: 10pt;" size="2">-r</font> 117 </tt>in the <span style="font-weight: bold;">mrun</span> call. Thus 96 </tt>in the <span style="font-weight: bold;">mrun</span> 97 call. Thus 118 98 the example above can also be used 119 99 if no restart runs are intended. In such cases the character string … … 122 102 can simply be omitted. </p> 123 103 <p style="line-height: 100%;">Only by the specification of 124 <tt><font style="font-size: 10pt;" size="2">write_binary=true</font><font 125 style="font-size: 11pt;" size="2">126 </font><font face="Thorndale, serif">the</font></tt>model is104 <tt><font style="font-size: 10pt;" size="2">write_binary=true</font><font style="font-size: 11pt;" size="2"> 105 </font><font face="Thorndale, serif">the</font></tt> 106 model is 127 107 instructed to compute the remaining CPU time after each time step and 128 108 stop, if the run is not going to be completed and finished briefly … … 130 110 this time. Actually the stop takes place when the 131 111 difference from the available job time (determined by the <b>mrun</b> 132 option <tt><font style="font-size: 10pt;" size="2">-t</font></tt>) and 112 option <tt><font style="font-size: 10pt;" size="2">-t</font></tt>) 113 and 133 114 the time used so far by the job becomes smaller than the time given 134 by the model variable <a 135 href="chapter_4.2.html#termination_time_needed">termination_time_needed</a>. 136 With the variable <b>termination_time_needed </b>the userdetermines,115 by the model variable <a href="chapter_4.2.html#termination_time_needed">termination_time_needed</a>. 116 With the variable <b>termination_time_needed </b>the user 117 determines, 137 118 how much time is needed for binary copying of the data for restart 138 119 runs, as 139 120 well as for the following data archiving and transfer of result data 140 121 etc. (as long as this is part of the job). Thus, as soon as the 141 remaining job time is less than <b>termination_time_needed</b>, the 122 remaining job time is less than <b>termination_time_needed</b>, 123 the 142 124 model stops 143 125 the time step procedure and copies the data for a restart run to the … … 148 130 the fact that a restart run must be started and leads to the 149 131 start of an appropriate job. </p> 150 <p style="line-height: 100%;"><font color="#000000">During the initial 151 phase of a restart ru</font>n different actions than during the initial 132 <p style="line-height: 100%;"><font color="#000000">During 133 the initial 134 phase of a restart ru</font>n different actions than during the 135 initial 152 136 phase of an initial run of the model are neccessary. In this 153 137 case the model must read in the binary data written by the preceding 154 138 run at the beginning of the run. Beyond that it also reads the 155 139 initialization parameters from this file. Therefore these do not need 156 to be indicated in the parameter file (local name <a 157 href="chapter_3.4.html#PARIN">PARIN</a>). 140 to be indicated in the parameter file (local name <a href="chapter_3.4.html#PARIN">PARIN</a>). 158 141 If they are indicated nevertheless and if their value deviates from 159 142 their value of the initial run, then this is ignored. There is 160 143 exactly one exception to this rule: with the help of the 161 initialization parameter <a 162 href="chapter_4.1.html#initializing_actions">initializing_actions</a> 144 initialization parameter <a href="chapter_4.1.html#initializing_actions">initializing_actions</a> 163 145 it is determined whether the job is a restart run or an 164 146 initial run. If <b>initializing_actions</b> = 165 <i>read_restart_data</i>, then it is a restart 147 “<i>read_restart_data”</i>, then it is 148 a restart 166 149 run, otherwise an initial run. The previous remarks make it 167 150 clear that the model obviously needs two different parameter files … … 173 156 parameters with values different from the initial run may appear in 174 157 this file, but they will be ignored), which 175 must have the value <i>read_restart_data</i>.158 must have the value “<i>read_restart_data”</i>. 176 159 Therefore the user must produce two different parameter files if he 177 160 wants to operate job chains. Since the model always expects the 178 parameter file on the local file <tt>PARIN</tt>, two different file 161 parameter file on the local file <tt>PARIN</tt>, two 162 different file 179 163 connection statements must be given for this file in the 180 164 configuration file. One may be active only at the initial run, 181 the other one only at restart runs. The <b>mrun </b>call for the 165 the other one only at restart runs. The <b>mrun </b>call 166 for the 182 167 initial run shown above activates the first of the two 183 specified connection statements, because the character string <tt><font 184 style="font-size: 10pt;" size="2">d3#</font></tt> 168 specified connection statements, because the character string <tt><font style="font-size: 10pt;" size="2">d3#</font></tt> 185 169 with the option <tt><font style="font-size: 10pt;" size="2">-r</font></tt> 186 170 coincides with the character 187 171 string in the third column of the connection statement. Obviously 188 172 the next statement must be active</p> 189 <ul> 190 <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font 191 style="font-size: 10pt;" size="2">PARIN in:job:npe d3f ~/palm/current_version/JOBS/$fname/INPUT _p3df</font></pre> 192 </ul> 193 <p style="line-height: 100%;">with the restart runs. Given that t<font 194 color="#000000">his statement only gets</font> active if the option <tt><font 195 style="font-size: 10pt;" size="2">-r</font></tt> is given the value 196 <tt><font style="font-size: 11pt;" size="2">d3f</font></tt> and that 173 <ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">PARIN in:job:npe d3f ~/palm/current_version/JOBS/$fname/INPUT _p3df</font></pre></ul> 174 <p style="line-height: 100%;">with the restart runs. Given 175 that t<font color="#000000">his statement only gets</font> 176 active if the option <tt><font style="font-size: 10pt;" size="2">-r</font></tt> is given the value 177 <tt><font style="font-size: 11pt;" size="2">d3f</font></tt> 178 and that 197 179 the <b>mrun</b> call for this restart run is produced 198 automatically (thus not by the user), <b>mrun</b> obviously has to 180 automatically (thus not by the user), <b>mrun</b> 181 obviously has to 199 182 replace <tt><font style="font-size: 10pt;" size="2">"d3#"</font></tt> 200 183 of the initial run with <tt><tt><font style="font-size: 10pt;" size="2">"d3f"</font> 201 </tt></tt>within the call of this restart run. Actually, with restart 184 </tt></tt>within the call of this restart run. Actually, 185 with restart 202 186 runs all <tt><font style="font-size: 10pt;" size="2">"#"</font></tt> 203 characters within the strings given for the options <tt><font 204 style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">-r</font></font></tt><font 205 style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> 206 , </font></font><tt><font style="font-size: 10pt;" size="2"><font 207 face="Cumberland, monospace">-i</font></font></tt> 208 and <tt><font style="font-size: 10pt;" size="2">-o</font></tt> are 209 replaced by <tt><font style="font-size: 10pt;" size="2">f</font></tt>. 187 characters within the strings given for the options <tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">-r</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> 188 , </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">-i</font></font></tt> 189 and <tt><font style="font-size: 10pt;" size="2">-o</font></tt> 190 are 191 replaced by <tt><font style="font-size: 10pt;" size="2">“f”</font></tt>. 210 192 </p> 211 <p style="line-height: 100%;">For example, for the initial run 193 <p style="line-height: 100%;">For example, for the initial 194 run 212 195 the permanent file </p> 213 <ul> 214 <pre style="margin-bottom: 0.5cm; line-height: 100%;">~/palm/current_version/JOBS/abcde/INPUT/abcde_p3d</pre> 215 </ul> 216 <p style="line-height: 100%;">and for restart runs the permanent file<span 217 style="font-family: monospace;"> </span></p> 218 <ul style="font-family: monospace;"> 219 <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font 220 style="font-size: 10pt;" size="2">~/palm/current_version/JOBS/abcde/INPUT/abcde_p3df</font></pre> 221 </ul> 222 <p style="line-height: 100%;">is used. Only with restart runs the 223 local file <tt>BININ</tt> is made available as input file, because 196 <ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;">~/palm/current_version/JOBS/abcde/INPUT/abcde_p3d</pre></ul> 197 <p style="line-height: 100%;">and for restart runs the 198 permanent file<span style="font-family: monospace;"> </span></p> 199 <ul style="font-family: monospace;"> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">~/palm/current_version/JOBS/abcde/INPUT/abcde_p3df</font></pre></ul> 200 <p style="line-height: 100%;">is used. Only with restart 201 runs the 202 local file <tt>BININ</tt> is made available as input file, 203 because 224 204 the appropriate file connection statement also contains the 225 205 character string <tt><font style="font-size: 10pt;" size="2">"d3f"</font></tt> … … 230 210 the corresponding output file (local name BINOUT) are identical and 231 211 read </p> 232 <ul> 233 <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font 234 style="font-size: 10pt;" size="2">~/palm/current_version/JOBS/abcde/OUTPUT/abcde_d3d.</font></pre> 235 </ul> 236 <p style="line-height: 100%;">However, after the file produced by the 212 <ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">~/palm/current_version/JOBS/abcde/OUTPUT/abcde_d3d.</font></pre></ul> 213 <p style="line-height: 100%;">However, after the file 214 produced by the 237 215 previous job was read in by the model and after at the local file 238 216 <tt>BINOUT </tt>was produced at the end of the job, the 239 restart job does not overwrite this permanent file (<tt> 240 /<font 241 style="font-size: 10pt;" size="2">abcde_d3d</font></tt>) 217 restart job does not overwrite this permanent file (<tt>…/<font style="font-size: 10pt;" size="2">abcde_d3d</font></tt>) 242 218 with the new data. Instead of that, it is examined whether already 243 a permanent file with the name <tt><font style="font-size: 10pt;" 244 size="2"> 245 /abcde_d3d</font> 246 <font face="Thorndale, serif">exists </font></tt>when copying the 219 a permanent file with the name <tt><font style="font-size: 10pt;" size="2">…/abcde_d3d</font> 220 <font face="Thorndale, serif">exists </font></tt>when 221 copying the 247 222 output file (<tt><font style="font-size: 10pt;" size="2">BINOUT</font></tt>) 248 of <b>mrun</b>. If this is the case, <tt><font 249 style="font-size: 10pt;" size="2">BINOUT</font></tt> 250 is copied to the file<font style="font-size: 10pt;" size="2"><font 251 face="Cumberland, monospace"> 252 </font></font><tt><font style="font-size: 10pt;" size="2"><font 253 face="Cumberland, monospace"> 254 /abcde_d3d.1</font></font></tt><font 255 style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">.</font></font> 256 Even if this file is already present, <tt><font 257 style="font-size: 10pt;" size="2"> 258 /abcde_d3d.2</font></tt> 223 of <b>mrun</b>. If this is the case, <tt><font style="font-size: 10pt;" size="2">BINOUT</font></tt> 224 is copied to the file<font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> 225 </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">…/abcde_d3d.1</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">.</font></font> 226 Even if this file is already present, <tt><font style="font-size: 10pt;" size="2">…/abcde_d3d.2</font></tt> 259 227 is tried etc. For an input file the highest existing cycle 260 228 of the respective permanent file is copied. In the example above this 261 229 means: the initial run creates the permanent file 262 <tt><font style="font-size: 10pt;" size="2"> 263 /abcde_d3d</font></tt><font 264 style="font-size: 11pt;" size="2">,</font> 265 the first restart run uses this file and creates <tt> 266 /<font 267 style="font-size: 10pt;" size="2">abcde_d3d.1</font></tt>, 268 the second restart run creates <tt><font style="font-size: 10pt;" 269 size="2"> 270 /abcde_d3d.2</font></tt><font style="font-size: 10pt;" 271 size="2"> 230 <tt><font style="font-size: 10pt;" size="2">…/abcde_d3d</font></tt><font style="font-size: 11pt;" size="2">,</font> 231 the first restart run uses this file and creates <tt>…/<font style="font-size: 10pt;" size="2">abcde_d3d.1</font></tt>, 232 the second restart run creates <tt><font style="font-size: 10pt;" size="2">…/abcde_d3d.2</font></tt><font style="font-size: 10pt;" size="2"> 272 233 </font>etc. After completion of the job chain the user can still 273 234 access all files created by the jobs. This makes it possible for the 274 235 user for example to restart the model run of a certain job of the job 275 236 chain again. </p> 276 <p style="line-height: 100%;">Therefore restart jobs can not only be 277 started automatically through <b>mrun</b>, but also manually by the 237 <p style="line-height: 100%;">Therefore restart jobs can 238 not only be 239 started automatically through <b>mrun</b>, but also 240 manually by the 278 241 user. This is necessary e.g. whenever after the end of a job chain 279 242 it is decided that the simulation must be continued further, because 280 243 the phenomenon which should be examined did not reach the desired 281 state yet. In such cases the <b>mrun</b> options completely 282 correspond to those of the initial call; simply the <tt><font 283 style="font-size: 10pt;" size="2">"#"</font></tt> characters in the 284 arguments of options <tt><font style="font-size: 10pt;" size="2"><font 285 face="Cumberland, monospace">-r</font></font></tt><font 286 style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">, 287 </font></font><tt><font style="font-size: 10pt;" size="2"><font 288 face="Cumberland, monospace">-i</font></font></tt> 289 and <tt><font style="font-size: 10pt;" size="2">-o</font></tt> must be 244 state yet. In such cases the <b>mrun</b> options 245 completely 246 correspond to those of the initial call; simply the <tt><font style="font-size: 10pt;" size="2">"#"</font></tt> 247 characters in the 248 arguments of options <tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">-r</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">, 249 </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">-i</font></font></tt> 250 and <tt><font style="font-size: 10pt;" size="2">-o</font></tt> 251 must be 290 252 replaced by <tt><font style="font-size: 10pt;" size="2">"f"</font></tt>. 291 253 </p> 292 <hr> 293 <p style="line-height: 100%;"><br> 294 <font color="#000080"><font color="#000080"><a href="chapter_3.2.html"><font 295 color="#000080"><img src="left.gif" name="Grafik1" align="bottom" 296 border="2" height="32" width="32"></font></a><a href="index.html"><font 297 color="#000080"><img src="up.gif" name="Grafik2" align="bottom" 298 border="2" height="32" width="32"></font></a><a href="chapter_3.4.html"><font 299 color="#000080"><img src="right.gif" name="Grafik3" align="bottom" 300 border="2" height="32" width="32"></font></a></font></font></p> 301 <p style="line-height: 100%;"><i>Last change: </i> 14/04/05 (SR)</p> 302 </body> 303 </html> 254 <hr><p style="line-height: 100%;"><br> 255 <font color="#000080"><font color="#000080"><a href="chapter_3.2.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.4.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> 256 $Id$</p> 257 </body></html> -
palm/trunk/DOC/app/chapter_3.4.html
r54 r62 1 1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2 2 <html><head> 3 4 5 6 7 8 9 10 11 12 13 <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"> 14 <title>chapter_3.4</title></head> 15 16 <body> 17 18 19 20 21 22 <h3 style="line-height: 100%;"><font color="#000000">3.4 Input and 3 <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"><title>chapter_3.4</title> </head> 4 <body><h3 style="line-height: 100%;"><font color="#000000">3.4 Input and 23 5 output files</font></h3> 24 25 26 27 28 29 <p style="line-height: 100%;"><font color="#000000"></font></p> 30 31 <p style="line-height: 100%;"><font color="#000000">The model works 6 <p style="line-height: 100%;"></p><p style="line-height: 100%;"><font color="#000000">The 7 model works 32 8 with a set of files, which are all located in the temporary working 33 9 directory and which are either expected at the beginning of the run … … 35 11 produced during the run and/or at the end of the simulation (output 36 12 files).</font><font color="#800000"> 37 <font color="#000000">The following table lists all default files 13 <font color="#000000">The following table lists all 14 default files 38 15 addressed by the model. They are arranged according to the 39 16 associated FORTRAN unit (unit number).</font> </font><font color="#000000">The 40 17 unit 90 is used for different files, which are opened only briefly 41 18 and uniquely in the model and closed directly afterwards. 42 Unit numbers 101 - 109, 111 - 113, and 116 refer to data files which have NetCDF format. 19 Unit numbers 101 - 109, 111 - 113, and 116 refer to data files 20 which have NetCDF format. 43 21 These are not opened by a FORTRAN-OPEN-statement but by a corresponding 44 22 NetCDF call (NF90_CREATE or NF90_OPEN). These files are only created on 45 23 machines where a NetCDF library is available.<br> 46 47 </font></p> 48 49 50 <p style="line-height: 100%;"><font color="#000000">The file 24 </font></p><p style="line-height: 100%;"><font color="#000000">The file 51 25 names described in the list correspond to the names indicated in the 52 26 respective OPEN instruction, i.e. the files are expected and saved … … 57 31 If restart jobs shall append data to an existing NetCDF file (created 58 32 by a previous job of the job chain), the respective file has to be 59 given as an input file (see also <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a> which gives more details about the PALM-NetCDF-output).</font> </p> 60 61 <p style="line-height: 100%;"> </p> 62 63 64 65 66 67 68 <p style="line-height: 100%;"><font color="#000000">On parallel 33 given as an input file (see also <a href="../app/chapter_4.5.1.html">chapter 34 4.5.1</a> which gives more details about the PALM-NetCDF-output).</font> 35 </p> 36 <p style="line-height: 100%;"> </p><p style="line-height: 100%;"><font color="#000000">On 37 parallel 69 38 computers many of the files are read and/or written by the central 70 39 processing element 0 (PE0) only. These files have processor-independent … … 73 42 content. For the binary output of data for restart runs (local file 74 43 <a href="#BINOUT">BINOUT</a>), 75 for example, <font color="#000000">each PE outputs only the data of 44 for example, <font color="#000000">each PE outputs only 45 the data of 76 46 its subdomain. So each processing element writes 77 47 into its own file with its own file name. These files lie in a … … 82 52 Such files, which have processor-dependent content on parallel 83 53 computers, are marked in the following list by the fact, that to the 84 file name a line (”/“) is attached. If appropriate output 85 files are to be copied through <b>mrun</b> to permanent files, and/or 54 file name a line (”/“) is attached. If appropriate 55 output 56 files are to be copied through <b>mrun</b> to permanent 57 files, and/or 86 58 files with processor-dependent content are supposed to be copied as 87 59 input files into the temporary working directory of the model, you have … … 90 62 <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#flpe">flpe</a> 91 63 <font color="#000000">in the <b>mrun </b>description).</font><font color="#800000"> 92 </font><font color="#000000">Then the permanent file name will be 64 </font><font color="#000000">Then the permanent file 65 name will be 93 66 interpreted as a directory name, in which the input files are 94 67 expected and/or to which output files are written. The file names in 95 68 these directories are always named _0000, _0001, _0002 etc. </font> 96 </font></p> 97 98 99 100 101 102 <font color="#000000"><font color="#000000">For internal use, 69 </font></p><font color="#000000"><font color="#000000">For internal use, 103 70 the model may open a set of further files, which are not 104 71 defined by the user but contain no usable information and 105 72 therefore are not included in this list. <br> 106 107 108 109 110 111 <br> 112 113 114 115 116 117 </font> 118 <table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> 119 120 121 122 123 124 <tbody> 125 126 127 128 129 130 <tr valign="top"> 131 132 133 134 135 136 <td width="8%"> 137 138 139 140 141 142 <p><font size="4"><b>Unit</b></font></p> 143 144 145 146 147 148 </td> 149 150 151 152 153 154 <td width="12%"> 155 156 157 158 159 160 <p><font size="4"><b>Name</b></font></p> 161 162 163 164 165 166 </td> 167 168 169 170 171 172 <td width="4%"> 173 174 175 176 177 178 <p><font size="4"><b>I/O</b></font></p> 179 180 181 182 183 184 </td> 185 186 187 188 189 190 <td width="9%"> 191 192 193 194 195 196 <p><font size="4"><b>Format</b></font></p> 197 198 199 200 201 202 </td> 203 204 205 206 207 208 <td colspan="1" width="67%"> 209 210 211 212 213 214 <p><font size="4"><b>Description/contents</b></font></p> 215 216 217 218 219 220 </td> 221 222 223 224 225 226 </tr> 227 228 229 230 231 232 <tr valign="top"> 233 234 235 236 237 238 <td style="text-align: center;" width="8%"> 11<br> 239 240 241 242 243 244 </td> 245 246 247 248 249 250 <td width="12%"> 251 252 253 254 255 256 <p><a name="PARIN"></a>PARIN</p> 257 258 259 260 261 262 </td> 263 264 265 266 267 268 <td width="4%"> 269 270 271 272 273 274 <p align="center">I</p> 275 276 277 278 279 280 </td> 281 282 283 284 285 286 <td style="width: 9%;"> 287 288 289 290 291 292 <p>ASCII/ <br> 293 294 295 296 297 298 NAMELIST</p> 299 300 301 302 303 304 </td> 305 306 307 308 309 310 <td colspan="1" width="67%"> 311 312 313 314 315 316 <p><font color="#000000">Parameter for model steering. This file 73 <br></font> 74 <table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody> <tr valign="top"> <td width="8%"> <p><font size="4"><b>Unit</b></font></p> </td> 75 <td width="12%"> <p><font size="4"><b>Name</b></font></p> 76 </td> <td width="4%"> <p><font size="4"><b>I/O</b></font></p> 77 </td> <td width="9%"> <p><font size="4"><b>Format</b></font></p> 78 </td> <td colspan="1" width="67%"> <p><font size="4"><b>Description/contents</b></font></p> 79 </td> </tr> <tr valign="top"> <td style="text-align: center;" width="8%"> 11<br> </td> 80 <td width="12%"> <p><a name="PARIN"></a>PARIN</p> 81 </td> <td width="4%"> <p align="center">I</p> 82 </td> <td style="width: 9%;"> <p>ASCII/ 83 <br>NAMELIST</p> </td> <td colspan="1" width="67%"> <p><font color="#000000">Parameter 84 for model steering. This file 317 85 is needed by the model in each case. Its content and structure is 318 86 described in detail in</font> <a href="chapter_4.0.html">chapter 319 87 4.0</a>. <a href="chapter_4.4.html">Chapter 320 4.4</a> <font color="#000000">shows a simple example. </font> </p> 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 </td> 336 337 338 339 340 341 </tr> 342 343 344 345 346 347 <tr valign="top"> 348 349 350 351 352 353 <td style="text-align: center;" width="8%"> 354 355 356 357 358 359 <p align="center">13</p> 360 361 362 363 364 365 </td> 366 367 368 369 370 371 <td width="12%"> 372 373 374 375 376 377 <p><a name="BININ"></a>BININ/</p> 378 379 380 381 382 383 </td> 384 385 386 387 388 389 <td width="4%"> 390 391 392 393 394 395 <p align="center">I</p> 396 397 398 399 400 401 </td> 402 403 404 405 406 407 <td width="9%"> 408 409 410 411 412 413 <p>Binary</p> 414 415 416 417 418 419 </td> 420 421 422 423 424 425 <td colspan="1" width="67%"> 426 427 428 429 430 431 <p>Binary data, which are read in by the model at the beginning 88 4.4</a> <font color="#000000">shows a simple 89 example. </font> </p> </td> </tr> <tr valign="top"> <td style="text-align: center;" width="8%"> <p align="center">13</p> </td> 90 <td width="12%"> <p><a name="BININ"></a>BININ/</p> 91 </td> <td width="4%"> <p align="center">I</p> 92 </td> <td width="9%"> <p>Binary</p> </td> 93 <td colspan="1" width="67%"> <p>Binary data, 94 which are read in by the model at the beginning 432 95 of a restart run (see <a href="chapter_3.3.html">chapter 433 3.3</a>). The appropriate file must have been written by the preceding 96 3.3</a>). The appropriate file must have been written by the 97 preceding 434 98 job of the job chain (see <a href="#BINOUT">BINOUT</a>). 435 99 This file contains the initial parameters (see <a href="chapter_4.1.html">chapter 436 4.1</a>) of the job chain, arrays of the prognostic and diagnostic 100 4.1</a>) of the job chain, arrays of the prognostic and 101 diagnostic 437 102 variables as well as those parameters and variables for plots of 438 103 horizontally averaged vertical profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>), … … 441 106 reads its own file and the file content is processor-dependent. The 442 107 number of processors which can be used must not be changed during a job 443 chain and/or if a job chain is continued. </p> 444 445 446 447 448 449 450 451 452 453 454 <p>Knowledge of the file structure is usually not necessary, 108 chain and/or if a job chain is continued. </p> <p>Knowledge 109 of the file structure is usually not necessary, 455 110 because the file is produced and also read again by the model, but it 456 111 can be useful for error determination in case of read errors . 457 112 Therefore the file structure is described in the following. </p> 458 459 460 461 462 463 464 465 466 467 468 <p>The first record of this file contains a version number (ten 113 <p>The first record of this file contains a version number (ten 469 114 character string) of the subroutine, which, which output the data that 470 115 follows (write_var_list.f90). This number has to … … 472 117 (read_var_list.f90) in case of a restart run. Otherwise the model run 473 118 is aborted. Version numbers are changed whenever new code revisions 474 require a change of the file format. </p> 475 476 477 478 479 480 481 482 483 484 485 <p>Starting from the second record, all initial parameters follow 119 require a change of the file format. </p> <p>Starting 120 from the second record, all initial parameters follow 486 121 (exception: <a href="chapter_4.1.html#initializing_actions">initializing_actions</a>), 487 122 whereby each parameter fills two records. In the first record the name … … 493 128 and <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>. 494 129 If a variable with unknown name is found the model run is 495 aborted. </p> 496 497 498 499 500 501 502 503 504 505 506 <p>At the end of the initial parameters a record with the string "<i>*** 507 end ***</i>"follows (filled up with trailing blanks up to a length of 508 30 characters). </p> 509 510 511 512 513 514 515 516 517 518 519 <p>Afterwards the fields of the prognostic and diagnostic 130 aborted. </p> <p>At the end of the initial 131 parameters a record with the string "<i>*** 132 end ***</i>"follows (filled up with trailing blanks up to a 133 length of 134 30 characters). </p> <p>Afterwards the fields 135 of the prognostic and diagnostic 520 136 variables follow. This part of the file also begins with a record 521 137 consisting of a character string of length 10, which contains the 522 138 version number of the subroutine that wrote the arrays that follow 523 139 (write_3d_binary.f90). It must agree with the number of the reading 524 subroutine (read_3d_binary.f90). </p> 525 526 527 528 529 530 531 532 533 534 535 <p>The following record contains the number of processors which 140 subroutine (read_3d_binary.f90). </p> <p>The 141 following record contains the number of processors which 536 142 were used in the model run producing this file, the processor ID of the 537 143 special processor, which creates the file, as well as the lower and … … 541 147 particular on parallel computers, because the jobs of a job chain 542 148 always have to use the same number of processors and the same virtual 543 processor grid. </p> 544 545 546 547 548 549 550 551 552 553 554 <p>After these tests the individual arrays as well as parameters 149 processor grid. </p> <p>After these tests the 150 individual arrays as well as parameters 555 151 and variables for plots of horizontally averaged vertical profiles 556 152 follow. Like the initialization parameters, they consist of two … … 561 157 the plot and the respective variables are only read in if for the run 562 158 parameter <a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a> 563 = <i>.TRUE</i> is selected, otherwise they will be skipped. </p> 564 565 566 567 568 569 570 571 572 573 574 <p>At the end of the file there has to be a record with the 575 character string "<span style="font-style: italic;"></span><i>*** end 159 = <i>.TRUE</i> is selected, otherwise they will be 160 skipped. </p> <p>At the end of the file there 161 has to be a record with the 162 character string "<span style="font-style: italic;"></span><i>*** 163 end 576 164 ***</i>"(filled up with trailing blanks up to a length of 20 577 characters).</p> 578 579 580 581 582 583 </td> 584 585 586 587 588 589 </tr> 590 591 592 593 594 595 <tr valign="top"> 596 597 598 599 600 601 <td style="text-align: center;" width="8%"> 602 603 604 605 606 607 <p align="center">14</p> 608 609 610 611 612 613 </td> 614 615 616 617 618 619 <td width="12%"> 620 621 622 623 624 625 <p><a name="BINOUT"></a>BINOUT/</p> 626 627 628 629 630 631 </td> 632 633 634 635 636 637 <td width="4%"> 638 639 640 641 642 643 <p align="center">O</p> 644 645 646 647 648 649 </td> 650 651 652 653 654 655 <td width="9%"> 656 657 658 659 660 661 <p>Binary</p> 662 663 664 665 666 667 </td> 668 669 670 671 672 673 <td colspan="1" width="67%"> 674 675 676 677 678 679 <p>Binary data, which are written by the model at the end of the 165 characters).</p> </td> </tr> <tr valign="top"> 166 <td style="text-align: center;" width="8%"> <p align="center">14</p> </td> <td width="12%"> 167 <p><a name="BINOUT"></a>BINOUT/</p> </td> 168 <td width="4%"> <p align="center">O</p> 169 </td> <td width="9%"> <p>Binary</p> </td> 170 <td colspan="1" width="67%"> <p>Binary data, 171 which are written by the model at the end of the 680 172 run and possibly needed by restart runs (see <a href="chapter_3.3.html">chapter 681 3.3</a>) for the initialization. This output file is then read in as 173 3.3</a>) for the initialization. This output file is then read in 174 as 682 175 file <a href="#BININ">BININ</a>. 683 176 It contains the initial parameters (see <a href="chapter_4.1.html">chapter 684 4.1</a>) of the model run, arrays of the prognostic and diagnostic 177 4.1</a>) of the model run, arrays of the prognostic and 178 diagnostic 685 179 variables as well as those parameters determined so far during a job 686 180 chain and variables for plots of horizontally averaged vertical … … 690 184 processor-dependent. A specification of the file format can be found in 691 185 the 692 description of the file <a href="#BININ">BININ</a>. </p> 693 694 695 696 697 698 699 700 701 702 703 <p>The file BINOUT is written by the model only if, with the help 704 of the <b>mrun</b>-configuration file, the <font face="Thorndale, serif">value</font> <span style="font-family: monospace;">true</span> is assigned for the 186 description of the file <a href="#BININ">BININ</a>. 187 </p> <p>The file BINOUT is written by the model only if, 188 with the help 189 of the <b>mrun</b>-configuration file, the <font face="Thorndale, serif">value</font> <span style="font-family: monospace;">true</span> is 190 assigned for the 705 191 environment 706 192 variable <span style="font-size: 10pt; font-family: monospace;">write_binary</span> 707 193 (see <a href="chapter_3.3.html">chapter 708 3.3</a>). </p> 709 710 711 712 713 714 715 716 717 718 719 <p>With large grid point numbers the file BINOUT (or the 194 3.3</a>). </p> <p>With large grid point 195 numbers the file BINOUT (or the 720 196 files residing in directory BINOUT/) will be very large and should 721 197 be stored (if available) on the archive system of the remote computer.</p> 722 723 724 725 726 727 </td> 728 729 730 731 732 733 </tr> 734 735 736 737 738 739 <tr> 740 741 742 743 744 745 <td style="vertical-align: top; text-align: center;">15<br> 746 747 748 749 750 751 </td> 752 753 754 755 756 757 <td style="vertical-align: top;"><a name="RUN_CONTROL"></a>RUN_CONTROL</td> 758 759 760 761 762 763 <td style="vertical-align: top;">O</td> 764 765 766 767 768 769 <td style="vertical-align: top;">Ascii</td> 770 771 772 773 774 775 <td colspan="1" width="67%"> 776 777 778 779 780 781 <p>This file contains the so-called time step control output of 198 </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">15<br> 199 </td> <td style="vertical-align: top;"><a name="RUN_CONTROL"></a>RUN_CONTROL</td> <td style="vertical-align: top;">O</td> <td style="vertical-align: top;">Ascii</td> <td colspan="1" width="67%"> <p>This file contains 200 the so-called time step control output of 782 201 the model. At certain temporal intervals, which are described by the 783 202 run … … 787 206 file. Additionally, such a control line is always written, whenever the 788 207 time step of the model changes. All data and quantities always refer to 789 the entire model domain. </p> 790 791 792 793 794 795 796 797 798 799 800 <p>If the 1D-model is switched on for the initialization of the 208 the entire model domain. </p> <p>If the 209 1D-model is switched on for the initialization of the 801 210 3D-models, then control lines are likewise written into this file at 802 211 certain temporal intervals (see <a href="chapter_4.1.html#dt_run_control_1d">dt_run_control_1d</a>). 803 </p> 804 805 806 807 808 809 810 811 812 813 814 <p>By default, the file RUN_CONTROL only lists information 212 </p> <p>By default, the file RUN_CONTROL only lists 213 information 815 214 about the selected model parameters at the beginning of the 816 215 initial run. These informations are written at the beginnning of a run. … … 821 220 it can be achieved that this information is also written at the 822 221 beginning of the file RUN_CONTROL at restart runs. </p> 823 824 825 826 827 828 829 830 831 832 833 <p>The individual columns of the 1D - time step control output 222 <p>The individual columns of the 1D - time step control output 834 223 have the following meaning (listed by the respective heading of the 835 224 appropriate 836 column in the file): <br> 837 838 839 840 841 842 </p> 843 844 845 846 847 848 849 850 851 852 853 <table style="text-align: left; width: 100%;" cellpadding="2"> 854 855 856 857 858 859 <tbody> 860 861 862 863 864 865 <tr> 866 867 868 869 870 871 <td style="vertical-align: top;">ITER.</td> 872 873 874 875 876 877 <td style="vertical-align: top;">Number of time steps 878 accomplished so far</td> 879 880 881 882 883 884 </tr> 885 886 887 888 889 890 <tr> 891 892 893 894 895 896 <td style="vertical-align: top;">HH:MM:SS</td> 897 898 899 900 901 902 <td style="vertical-align: top;">Time (in hours: minutes: 903 seconds)</td> 904 905 906 907 908 909 </tr> 910 911 912 913 914 915 <tr> 916 917 918 919 920 921 <td style="vertical-align: top;">DT</td> 922 923 924 925 926 927 <td style="vertical-align: top;">Time step (in s)</td> 928 929 930 931 932 933 </tr> 934 935 936 937 938 939 <tr> 940 941 942 943 944 945 <td style="vertical-align: top;">UMAX</td> 946 947 948 949 950 951 <td style="vertical-align: top;">Maximum absolute wind 225 column in the file): <br> </p> <table style="text-align: left; width: 100%;" cellpadding="2"> 226 <tbody> <tr> <td style="vertical-align: top;">ITER.</td> 227 <td style="vertical-align: top;">Number of time steps 228 accomplished so far</td> </tr> <tr> <td style="vertical-align: top;">HH:MM:SS</td> <td style="vertical-align: top;">Time (in hours: minutes: 229 seconds)</td> </tr> <tr> <td style="vertical-align: top;">DT</td> <td style="vertical-align: top;">Time step (in s)</td> </tr> 230 <tr> <td style="vertical-align: top;">UMAX</td> 231 <td style="vertical-align: top;">Maximum absolute wind 952 232 velocity 953 (u-component) (in m/s)</td> 954 955 956 957 958 959 </tr> 960 961 962 963 964 965 <tr> 966 967 968 969 970 971 <td style="vertical-align: top;">VMAX</td> 972 973 974 975 976 977 <td style="vertical-align: top;">Maximum absolute wind 233 (u-component) (in m/s)</td> </tr> <tr> <td style="vertical-align: top;">VMAX</td> <td style="vertical-align: top;">Maximum absolute wind 978 234 velocity 979 (v-component) (in m/s)</td> 980 981 982 983 984 985 </tr> 986 987 988 989 990 991 <tr> 992 993 994 995 996 997 <td style="vertical-align: top;">U *</td> 998 999 1000 1001 1002 1003 <td style="vertical-align: top;">Friction velocity (<font color="#000000">in </font>m/s)</td> 1004 1005 1006 1007 1008 1009 </tr> 1010 1011 1012 1013 1014 1015 <tr> 1016 1017 1018 1019 1020 1021 <td style="vertical-align: top;">ALPHA</td> 1022 1023 1024 1025 1026 1027 <td style="vertical-align: top;">Angle of the wind vector 235 (v-component) (in m/s)</td> </tr> <tr> <td style="vertical-align: top;">U *</td> <td style="vertical-align: top;">Friction velocity (<font color="#000000">in </font>m/s)</td> </tr> 236 <tr> <td style="vertical-align: top;">ALPHA</td> 237 <td style="vertical-align: top;">Angle of the wind vector 1028 238 (to the x-axis) at the top of the 1029 239 Prandtl layer (k=1) (<font color="#000000">in </font>degrees)</td> 1030 1031 1032 1033 1034 1035 </tr> 1036 1037 1038 1039 1040 1041 <tr> 1042 1043 1044 1045 1046 1047 <td style="vertical-align: middle;">ENERG.</td> 1048 1049 1050 1051 1052 1053 <td style="vertical-align: top;">Kinetic energy of the 240 </tr> <tr> <td style="vertical-align: middle;">ENERG.</td> 241 <td style="vertical-align: top;">Kinetic energy of the 1054 242 1D-model (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>), 1055 averaged over all grid points</td> 1056 1057 1058 1059 1060 1061 </tr> 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 </tbody> 1073 1074 1075 1076 1077 1078 </table> 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 <p> 243 averaged over all grid points</td> </tr> </tbody> </table> 244 <p> 1090 245 The individual columns of the 3D - time step control output 1091 246 have the following meaning (listed by the respective heading of the 1092 247 appropriate 1093 column in the file):<br> 1094 1095 1096 1097 1098 1099 </p> 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 <table style="text-align: left; width: 100%;" cellpadding="2"> 1111 1112 1113 1114 1115 1116 <tbody> 1117 1118 1119 1120 1121 1122 <tr> 1123 1124 1125 1126 1127 1128 <td style="vertical-align: top;">RUN</td> 1129 1130 1131 1132 1133 1134 <td style="vertical-align: top;">Serial-number of the job 248 column in the file):<br> </p> <table style="text-align: left; width: 100%;" cellpadding="2"> 249 <tbody> <tr> <td style="vertical-align: top;">RUN</td> 250 <td style="vertical-align: top;">Serial-number of the job 1135 251 in the job chain. The initial 1136 252 run has the number 0, restart runs accordingly have larger numbers.</td> 1137 1138 1139 1140 1141 1142 </tr> 1143 1144 1145 1146 1147 1148 <tr> 1149 1150 1151 1152 1153 1154 <td style="vertical-align: top;">ITER.</td> 1155 1156 1157 1158 1159 1160 <td style="vertical-align: top;">Number of time steps 253 </tr> <tr> <td style="vertical-align: top;">ITER.</td> 254 <td style="vertical-align: top;">Number of time steps 1161 255 accomplished since starting time t=0 of 1162 the initial run.</td> 1163 1164 1165 1166 1167 1168 </tr> 1169 1170 1171 1172 1173 1174 <tr> 1175 1176 1177 1178 1179 1180 <td style="vertical-align: top;">HH:MM:SS</td> 1181 1182 1183 1184 1185 1186 <td style="vertical-align: top;">Time (<font color="#000000">in 1187 </font>hours: minutes: 256 the initial run.</td> </tr> <tr> <td style="vertical-align: top;">HH:MM:SS</td> <td style="vertical-align: top;">Time (<font color="#000000">in 257 </font>hours: minutes: 1188 258 seconds) since starting time t=0 of the 1189 initial run.</td> 1190 1191 1192 1193 1194 1195 </tr> 1196 1197 1198 1199 1200 1201 <tr> 1202 1203 1204 1205 1206 1207 <td style="vertical-align: top;">DT (E)</td> 1208 1209 1210 1211 1212 1213 <td style="vertical-align: top;">Time step (<font color="#000000">in </font>s). The 259 initial run.</td> </tr> <tr> <td style="vertical-align: top;">DT (E)</td> <td style="vertical-align: top;">Time step (<font color="#000000">in </font>s). The 1214 260 following character indicates whether the 1215 261 time … … 1219 265 which indicates with which time step procedure the changed time step 1220 266 was accomplished (<span style="font-family: monospace;">L:</span> 1221 Leapfrog, <span style="font-family: monospace;">E:</span> Euler). This 267 Leapfrog, <span style="font-family: monospace;">E:</span> 268 Euler). This 1222 269 does 1223 not apply for the default Runge-Kutta timestep scheme.</td> 1224 1225 1226 1227 1228 1229 </tr> 1230 1231 1232 1233 1234 1235 <tr> 1236 1237 1238 1239 1240 1241 <td style="vertical-align: top;">UMAX</td> 1242 1243 1244 1245 1246 1247 <td style="vertical-align: top;">Maximum absolute wind 1248 velocity (u-component) (<font color="#000000">in </font>m/s). If at 270 not apply for the default Runge-Kutta timestep scheme.</td> </tr> 271 <tr> <td style="vertical-align: top;">UMAX</td> 272 <td style="vertical-align: top;">Maximum absolute wind 273 velocity (u-component) (<font color="#000000">in </font>m/s). 274 If at 1249 275 the 1250 276 appropriate output time a random disturbance was added to the 1251 277 horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>), 1252 278 the character D will appear directly after the velocity value.</td> 1253 1254 1255 1256 1257 1258 </tr> 1259 1260 1261 1262 1263 1264 <tr> 1265 1266 1267 1268 1269 1270 <td style="vertical-align: top;">VMAX</td> 1271 1272 1273 1274 1275 1276 <td style="vertical-align: top;">Maximum absolute wind 1277 velocity (v-component) (<font color="#000000">in </font>m/s). If at 279 </tr> <tr> <td style="vertical-align: top;">VMAX</td> 280 <td style="vertical-align: top;">Maximum absolute wind 281 velocity (v-component) (<font color="#000000">in </font>m/s). 282 If at 1278 283 the 1279 284 appropriate output time a random disturbance was added to the 1280 285 horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>), 1281 286 the character D will appear directly after the velocity value.</td> 1282 1283 1284 1285 1286 1287 </tr> 1288 1289 1290 1291 1292 1293 <tr> 1294 1295 1296 1297 1298 1299 <td style="vertical-align: top;">WMAX</td> 1300 1301 1302 1303 1304 1305 <td style="vertical-align: top;">Maximum absolute wind 287 </tr> <tr> <td style="vertical-align: top;">WMAX</td> 288 <td style="vertical-align: top;">Maximum absolute wind 1306 289 velocity (w-component) (<font color="#000000">in </font>m/s).</td> 1307 1308 1309 1310 1311 1312 </tr> 1313 1314 1315 1316 1317 1318 <tr> 1319 1320 1321 1322 1323 1324 <td style="vertical-align: top;">U *</td> 1325 1326 1327 1328 1329 1330 <td style="vertical-align: top;">Horizontal average of the 290 </tr> <tr> <td style="vertical-align: top;">U 291 *</td> <td style="vertical-align: top;">Horizontal 292 average of the 1331 293 friction velocity (<font color="#000000">in </font>m/s).</td> 1332 1333 1334 1335 1336 1337 </tr> 1338 1339 1340 1341 1342 1343 <tr> 1344 1345 1346 1347 1348 1349 <td style="vertical-align: top;">W *</td> 1350 1351 1352 1353 1354 1355 <td style="vertical-align: top;">Convective velocity scale 1356 (<font color="#000000">in </font>m/s). The assumed boundary layer 1357 height is determined via the heat flux minimum criterion.</td> 1358 1359 1360 1361 1362 1363 </tr> 1364 1365 1366 1367 1368 1369 <tr> 1370 1371 1372 1373 1374 1375 <td style="vertical-align: top;">THETA *</td> 1376 1377 1378 1379 1380 1381 <td style="vertical-align: top;">Characteristic temperature 294 </tr> <tr> <td style="vertical-align: top;">W 295 *</td> <td style="vertical-align: top;">Convective 296 velocity scale 297 (<font color="#000000">in </font>m/s). The assumed 298 boundary layer 299 height is determined via the heat flux minimum criterion.</td> </tr> 300 <tr> <td style="vertical-align: top;">THETA *</td> 301 <td style="vertical-align: top;">Characteristic 302 temperature 1382 303 of the Prandtl - layer (<font color="#000000">in </font>K).</td> 1383 1384 1385 1386 1387 1388 </tr> 1389 1390 1391 1392 1393 1394 <tr> 1395 1396 1397 1398 1399 1400 <td style="vertical-align: top;">Z_I</td> 1401 1402 1403 1404 1405 1406 <td style="vertical-align: top;">Height of the convective 1407 boundary layer (<font color="#000000">in </font>m), determined via 1408 the criterion of the heat flux minimum.</td> 1409 1410 1411 1412 1413 1414 </tr> 1415 1416 1417 1418 1419 1420 <tr> 1421 1422 1423 1424 1425 1426 <td style="vertical-align: middle;">ENERG.</td> 1427 1428 1429 1430 1431 1432 <td style="vertical-align: top;">Average resolved total 304 </tr> <tr> <td style="vertical-align: top;">Z_I</td> 305 <td style="vertical-align: top;">Height of the convective 306 boundary layer (<font color="#000000">in </font>m), 307 determined via 308 the criterion of the heat flux minimum.</td> </tr> <tr> 309 <td style="vertical-align: middle;">ENERG.</td> <td style="vertical-align: top;">Average resolved total 1433 310 energy of the flow field (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>), 1434 normalized with the total number of grid points.</td> 1435 1436 1437 1438 1439 1440 </tr> 1441 1442 1443 1444 1445 1446 <tr> 1447 1448 1449 1450 1451 1452 <td style="vertical-align: middle;">DISTENERG</td> 1453 1454 1455 1456 1457 1458 <td style="vertical-align: top;">Average resolved 1459 disturbance energy of flow field (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>), 1460 normalized with the total number of grid points.</td> 1461 1462 1463 1464 1465 1466 </tr> 1467 1468 1469 1470 1471 1472 <tr> 1473 1474 1475 1476 1477 1478 <td style="vertical-align: top;">DIVOLD</td> 1479 1480 1481 1482 1483 1484 <td style="vertical-align: top;"><font color="#000000">Divergence 311 normalized with the total number of grid points.</td> </tr> 312 <tr> <td style="vertical-align: middle;">DISTENERG</td> 313 <td style="vertical-align: top;">Average resolved 314 disturbance energy of flow field (<font color="#000000">in 315 </font>m<sup>2</sup>/s<sup>2</sup>), 316 normalized with the total number of grid points.</td> </tr> 317 <tr> <td style="vertical-align: top;">DIVOLD</td> 318 <td style="vertical-align: top;"><font color="#000000">Divergence 1485 319 of the velocity field (sum of 1486 the absolute values) (</font><font color="#000000">in </font><font color="#000000">1/s) before call of the pressure solver, 320 the absolute values) (</font><font color="#000000">in 321 </font><font color="#000000">1/s) before call of the 322 pressure solver, 1487 323 normalized with the total number of grid points.</font></td> 1488 1489 1490 1491 1492 1493 </tr> 1494 1495 1496 1497 1498 1499 <tr> 1500 1501 1502 1503 1504 1505 <td style="vertical-align: top;">DIVNEW</td> 1506 1507 1508 1509 1510 1511 <td style="vertical-align: top;"><font color="#000000">Divergence 324 </tr> <tr> <td style="vertical-align: top;">DIVNEW</td> 325 <td style="vertical-align: top;"><font color="#000000">Divergence 1512 326 of the velocity field (sum of 1513 the absolute values) (</font><font color="#000000">in </font><font color="#000000">1/s) after call of the pressure solver, normalized</font> 1514 with the total number of grid points.</td> 1515 1516 1517 1518 1519 1520 </tr> 1521 1522 1523 1524 1525 1526 <tr> 1527 1528 1529 1530 1531 1532 <td style="vertical-align: top;">UMAX (KJI)</td> 1533 1534 1535 1536 1537 1538 <td style="vertical-align: top;">Indices of the grid point 327 the absolute values) (</font><font color="#000000">in 328 </font><font color="#000000">1/s) after call of the 329 pressure solver, normalized</font> 330 with the total number of grid points.</td> </tr> <tr> 331 <td style="vertical-align: top;">UMAX (KJI)</td> <td style="vertical-align: top;">Indices of the grid point 1539 332 with the maximum absolute 1540 u-component of the wind velocity (sequence: k, j, i).</td> 1541 1542 1543 1544 1545 1546 </tr> 1547 1548 1549 1550 1551 1552 <tr> 1553 1554 1555 1556 1557 1558 <td style="vertical-align: top;">VMAX (KJI)</td> 1559 1560 1561 1562 1563 1564 <td style="vertical-align: top;">Indices of the grid point 333 u-component of the wind velocity (sequence: k, j, i).</td> </tr> 334 <tr> <td style="vertical-align: top;">VMAX (KJI)</td> 335 <td style="vertical-align: top;">Indices of the grid point 1565 336 with the maximum absolute 1566 v-component of the wind velocity (sequence: k, j, i).</td> 1567 1568 1569 1570 1571 1572 </tr> 1573 1574 1575 1576 1577 1578 <tr> 1579 1580 1581 1582 1583 1584 <td style="vertical-align: top;">WMAX (KJI)</td> 1585 1586 1587 1588 1589 1590 <td style="vertical-align: top;">Indices of the grid point 337 v-component of the wind velocity (sequence: k, j, i).</td> </tr> 338 <tr> <td style="vertical-align: top;">WMAX (KJI)</td> 339 <td style="vertical-align: top;">Indices of the grid point 1591 340 with the maximum absolute 1592 w-component of the wind velocity (sequence: k, j, i).</td> 1593 1594 1595 1596 1597 1598 </tr> 1599 1600 1601 1602 1603 1604 <tr> 1605 1606 1607 1608 1609 1610 <td style="vertical-align: top;">ADVECX</td> 1611 1612 1613 1614 1615 1616 <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the 341 w-component of the wind velocity (sequence: k, j, i).</td> </tr> 342 <tr> <td style="vertical-align: top;">ADVECX</td> 343 <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the 1617 344 coordinate system has been moved in 1618 345 x-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td> 1619 1620 1621 1622 1623 1624 </tr> 1625 1626 1627 1628 1629 1630 <tr> 1631 1632 1633 1634 1635 1636 <td style="vertical-align: top;">ADVECY</td> 1637 1638 1639 1640 1641 1642 <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the 346 </tr> <tr> <td style="vertical-align: top;">ADVECY</td> 347 <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the 1643 348 coordinate system has been moved in 1644 349 y-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td> 1645 1646 1647 1648 1649 1650 </tr> 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 </tbody> 1662 1663 1664 1665 1666 1667 </table> 1668 1669 1670 1671 1672 1673 </td> 1674 1675 1676 1677 1678 1679 </tr> 1680 1681 1682 1683 1684 1685 <tr> 1686 1687 1688 1689 1690 1691 <td style="vertical-align: top; text-align: center;">16<br> 1692 1693 1694 1695 1696 1697 </td> 1698 1699 1700 1701 1702 1703 <td style="vertical-align: top;"><a name="LIST_PROFIL"></a>LIST_PROFIL 1704 </td> 1705 1706 1707 1708 1709 1710 <td style="vertical-align: top;">O<br> 1711 1712 1713 1714 1715 1716 </td> 1717 1718 1719 1720 1721 1722 <td style="vertical-align: top;">Ascii<br> 1723 1724 1725 1726 1727 1728 </td> 1729 1730 1731 1732 1733 1734 <td style="vertical-align: top;">This file contains horizontally 350 </tr> </tbody> </table> </td> </tr> <tr> 351 <td style="vertical-align: top; text-align: center;">16<br> 352 </td> <td style="vertical-align: top;"><a name="LIST_PROFIL"></a>LIST_PROFIL </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii<br> </td> <td style="vertical-align: top;">This file contains horizontally 1735 353 (and possibly temporally) 1736 354 averaged vertical profiles of some model variables. The quantities … … 1745 363 the respective subdomain (see <a href="chapter_4.3.html#region">region</a>) 1746 364 appears in the header of the respective table. <br> 1747 1748 1749 1750 1751 1752 365 In each case the tables consist of a header, followed by the 1753 366 profiles arranged next to each other in columns. The header contains … … 1757 370 computer, date, time of the beginning of the run, name of the 1758 371 subdomain, output time, kind of averaging). On the u-v-level the 1759 following columns are written: <br> 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 <table style="text-align: left; width: 100%;" cellpadding="2"> 1771 1772 1773 1774 1775 1776 <tbody> 1777 1778 1779 1780 1781 1782 <tr> 1783 1784 1785 1786 1787 1788 <td style="text-align: left; vertical-align: middle;">k<br> 1789 1790 1791 1792 1793 1794 </td> 1795 1796 1797 1798 1799 1800 <td style="text-align: left; vertical-align: middle;">Vertical 1801 grid point index.</td> 1802 1803 1804 1805 1806 1807 </tr> 1808 1809 1810 1811 1812 1813 <tr> 1814 1815 1816 1817 1818 1819 <td style="text-align: left; vertical-align: middle;">zu<br> 1820 1821 1822 1823 1824 1825 </td> 1826 1827 1828 1829 1830 1831 <td style="text-align: left; vertical-align: middle;">Height 372 following columns are written: <br> <table style="text-align: left; width: 100%;" cellpadding="2"> 373 <tbody> <tr> <td style="text-align: left; vertical-align: middle;">k<br> 374 </td> <td style="text-align: left; vertical-align: middle;">Vertical 375 grid point index.</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">zu<br> 376 </td> <td style="text-align: left; vertical-align: middle;">Height 1832 377 of the grid point 1833 378 level (<font color="#000000">in </font>m).</td> 1834 1835 1836 1837 1838 1839 </tr> 1840 1841 1842 1843 1844 1845 <tr> 1846 1847 1848 1849 1850 1851 <td style="text-align: left; vertical-align: middle;">u<br> 1852 1853 1854 1855 1856 1857 </td> 1858 1859 1860 1861 1862 1863 <td style="text-align: left; vertical-align: middle;">u-component 379 </tr> <tr> <td style="text-align: left; vertical-align: middle;">u<br> 380 </td> <td style="text-align: left; vertical-align: middle;">u-component 1864 381 of the wind 1865 382 velocity (<font color="#000000">in </font>m/s).</td> 1866 1867 1868 1869 1870 1871 </tr> 1872 1873 1874 1875 1876 1877 <tr> 1878 1879 1880 1881 1882 1883 <td style="text-align: left; vertical-align: middle;">du<br> 1884 1885 1886 1887 1888 1889 </td> 1890 1891 1892 1893 1894 1895 <td style="text-align: left; vertical-align: middle;">Deviation 383 </tr> <tr> <td style="text-align: left; vertical-align: middle;">du<br> 384 </td> <td style="text-align: left; vertical-align: middle;">Deviation 1896 385 of the 1897 386 u-component from the initial profile at the 1898 time t=0 (initialization profile) (<font color="#000000">in </font>m/s).</td> 1899 1900 1901 1902 1903 1904 </tr> 1905 1906 1907 1908 1909 1910 <tr> 1911 1912 1913 1914 1915 1916 <td style="text-align: left; vertical-align: middle;">v<br> 1917 1918 1919 1920 1921 1922 </td> 1923 1924 1925 1926 1927 1928 <td style="text-align: left; vertical-align: middle;">v-component 387 time t=0 (initialization profile) (<font color="#000000">in 388 </font>m/s).</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">v<br> 389 </td> <td style="text-align: left; vertical-align: middle;">v-component 1929 390 of the wind 1930 391 velocity (<font color="#000000">in </font>m/s).</td> 1931 1932 1933 1934 1935 1936 </tr> 1937 1938 1939 1940 1941 1942 <tr> 1943 1944 1945 1946 1947 1948 <td style="text-align: left; vertical-align: middle;">dv<br> 1949 1950 1951 1952 1953 1954 </td> 1955 1956 1957 1958 1959 1960 <td style="text-align: left; vertical-align: middle;">Deviation 392 </tr> <tr> <td style="text-align: left; vertical-align: middle;">dv<br> 393 </td> <td style="text-align: left; vertical-align: middle;">Deviation 1961 394 of the 1962 395 v-component from the initial profile at the 1963 time t=0 (initialization profile) (<font color="#000000">in </font>m/s).</td> 1964 1965 1966 1967 1968 1969 </tr> 1970 1971 1972 1973 1974 1975 <tr> 1976 1977 1978 1979 1980 1981 <td style="text-align: left; vertical-align: middle;">pt 1982 <br> 1983 1984 1985 1986 1987 1988 </td> 1989 1990 1991 1992 1993 1994 <td style="text-align: left; vertical-align: middle;">Potential 396 time t=0 (initialization profile) (<font color="#000000">in 397 </font>m/s).</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">pt 398 <br> </td> <td style="text-align: left; vertical-align: middle;">Potential 1995 399 temperature (<font color="#000000">in </font>K).</td> 1996 1997 1998 1999 2000 2001 </tr> 2002 2003 2004 2005 2006 2007 <tr> 2008 2009 2010 2011 2012 2013 <td style="text-align: left; vertical-align: middle;">dpt<br> 2014 2015 2016 2017 2018 2019 </td> 2020 2021 2022 2023 2024 2025 <td style="text-align: left; vertical-align: middle;">Deviation 400 </tr> <tr> <td style="text-align: left; vertical-align: middle;">dpt<br> 401 </td> <td style="text-align: left; vertical-align: middle;">Deviation 2026 402 of potential 2027 403 temperature from the initial profile at 2028 the time t=0 (initialization profile) (<font color="#000000">in </font>K).</td> 2029 2030 2031 2032 2033 2034 </tr> 2035 2036 2037 2038 2039 2040 <tr> 2041 2042 2043 2044 2045 2046 <td style="text-align: left; vertical-align: middle;">e<br> 2047 2048 2049 2050 2051 2052 </td> 2053 2054 2055 2056 2057 2058 <td style="text-align: left; vertical-align: middle;">Turbulent 404 the time t=0 (initialization profile) (<font color="#000000">in 405 </font>K).</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">e<br> 406 </td> <td style="text-align: left; vertical-align: middle;">Turbulent 2059 407 kinetic energy 2060 408 (subgrid-scale) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td> 2061 2062 2063 2064 2065 2066 </tr> 2067 2068 2069 2070 2071 2072 <tr> 2073 2074 2075 2076 2077 2078 <td style="text-align: left; vertical-align: middle;">Km<br> 2079 2080 2081 2082 2083 2084 </td> 2085 2086 2087 2088 2089 2090 <td style="text-align: left; vertical-align: middle;">Turbulent 409 </tr> <tr> <td style="text-align: left; vertical-align: middle;">Km<br> 410 </td> <td style="text-align: left; vertical-align: middle;">Turbulent 2091 411 diffusion 2092 412 coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td> 2093 2094 2095 2096 2097 2098 </tr> 2099 2100 2101 2102 2103 2104 <tr> 2105 2106 2107 2108 2109 2110 <td style="text-align: left; vertical-align: middle;">Kh<br> 2111 2112 2113 2114 2115 2116 </td> 2117 2118 2119 2120 2121 2122 <td style="text-align: left; vertical-align: middle;">Turbulent 413 </tr> <tr> <td style="text-align: left; vertical-align: middle;">Kh<br> 414 </td> <td style="text-align: left; vertical-align: middle;">Turbulent 2123 415 diffusion 2124 416 coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td> 2125 2126 2127 2128 2129 2130 </tr> 2131 2132 2133 2134 2135 2136 <tr> 2137 2138 2139 2140 2141 2142 <td style="text-align: left; vertical-align: middle;">l<br> 2143 2144 2145 2146 2147 2148 </td> 2149 2150 2151 2152 2153 2154 <td style="text-align: left; vertical-align: middle;">Mixing 417 </tr> <tr> <td style="text-align: left; vertical-align: middle;">l<br> 418 </td> <td style="text-align: left; vertical-align: middle;">Mixing 2155 419 length (<font color="#000000">in </font>m).</td> 2156 2157 2158 2159 2160 2161 </tr> 2162 2163 2164 2165 2166 2167 <tr> 2168 2169 2170 2171 2172 2173 <td style="vertical-align: top;"><br> 2174 2175 2176 2177 2178 2179 </td> 2180 2181 2182 2183 2184 2185 <td style="vertical-align: top;"><br> 2186 2187 2188 2189 2190 2191 </td> 2192 2193 2194 2195 2196 2197 </tr> 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 </tbody> 2209 2210 2211 2212 2213 2214 </table> 2215 2216 2217 2218 2219 2220 On the w-level the following columns are written:<br> 2221 2222 2223 2224 2225 2226 <br> 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 <table style="text-align: left; width: 100%;" cellpadding="2"> 2238 2239 2240 2241 2242 2243 <tbody> 2244 2245 2246 2247 2248 2249 <tr> 2250 2251 2252 2253 2254 2255 <td style="vertical-align: middle;">k<br> 2256 2257 2258 2259 2260 2261 </td> 2262 2263 2264 2265 2266 2267 <td style="vertical-align: middle;">Vertical grid point 2268 index.</td> 2269 2270 2271 2272 2273 2274 </tr> 2275 2276 2277 2278 2279 2280 <tr> 2281 2282 2283 2284 2285 2286 <td style="vertical-align: middle;">zw<br> 2287 2288 2289 2290 2291 2292 </td> 2293 2294 2295 2296 2297 2298 <td style="vertical-align: middle;">Height of the grid 420 </tr> <tr> <td style="vertical-align: top;"><br> 421 </td> <td style="vertical-align: top;"><br> </td> 422 </tr> </tbody> </table> 423 On the w-level the following columns are written:<br> <br> 424 <table style="text-align: left; width: 100%;" cellpadding="2"> 425 <tbody> <tr> <td style="vertical-align: middle;">k<br> 426 </td> <td style="vertical-align: middle;">Vertical 427 grid point 428 index.</td> </tr> <tr> <td style="vertical-align: middle;">zw<br> </td> <td style="vertical-align: middle;">Height of the grid 2299 429 point 2300 430 level (<font color="#000000">in </font>m).</td> 2301 2302 2303 2304 2305 2306 </tr> 2307 2308 2309 2310 2311 2312 <tr> 2313 2314 2315 2316 2317 2318 <td style="vertical-align: middle;">w'pt'</td> 2319 2320 2321 2322 2323 2324 <td style="vertical-align: middle;">Vertical subgrid-scale 2325 kinematic heat flux (<font color="#000000">in </font>K m/s).</td> 2326 2327 2328 2329 2330 2331 </tr> 2332 2333 2334 2335 2336 2337 <tr> 2338 2339 2340 2341 2342 2343 <td style="vertical-align: middle;">wpt</td> 2344 2345 2346 2347 2348 2349 <td style="vertical-align: middle;">Vertical total ( 431 </tr> <tr> <td style="vertical-align: middle;">w'pt'</td> 432 <td style="vertical-align: middle;">Vertical subgrid-scale 433 kinematic heat flux (<font color="#000000">in </font>K 434 m/s).</td> </tr> <tr> <td style="vertical-align: middle;">wpt</td> <td style="vertical-align: middle;">Vertical total ( 2350 435 subgrid-scale + resolved) 2351 kinematic heat flux (<font color="#000000">in </font>K m/s).</td> 2352 2353 2354 2355 2356 2357 </tr> 2358 2359 2360 2361 2362 2363 <tr> 2364 2365 2366 2367 2368 2369 <td style="vertical-align: middle;">w'u'</td> 2370 2371 2372 2373 2374 2375 <td style="vertical-align: middle;">u-component of the 2376 vertical subgrid-scale momentum flux (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td> 2377 2378 2379 2380 2381 2382 </tr> 2383 2384 2385 2386 2387 2388 <tr> 2389 2390 2391 2392 2393 2394 <td style="vertical-align: middle;">wu</td> 2395 2396 2397 2398 2399 2400 <td style="vertical-align: middle;">u-component of the 436 kinematic heat flux (<font color="#000000">in </font>K 437 m/s).</td> </tr> <tr> <td style="vertical-align: middle;">w'u'</td> <td style="vertical-align: middle;">u-component of the 438 vertical subgrid-scale momentum flux (<font color="#000000">in 439 </font>m<sup>2</sup>/s<sup>2</sup>).</td> 440 </tr> <tr> <td style="vertical-align: middle;">wu</td> 441 <td style="vertical-align: middle;">u-component of the 2401 442 total 2402 443 vertical momentum flux ( 2403 444 subgrid-scale + resolved) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td> 2404 2405 2406 2407 2408 2409 </tr> 2410 2411 2412 2413 2414 2415 <tr> 2416 2417 2418 2419 2420 2421 <td style="vertical-align: middle;">w'v'</td> 2422 2423 2424 2425 2426 2427 <td style="vertical-align: middle;">v-component of the 2428 vertical subgrid-scale momentum flux (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td> 2429 2430 2431 2432 2433 2434 </tr> 2435 2436 2437 2438 2439 2440 <tr> 2441 2442 2443 2444 2445 2446 <td style="vertical-align: middle;">wv</td> 2447 2448 2449 2450 2451 2452 <td style="vertical-align: middle;">v-component of the 445 </tr> <tr> <td style="vertical-align: middle;">w'v'</td> 446 <td style="vertical-align: middle;">v-component of the 447 vertical subgrid-scale momentum flux (<font color="#000000">in 448 </font>m<sup>2</sup>/s<sup>2</sup>).</td> 449 </tr> <tr> <td style="vertical-align: middle;">wv</td> 450 <td style="vertical-align: middle;">v-component of the 2453 451 total 2454 452 vertical momentum flux ( 2455 453 subgrid-scale + resolved) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td> 2456 2457 2458 2459 2460 2461 </tr> 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 </tbody> 2473 2474 2475 2476 2477 2478 </table> 2479 2480 2481 2482 2483 2484 <br> 2485 2486 2487 2488 2489 2490 </td> 2491 2492 2493 2494 2495 2496 </tr> 2497 2498 2499 2500 2501 2502 <tr> 2503 2504 2505 2506 2507 2508 <td style="vertical-align: top; text-align: center;">17 </td> 2509 2510 2511 2512 2513 2514 <td style="vertical-align: top;"><a name="LIST_PROFIL_1D"></a>LIST_PROFIL_1D 2515 </td> 2516 2517 2518 2519 2520 2521 <td style="vertical-align: top;">O </td> 2522 2523 2524 2525 2526 2527 <td style="vertical-align: top;">Ascii </td> 2528 2529 2530 2531 2532 2533 <td style="vertical-align: top;">This file contains the vertical 454 </tr> </tbody> </table> <br> </td> </tr> 455 <tr> <td style="vertical-align: top; text-align: center;">17 456 </td> <td style="vertical-align: top;"><a name="LIST_PROFIL_1D"></a>LIST_PROFIL_1D </td> <td style="vertical-align: top;">O </td> <td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;">This file contains the vertical 2534 457 profiles calculated by the 2535 458 1D-model within initial runs. The quantities saved are set … … 2543 466 only switched on at initial runs), executing computer, date, 2544 467 time of the beginning of the run, output time). Afterwards the 2545 following columns appear:<br> 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 <table style="text-align: left; width: 100%;" cellpadding="2"> 2557 2558 2559 2560 2561 2562 <tbody> 2563 2564 2565 2566 2567 2568 <tr> 2569 2570 2571 2572 2573 2574 <td style="text-align: left; vertical-align: middle;">k<br> 2575 2576 2577 2578 2579 2580 </td> 2581 2582 2583 2584 2585 2586 <td style="text-align: left; vertical-align: middle;">Vertical 2587 grid point index.</td> 2588 2589 2590 2591 2592 2593 </tr> 2594 2595 2596 2597 2598 2599 <tr> 2600 2601 2602 2603 2604 2605 <td style="text-align: left; vertical-align: middle;">zu<br> 2606 2607 2608 2609 2610 2611 </td> 2612 2613 2614 2615 2616 2617 <td style="text-align: left; vertical-align: middle;">Height 468 following columns appear:<br> <table style="text-align: left; width: 100%;" cellpadding="2"> 469 <tbody> <tr> <td style="text-align: left; vertical-align: middle;">k<br> 470 </td> <td style="text-align: left; vertical-align: middle;">Vertical 471 grid point index.</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">zu<br> 472 </td> <td style="text-align: left; vertical-align: middle;">Height 2618 473 of the grid point 2619 474 level (<font color="#000000">in </font>m).</td> 2620 2621 2622 2623 2624 2625 </tr> 2626 2627 2628 2629 2630 2631 <tr> 2632 2633 2634 2635 2636 2637 <td style="text-align: left; vertical-align: middle;">u<br> 2638 2639 2640 2641 2642 2643 </td> 2644 2645 2646 2647 2648 2649 <td style="text-align: left; vertical-align: middle;">u-component 475 </tr> <tr> <td style="text-align: left; vertical-align: middle;">u<br> 476 </td> <td style="text-align: left; vertical-align: middle;">u-component 2650 477 of the wind 2651 478 velocity (<font color="#000000">in </font>m/s).</td> 2652 2653 2654 2655 2656 2657 </tr> 2658 2659 2660 2661 2662 2663 <tr> 2664 2665 2666 2667 2668 2669 <td style="text-align: left; vertical-align: middle;">v<br> 2670 2671 2672 2673 2674 2675 </td> 2676 2677 2678 2679 2680 2681 <td style="text-align: left; vertical-align: middle;">v-component 479 </tr> <tr> <td style="text-align: left; vertical-align: middle;">v<br> 480 </td> <td style="text-align: left; vertical-align: middle;">v-component 2682 481 of the wind 2683 482 velocity (<font color="#000000">in </font>m/s).</td> 2684 2685 2686 2687 2688 2689 </tr> 2690 2691 2692 2693 2694 2695 <tr> 2696 2697 2698 2699 2700 2701 <td style="text-align: left; vertical-align: middle;">pt<br> 2702 2703 2704 2705 2706 2707 </td> 2708 2709 2710 2711 2712 2713 <td style="text-align: left; vertical-align: middle;">Potential 483 </tr> <tr> <td style="text-align: left; vertical-align: middle;">pt<br> 484 </td> <td style="text-align: left; vertical-align: middle;">Potential 2714 485 temperature (<font color="#000000">in </font>K).</td> 2715 2716 2717 2718 2719 2720 </tr> 2721 2722 2723 2724 2725 2726 <tr> 2727 2728 2729 2730 2731 2732 <td style="text-align: left; vertical-align: middle;">e<br> 2733 2734 2735 2736 2737 2738 </td> 2739 2740 2741 2742 2743 2744 <td style="text-align: left; vertical-align: middle;">Turbulent 486 </tr> <tr> <td style="text-align: left; vertical-align: middle;">e<br> 487 </td> <td style="text-align: left; vertical-align: middle;">Turbulent 2745 488 kinetic energy (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td> 2746 2747 2748 2749 2750 2751 </tr> 2752 2753 2754 2755 2756 2757 <tr> 2758 2759 2760 2761 2762 2763 <td style="text-align: left; vertical-align: middle;">rif<br> 2764 2765 2766 2767 2768 2769 </td> 2770 2771 2772 2773 2774 2775 <td style="text-align: left; vertical-align: middle;">Flux 2776 Richardson number</td> 2777 2778 2779 2780 2781 2782 </tr> 2783 2784 2785 2786 2787 2788 <tr> 2789 2790 2791 2792 2793 2794 <td style="text-align: left; vertical-align: middle;">Km<br> 2795 2796 2797 2798 2799 2800 </td> 2801 2802 2803 2804 2805 2806 <td style="text-align: left; vertical-align: middle;">Turbulent 489 </tr> <tr> <td style="text-align: left; vertical-align: middle;">rif<br> 490 </td> <td style="text-align: left; vertical-align: middle;">Flux 491 Richardson number</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">Km<br> 492 </td> <td style="text-align: left; vertical-align: middle;">Turbulent 2807 493 diffusion 2808 494 coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td> 2809 2810 2811 2812 2813 2814 </tr> 2815 2816 2817 2818 2819 2820 <tr> 2821 2822 2823 2824 2825 2826 <td style="text-align: left; vertical-align: middle;">Kh<br> 2827 2828 2829 2830 2831 2832 </td> 2833 2834 2835 2836 2837 2838 <td style="text-align: left; vertical-align: middle;">Turbulent 495 </tr> <tr> <td style="text-align: left; vertical-align: middle;">Kh<br> 496 </td> <td style="text-align: left; vertical-align: middle;">Turbulent 2839 497 diffusion 2840 498 coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td> 2841 2842 2843 2844 2845 2846 </tr> 2847 2848 2849 2850 2851 2852 <tr> 2853 2854 2855 2856 2857 2858 <td style="text-align: left; vertical-align: middle;">l<br> 2859 2860 2861 2862 2863 2864 </td> 2865 2866 2867 2868 2869 2870 <td style="text-align: left; vertical-align: middle;"><font color="#000000">Mixing 2871 length (</font><font color="#000000">in </font><font color="#000000">m).</font></td> 2872 2873 2874 2875 2876 2877 </tr> 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 </tbody> 2889 2890 2891 2892 2893 2894 </table> 2895 2896 2897 2898 2899 2900 <br> 2901 2902 2903 2904 2905 2906 </td> 2907 2908 2909 2910 2911 2912 </tr> 2913 2914 2915 2916 2917 2918 <tr> 2919 2920 2921 2922 2923 2924 <td style="vertical-align: top; text-align: center;">18 </td> 2925 2926 2927 2928 2929 2930 <td style="vertical-align: top;"><a name="CPU_MEASURES"></a>CPU_MEASURES 2931 </td> 2932 2933 2934 2935 2936 2937 <td style="vertical-align: top;">O </td> 2938 2939 2940 2941 2942 2943 <td style="vertical-align: top;">Ascii </td> 2944 2945 2946 2947 2948 2949 <td style="vertical-align: top;">Time measurements are 499 </tr> <tr> <td style="text-align: left; vertical-align: middle;">l<br> 500 </td> <td style="text-align: left; vertical-align: middle;"><font color="#000000">Mixing 501 length (</font><font color="#000000">in </font><font color="#000000">m).</font></td> </tr> </tbody> 502 </table> <br> </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">18 </td> 503 <td style="vertical-align: top;"><a name="CPU_MEASURES"></a>CPU_MEASURES 504 </td> <td style="vertical-align: top;">O </td> 505 <td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;">Time measurements are 2950 506 accomplished through the subroutine <span style="font-family: monospace;">cpu_log.f90.</span><span style="font-size: 10pt;"></span> The file 2951 507 CPU_MEASURES contains a header with some basic information of the … … 2956 512 times which have been consumed by certain model parts. The model parts 2957 513 analyzed in the first table do not overlap and the CPU times needed for 2958 them therefore approximately add up to the “total” value given in the 514 them therefore approximately add up to the “total” 515 value given in the 2959 516 first line of this table. In the second table (heading: special 2960 517 measures) overlaps (in particular with the parts described in the first 2961 518 table) are possible. <br> 2962 2963 2964 2965 2966 2967 519 For each model part it is indicated in the following columns how much 2968 520 CPU time was needed (absolutely and relative), and how often it was 2969 called. With runs on several processors the average values of all 521 called. With runs on several processors the average values of 522 all 2970 523 processors are indicated. In the case of parallel runs information for 2971 524 those processors with the largest and smallest CPU time follow as … … 2974 527 parallelization the CPU times on the individual processors should 2975 528 differ only little from each other and the standard deviation should be 2976 small. </td> 2977 2978 2979 2980 2981 2982 </tr> 2983 2984 2985 2986 2987 2988 <tr> 2989 2990 2991 2992 2993 2994 <td style="vertical-align: top; text-align: center;">19 </td> 2995 2996 2997 2998 2999 3000 <td style="vertical-align: top;"><a name="HEADER"></a>HEADER </td> 3001 3002 3003 3004 3005 3006 <td style="vertical-align: top;">O </td> 3007 3008 3009 3010 3011 3012 <td style="vertical-align: top;">Ascii </td> 3013 3014 3015 3016 3017 3018 <td style="vertical-align: top;"> 3019 3020 3021 3022 3023 3024 <p>Information about the selected model parameters (physical and 3025 numerical values) as well as general information about the run. </p> 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 <p>This file contains the values of all important steering 529 small. </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">19 </td> 530 <td style="vertical-align: top;"><a name="HEADER"></a>HEADER 531 </td> <td style="vertical-align: top;">O </td> 532 <td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;"> <p>Information about 533 the selected model parameters (physical and 534 numerical values) as well as general information about the 535 run. </p> <p>This file contains the values of 536 all important steering 3037 537 parameters 3038 538 (numerical procedures, computing grid and model dimensions, boundary … … 3054 554 time reached is missing etc.) and then briefly before the normal end of 3055 555 the simulation. The second, now complete output overwrites the first 3056 output.). </p> 3057 3058 3059 3060 3061 3062 3063 3064 3065 3066 3067 <p>At the end of the file, information about the values of user 556 output.). </p> <p>At the end of the file, 557 information about the values of user 3068 558 parameters (see <a href="chapter_3.7.html">chapter 3069 559 3.7</a> and <a href="targetliste:chapter_1.0.html#chapter%204.3">chapter 3070 4.3</a>) can be output by the user with the help of the subroutine <tt><font style="font-size: 11pt;" size="2">user_header</font></tt> (located in 560 4.3</a>) can be output by the user with the help of the 561 subroutine <tt><font style="font-size: 11pt;" size="2">user_header</font></tt> 562 (located in 3071 563 the file <tt><font style="font-size: 10pt;" size="2">user_interface.f90</font></tt>). 3072 If no user parameters were found, the string “<tt><font style="font-size: 10pt;" size="2">*** no user-defined variables found</font></tt>” 564 If no user parameters were found, the string “<tt><font style="font-size: 10pt;" size="2">*** no user-defined 565 variables found</font></tt>” 3073 566 appears at the end of the file. 3074 If user parameters were indicated, the string “<tt><font style="font-size: 11pt;" size="2">user-defined variables and actions</font></tt>” 567 If user parameters were indicated, the string “<tt><font style="font-size: 11pt;" size="2">user-defined 568 variables and actions</font></tt>” 3075 569 is printed, followed by informations about the user-defined subdomains 3076 570 for which 3077 571 profiles and time series are output. All further information to appear 3078 572 here, must be provided by the user (by appropriate 3079 WRITE statements in <tt><font style="font-size: 10pt;" size="2">user_header</font></tt>).</p> 3080 3081 3082 3083 3084 3085 </td> 3086 3087 3088 3089 3090 3091 </tr> 3092 3093 3094 3095 3096 3097 <tr> 3098 3099 3100 3101 3102 3103 <td style="vertical-align: top; text-align: center;">21 </td> 3104 3105 3106 3107 3108 3109 <td style="vertical-align: top;"><a name="PLOT2D_XY"></a>PLOT2D_XY 3110 </td> 3111 3112 3113 3114 3115 3116 <td style="vertical-align: top;">O<br> 3117 3118 3119 3120 3121 3122 </td> 3123 3124 3125 3126 3127 3128 <td style="vertical-align: top;">Binary<br> 3129 3130 3131 3132 3133 3134 </td> 3135 3136 3137 3138 3139 3140 <td style="vertical-align: top;"> 3141 3142 3143 3144 3145 3146 <p>This file contains data of the two-dimensional horizontal 573 WRITE statements in <tt><font style="font-size: 10pt;" size="2">user_header</font></tt>).</p> </td> 574 </tr> <tr> <td style="vertical-align: top; text-align: center;">21 </td> 575 <td style="vertical-align: top;"><a name="PLOT2D_XY"></a>PLOT2D_XY 576 </td> <td style="vertical-align: top;">O<br> </td> 577 <td style="vertical-align: top;">Binary<br> </td> 578 <td style="vertical-align: top;"> <p>This file 579 contains data of the two-dimensional horizontal 3147 580 cross sections written by the model (see <a href="chapter_4.2.html#data_output">data_output</a>) 3148 581 in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a> 3149 (the first record contains the coordinate information <tt><font style="font-size: 11pt;" size="2">dx</font></tt><font style="font-size: 11pt;" size="2">, </font><tt><font style="font-size: 11pt;" size="2">eta</font></tt><font style="font-size: 11pt;" size="2">, </font><tt><font style="font-size: 11pt;" size="2">hu</font></tt><font style="font-size: 11pt;" size="2">, <tt>ho</tt></font>, then 582 (the first record contains the coordinate information <tt><font style="font-size: 11pt;" size="2">dx</font></tt><font style="font-size: 11pt;" size="2">, </font><tt><font style="font-size: 11pt;" size="2">eta</font></tt><font style="font-size: 11pt;" size="2">, </font><tt><font style="font-size: 11pt;" size="2">hu</font></tt><font style="font-size: 11pt;" size="2">, <tt>ho</tt></font>, 583 then 3150 584 the individual arrays follow). The data are visualized with the help of 3151 585 ISO2D using … … 3153 587 the 3154 588 local files <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a> 3155 and <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>. </p> 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166 <p>With parallel runs and choice of <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a> 3167 = <i>.T.</i> each processing element writes the data of its subdomain 3168 to a separate file with the name PLOT2D_XY_<processor-Id>, 589 and <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>. 590 </p> <p>With parallel runs and choice of <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a> 591 = <i>.T.</i> each processing element writes the data of 592 its subdomain 593 to a separate file with the name 594 PLOT2D_XY_<processor-Id>, 3169 595 whereby <processor-Id> is a four digit number (e.g. 3170 596 PLOT2D_XY_0000). These files are not suitable for ISO2D, but after the … … 3182 608 possibly existing files of the other cross sections (xz and/or yz) 3183 609 and three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>) 3184 are also combined. </p> 3185 3186 3187 3188 3189 3190 3191 3192 3193 3194 3195 <p>Further information about the output of plots of 610 are also combined. </p> <p>Further information 611 about the output of plots of 3196 612 two-dimensional cross sections is found in the description of the run 3197 613 parameter <a href="chapter_4.2.html#data_output">data_output</a>.</p> 3198 3199 3200 3201 3202 3203 </td> 3204 3205 3206 3207 3208 3209 </tr> 3210 3211 3212 3213 3214 3215 <tr> 3216 3217 3218 3219 3220 3221 <td style="vertical-align: top; text-align: center;">22<br> 3222 3223 3224 3225 3226 3227 </td> 3228 3229 3230 3231 3232 3233 <td style="vertical-align: top;"><a name="PLOT2D_XZ"></a>PLOT2D_XZ 3234 </td> 3235 3236 3237 3238 3239 3240 <td style="vertical-align: top;">O<br> 3241 3242 3243 3244 3245 3246 </td> 3247 3248 3249 3250 3251 3252 <td style="vertical-align: top;">Binary<br> 3253 3254 3255 3256 3257 3258 </td> 3259 3260 3261 3262 3263 3264 <td style="vertical-align: top;"> 3265 3266 3267 3268 3269 3270 <p>This file contains the data of the xz 614 </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">22<br> 615 </td> <td style="vertical-align: top;"><a name="PLOT2D_XZ"></a>PLOT2D_XZ </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Binary<br> </td> <td style="vertical-align: top;"> <p>This file contains 616 the data of the xz 3271 617 cross sections written by the model. </p> 3272 3273 3274 3275 3276 3277 618 The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a> 3278 applies to this file, respectively </td> 3279 3280 3281 3282 3283 3284 </tr> 3285 3286 3287 3288 3289 3290 <tr> 3291 3292 3293 3294 3295 3296 <td style="vertical-align: top; text-align: center;">23<br> 3297 3298 3299 3300 3301 3302 </td> 3303 3304 3305 3306 3307 3308 <td style="vertical-align: top;"><a name="PLOT2D_YZ"></a>PLOT2D_YZ 3309 </td> 3310 3311 3312 3313 3314 3315 <td style="vertical-align: top;">O<br> 3316 3317 3318 3319 3320 3321 </td> 3322 3323 3324 3325 3326 3327 <td style="vertical-align: top;">Binary<br> 3328 3329 3330 3331 3332 3333 </td> 3334 3335 3336 3337 3338 3339 <td style="vertical-align: top;"> 3340 3341 3342 3343 3344 3345 <p>This file contains the data of the xz 619 applies to this file, respectively </td> </tr> <tr> 620 <td style="vertical-align: top; text-align: center;">23<br> 621 </td> <td style="vertical-align: top;"><a name="PLOT2D_YZ"></a>PLOT2D_YZ </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Binary<br> </td> <td style="vertical-align: top;"> <p>This file contains 622 the data of the xz 3346 623 cross sections written by the model. </p> 3347 3348 3349 3350 3351 3352 624 The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a> 3353 applies to this file, respectively </td> 3354 3355 3356 3357 3358 3359 </tr> 3360 3361 3362 3363 3364 3365 <tr> 3366 3367 3368 3369 3370 3371 <td style="vertical-align: top; text-align: center;">27<br> 3372 3373 3374 3375 3376 3377 </td> 3378 3379 3380 3381 3382 3383 <td style="vertical-align: top;"><a name="PLOT2D_XY_LOCAL"></a>PLOT2D_XY_LOCAL 3384 </td> 3385 3386 3387 3388 3389 3390 <td style="vertical-align: top;">O<br> 3391 3392 3393 3394 3395 3396 </td> 3397 3398 3399 3400 3401 3402 <td style="vertical-align: top;">Ascii/ NAMELIST<br> 3403 3404 3405 3406 3407 3408 </td> 3409 3410 3411 3412 3413 3414 <td style="vertical-align: top;"> 3415 3416 3417 3418 3419 3420 <p>NAMELIST - parameter sets, with which the plot layout of the 625 applies to this file, respectively </td> </tr> <tr> 626 <td style="vertical-align: top; text-align: center;">27<br> 627 </td> <td style="vertical-align: top;"><a name="PLOT2D_XY_LOCAL"></a>PLOT2D_XY_LOCAL </td> 628 <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ NAMELIST<br> </td> 629 <td style="vertical-align: top;"> <p>NAMELIST - 630 parameter sets, with which the plot layout of the 3421 631 data in the local file <a href="#PLOT2D_XY">PLOT2D_XY</a> 3422 632 can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a>. 3423 633 This file contains the so-called local parameter set (NAMELIST - group 3424 name: &LOCAL) required by ISO2D (one parameter set for each field 634 name: &LOCAL) required by ISO2D (one parameter set for each 635 field 3425 636 present at the file PLOT2D_XY). After the model run these parameter 3426 sets can be edited by the user, if neccessary. </p> 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 <p>Additionally ISO2D still needs another so-called global 637 sets can be edited by the user, if neccessary. </p> <p>Additionally 638 ISO2D still needs another so-called global 3438 639 parameter set. This is saved by the model to the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>. 3439 640 Due to the fact that ISO2D expects global and local parameter sets on … … 3443 644 contents of the file PLOT2D_XY_LOCAL to the file PLOT2D_XY_GLOBAL 3444 645 before the call of ISO2D (e.g. by an OUTPUT-command in the 3445 MRUN-configuration file: “PLOT2D_XY_LOCAL >> PLOT2D_XY_GLOBAL”). 646 MRUN-configuration file: “PLOT2D_XY_LOCAL >> 647 PLOT2D_XY_GLOBAL”). 3446 648 This relatively pedantic proceeding is due to the fact that the model 3447 649 can produce the file PLOT2D_XY_GLOBAL only at the end of the simulation 3448 650 (only then e.g. when the final value of the global ISO2D - parameter <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#PLANZ">planz</a> 3449 651 is known), while the local parameter sets are written continuously 3450 to the file PLOT2D_XY_LOCAL during the run.</p> 3451 3452 3453 3454 3455 3456 </td> 3457 3458 3459 3460 3461 3462 </tr> 3463 3464 3465 3466 3467 3468 <tr> 3469 3470 3471 3472 3473 3474 <td style="vertical-align: top; text-align: center;">28<br> 3475 3476 3477 3478 3479 3480 </td> 3481 3482 3483 3484 3485 3486 <td style="vertical-align: top;"><a name="PLOT2D_XZ_LOCAL"></a>PLOT2D_XZ_LOCAL 3487 </td> 3488 3489 3490 3491 3492 3493 <td style="vertical-align: top;">O<br> 3494 3495 3496 3497 3498 3499 </td> 3500 3501 3502 3503 3504 3505 <td style="vertical-align: top;">Ascii/ NAMELIST<br> 3506 3507 3508 3509 3510 3511 </td> 3512 3513 3514 3515 3516 3517 <td style="vertical-align: top;"> 3518 3519 3520 3521 3522 3523 <p>NAMELIST - parameter sets, with which the plot layout of the 652 to the file PLOT2D_XY_LOCAL during the run.</p> </td> </tr> 653 <tr> <td style="vertical-align: top; text-align: center;">28<br> 654 </td> <td style="vertical-align: top;"><a name="PLOT2D_XZ_LOCAL"></a>PLOT2D_XZ_LOCAL </td> 655 <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ NAMELIST<br> </td> 656 <td style="vertical-align: top;"> <p>NAMELIST - 657 parameter sets, with which the plot layout of the 3524 658 data in the local file <a href="#PLOT2D_XZ">PLOT2D_XZ</a> 3525 659 can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a>. 3526 </p> 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a> 3538 applies to this file, respectively. </p> 3539 3540 3541 3542 3543 3544 </td> 3545 3546 3547 3548 3549 3550 </tr> 3551 3552 3553 3554 3555 3556 <tr> 3557 3558 3559 3560 3561 3562 <td style="vertical-align: top; text-align: center;">29<br> 3563 3564 3565 3566 3567 3568 </td> 3569 3570 3571 3572 3573 3574 <td style="vertical-align: top;"><a name="PLOT2D_YZ_LOCAL"></a>PLOT2D_YZ_LOCAL 3575 </td> 3576 3577 3578 3579 3580 3581 <td style="vertical-align: top;">O<br> 3582 3583 3584 3585 3586 3587 </td> 3588 3589 3590 3591 3592 3593 <td style="vertical-align: top;">Ascii/ NAMELIST<br> 3594 3595 3596 3597 3598 3599 </td> 3600 3601 3602 3603 3604 3605 <td style="vertical-align: top;"> 3606 3607 3608 3609 3610 3611 <p>NAMELIST - parameter sets, with which the plot layout of the 660 </p> <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a> 661 applies to this file, respectively. </p> </td> </tr> 662 <tr> <td style="vertical-align: top; text-align: center;">29<br> 663 </td> <td style="vertical-align: top;"><a name="PLOT2D_YZ_LOCAL"></a>PLOT2D_YZ_LOCAL </td> 664 <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ NAMELIST<br> </td> 665 <td style="vertical-align: top;"> <p>NAMELIST - 666 parameter sets, with which the plot layout of the 3612 667 data in the local file <a href="#PLOT2D_YZ">PLOT2D_YZ</a> 3613 668 can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a>. 3614 </p> 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a> 3626 applies to this file, respectively. </p> 3627 3628 3629 3630 3631 3632 </td> 3633 3634 3635 3636 3637 3638 </tr> 3639 3640 3641 3642 3643 3644 <tr> 3645 3646 3647 3648 3649 3650 <td style="vertical-align: top; text-align: center;">30<br> 3651 3652 3653 3654 3655 3656 </td> 3657 3658 3659 3660 3661 3662 <td style="vertical-align: top;"><a name="PLOT3D_DATA"></a>PLOT3D_DATA 3663 </td> 3664 3665 3666 3667 3668 3669 <td style="vertical-align: top;">O<br> 3670 3671 3672 3673 3674 3675 </td> 3676 3677 3678 3679 3680 3681 <td style="vertical-align: top;">Binary<br> 3682 3683 3684 3685 3686 3687 </td> 3688 3689 3690 3691 3692 3693 <td style="vertical-align: top;"> 3694 3695 3696 3697 3698 3699 <p>This file contains the data of the three-dimensional arrays 669 </p> <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a> 670 applies to this file, respectively. </p> </td> </tr> 671 <tr> <td style="vertical-align: top; text-align: center;">30<br> 672 </td> <td style="vertical-align: top;"><a name="PLOT3D_DATA"></a>PLOT3D_DATA </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Binary<br> </td> <td style="vertical-align: top;"> <p>This file contains 673 the data of the three-dimensional arrays 3700 674 (see <a href="chapter_4.2.html#data_output">data_output</a>) 3701 675 written by the model in a format readable for the visualization … … 3710 684 -) file, the content of the file PLOT3D_FLD_COOR must be appended to 3711 685 the file PLOT3D_FLD by the user after the end of the model run (e.g. 3712 with an appropriate OUTPUT - command in the MRUN - configuration file: "<span style="font-family: monospace;">cat PLOT3D_FLD_COOR >> PLOT3D_FLD</span>"). 3713 </p> 3714 3715 3716 3717 3718 3719 3720 3721 3722 3723 3724 <p>With parallel runs each processing element writes the data of 686 with an appropriate OUTPUT - command in the MRUN - configuration file: "<span style="font-family: monospace;">cat PLOT3D_FLD_COOR 687 >> PLOT3D_FLD</span>"). </p> <p>With 688 parallel runs each processing element writes the data of 3725 689 its subdomain to a separate file with the name 3726 PLOT3D_DATA_<Processor-Id>, where <Processor-Id> is a 690 PLOT3D_DATA_<Processor-Id>, where 691 <Processor-Id> is a 3727 692 four digit number (e.g. PLOT3D_DATA_0000). These files are not suitable 3728 693 for AVS, but after the end of the model run they can be combined to one … … 3736 701 found). By the call of <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt> 3737 702 also possibly existing files with two-dimensional plot data (see e.g. <a href="#PLOT2D_XY">PLOT2D_XY</a>) 3738 are combined. </p> 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 <p>With parallel runs the output of data of large volume is also 703 are combined. </p> <p>With parallel runs the 704 output of data of large volume is also 3750 705 possible in compressed form. For this purpose the initialization 3751 706 parameter <a href="chapter_4.2.html#do3d_compress">do3d_compress</a> 3752 = <i>.TRUE.</i> must be set and the desired output accuracy has to be 707 = <i>.TRUE.</i> must be set and the desired output 708 accuracy has to be 3753 709 indicated 3754 710 with the help of <a href="chapter_4.2.html#do3d_precision">do3d_precision</a>. … … 3758 714 and a further entry in the MRUN-configuration file are needed. More 3759 715 details can be found in <a href="chapter_4.5.6.html">chapter 3760 4.5.6</a>.</p> 3761 3762 3763 3764 3765 3766 </td> 3767 3768 3769 3770 3771 3772 </tr> 3773 3774 3775 3776 3777 3778 <tr> 3779 3780 3781 3782 3783 3784 <td style="vertical-align: top; text-align: center;">31<br> 3785 3786 3787 3788 3789 3790 </td> 3791 3792 3793 3794 3795 3796 <td style="vertical-align: top;"><a name="PLOT3D_COOR"></a>PLOT3D_COOR 3797 </td> 3798 3799 3800 3801 3802 3803 <td style="vertical-align: top;">O<br> 3804 3805 3806 3807 3808 3809 </td> 3810 3811 3812 3813 3814 3815 <td style="vertical-align: top;">Binary<br> 3816 3817 3818 3819 3820 3821 </td> 3822 3823 3824 3825 3826 3827 <td style="vertical-align: top;"> 3828 3829 3830 3831 3832 3833 <p>Coordinate information concerning 716 4.5.6</a>.</p> </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">31<br> 717 </td> <td style="vertical-align: top;"><a name="PLOT3D_COOR"></a>PLOT3D_COOR </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Binary<br> </td> <td style="vertical-align: top;"> <p>Coordinate 718 information concerning 3834 719 the three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>) 3835 needed by the visualization software AVS. </p> 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 <p>The file PLOT3D_COOR should be saved by the user into the same 3847 permanent directory as the file PLOT3D_DATA. </p> 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 <p>For parallel runs PLOT3D_COOR is written by PE0 only.</p> 3859 3860 3861 3862 3863 3864 </td> 3865 3866 3867 3868 3869 3870 </tr> 3871 3872 3873 3874 3875 3876 <tr> 3877 3878 3879 3880 3881 3882 <td style="vertical-align: top; text-align: center;">32<br> 3883 3884 3885 3886 3887 3888 </td> 3889 3890 3891 3892 3893 3894 <td style="vertical-align: top;"><a name="PLOT3D_FLD"></a>PLOT3D_FLD 3895 </td> 3896 3897 3898 3899 3900 3901 <td style="vertical-align: top;">O<br> 3902 3903 3904 3905 3906 3907 </td> 3908 3909 3910 3911 3912 3913 <td style="vertical-align: top;">Ascii/ <br> 3914 3915 3916 3917 3918 3919 AVS-Fld </td> 3920 3921 3922 3923 3924 3925 <td style="vertical-align: top;"> 3926 3927 3928 3929 3930 3931 <p>AVS-fld-file describing the three-dimensional 720 needed by the visualization software AVS. </p> <p>The 721 file PLOT3D_COOR should be saved by the user into the same 722 permanent directory as the file PLOT3D_DATA. </p> <p>For 723 parallel runs PLOT3D_COOR is written by PE0 only.</p> </td> 724 </tr> <tr> <td style="vertical-align: top; text-align: center;">32<br> 725 </td> <td style="vertical-align: top;"><a name="PLOT3D_FLD"></a>PLOT3D_FLD </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ <br> 726 AVS-Fld </td> <td style="vertical-align: top;"> <p>AVS-fld-file 727 describing the three-dimensional 3932 728 array data, saved by the model into the local file <a href="#PLOT3D_DATA">PLOT3D_DATA</a>, 3933 needed by the visualization software AVS. </p> 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 <p>This file describes the structure of the file PLOT3D_DATA 729 needed by the visualization software AVS. </p> <p>This 730 file describes the structure of the file PLOT3D_DATA 3945 731 (e.g. number of arrays, array dimensions, data type etc.). It uses the 3946 732 so-called AVS-Fld-format. It also contains the name of the file 3947 733 (inclusive cycle number, but without path) under which the local file 3948 734 PLOT3D_DATA is saved (this is the file name given in the file 3949 connection statement of the MRUN – configuration) in the permanent 735 connection statement of the MRUN – configuration) in the 736 permanent 3950 737 directory of the user (possibly on remote computers). Under this name 3951 738 AVS expects the data which are to be visualized. If there is no file 3952 739 connection statement for PLOT3D_DATA indicated in the configuration 3953 file, that file (filename) is registered “unknown” in the file 740 file, that file (filename) is registered “unknown” 741 in the file 3954 742 PLOT3D_FLD and the 3955 743 actual name must be inserted later by hand. The file PLOT3D_FLD should … … 3957 745 that AVS can find the file PLOT3D_DATA without any problems. If the two 3958 746 files lie in different directories, then the path name of the file 3959 PLOT3D_DATA must be added. </p> 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 3970 <p>AVS-fld-files are expected by AVS to have the 747 PLOT3D_DATA must be added. </p> <p>AVS-fld-files 748 are expected by AVS to have the 3971 749 suffix "<span style="font-family: monospace;">.fld</span>"<font face="Cumberland, monospace">.</font> 3972 Cycle numbers must not be attached behind this "<span style="font-family: monospace;">.fld</span>" suffix. This suffix is 750 Cycle numbers must not be attached behind this "<span style="font-family: monospace;">.fld</span>" suffix. 751 This suffix is 3973 752 attached to the permanent file names (still after 3974 753 possible cycle numbers) by <span style="font-weight: bold;">mrun</span> 3975 754 if "<span style="font-family: monospace;">fld</span>" 3976 755 is indicated in the <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Spalte6">column 3977 6 </a>of the file connection statement. </p> 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 <p>Likewise, AVS expects information about the coordinate 756 6 </a>of the file connection statement. </p> <p>Likewise, 757 AVS expects information about the coordinate 3989 758 system underlying the arrays on this file. This information is output 3990 759 by the model … … 3992 761 whose content the user has to append to the file PLOT3D_FLD after the 3993 762 end of the model run (e.g. with an appropriate OUTPUT-command in the 3994 MRUN-configuration file: “cat PLOT3D_FLD_COOR >> 3995 PLOT3D_FLD”). </p> 3996 3997 3998 3999 4000 4001 4002 4003 4004 4005 4006 <p>For parallel runs, PLOT3D_FLD is produced by PE0 only.</p> 4007 4008 4009 4010 4011 4012 </td> 4013 4014 4015 4016 4017 4018 </tr> 4019 4020 4021 4022 4023 4024 <tr> 4025 4026 4027 4028 4029 4030 <td style="vertical-align: top; text-align: center;">33 </td> 4031 4032 4033 4034 4035 4036 <td style="vertical-align: top;"><a name="PLOT3D_FLD_COOR"></a>PLOT3D_FLD_COOR 4037 </td> 4038 4039 4040 4041 4042 4043 <td style="vertical-align: top;">O<br> 4044 4045 4046 4047 4048 4049 </td> 4050 4051 4052 4053 4054 4055 <td style="vertical-align: top;">Ascii/ <br> 4056 4057 4058 4059 4060 4061 AVS-Fld </td> 4062 4063 4064 4065 4066 4067 <td style="vertical-align: top;"> 4068 4069 4070 4071 4072 4073 <p>File for the description of the coordinate information output 763 MRUN-configuration file: “cat PLOT3D_FLD_COOR 764 >> 765 PLOT3D_FLD”). </p> <p>For parallel 766 runs, PLOT3D_FLD is produced by PE0 only.</p> </td> </tr> 767 <tr> <td style="vertical-align: top; text-align: center;">33 768 </td> <td style="vertical-align: top;"><a name="PLOT3D_FLD_COOR"></a>PLOT3D_FLD_COOR </td> 769 <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ <br> 770 AVS-Fld </td> <td style="vertical-align: top;"> <p>File 771 for the description of the coordinate information output 4074 772 by the model into the local file <a href="#PLOT3D_COOR">PLOT3D_COOR</a>, 4075 773 which is needed for the visualization of three-dimensional array data 4076 by visualization-software AVS. </p> 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 <p>This file describes the structure of the file PLOT3D_COOR 774 by visualization-software AVS. </p> <p>This 775 file describes the structure of the file PLOT3D_COOR 4088 776 (e.g. grid spacing, data type etc.) using the so-called AVS-Fld-format. 4089 777 It also contains the name of the file (inclusive cycle number, but … … 4097 785 registered as "unknown" in the file 4098 786 PLOT3D_FLD_COOR and the actual name 4099 must be inserted later by hand. </p> 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 <p>AVS expects the information contained in the file 787 must be inserted later by hand. </p> <p>AVS 788 expects the information contained in the file 4111 789 PLOT3D_FLD_COOR, as well as the remaining information about the 4112 790 three-dimensional arrays output by the model (see <a href="#PLOT3D_FLD">PLOT3D_FLD</a>) … … 4114 792 PLOT3D_FLD_COOR after the end of a run are to the 4115 793 file PLOT3D_FLD (e.g. with an appropriate OUTPUT-command in the 4116 MRUN-configuration file: “cat PLOT3D_FLD_COOR >> 4117 PLOT3D_FLD”). </p> 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 <p>For parallel runs, PLOT3D_FLD_COOR is written by PE0 only.</p> 4129 4130 4131 4132 4133 4134 </td> 4135 4136 4137 4138 4139 4140 </tr> 4141 4142 4143 4144 4145 4146 <tr> 4147 4148 4149 4150 4151 4152 <td style="vertical-align: top; text-align: center;"> 4153 4154 4155 4156 4157 4158 <p align="center">40 </p> 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 <p align="center">and/or <br> 4170 4171 4172 4173 4174 794 MRUN-configuration file: “cat PLOT3D_FLD_COOR 795 >> 796 PLOT3D_FLD”). </p> <p>For parallel 797 runs, PLOT3D_FLD_COOR is written by PE0 only.</p> </td> </tr> 798 <tr> <td style="vertical-align: top; text-align: center;"> 799 <p align="center">40 </p> <p align="center">and/or <br> 800 possibly </p> <p align="center">40-49</p> 801 </td> <td style="vertical-align: top;"> <p><a name="PLOT1D_DATA"></a>PLOT1D_DATA </p> 802 <p>and/or <br> 4175 803 possibly </p> 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 <p align="center">40-49</p>4187 4188 4189 4190 4191 4192 </td>4193 4194 4195 4196 4197 4198 <td style="vertical-align: top;">4199 4200 4201 4202 4203 4204 <p><a name="PLOT1D_DATA"></a>PLOT1D_DATA </p>4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 <p>and/or <br>4216 4217 4218 4219 4220 4221 possibly </p>4222 4223 4224 4225 4226 4227 804 PLOT1D_DATA_0 <br> 4228 4229 4230 4231 4232 4233 PLOT1D_DATA_1 </td> 4234 4235 4236 4237 4238 4239 <td style="vertical-align: top;">O </td> 4240 4241 4242 4243 4244 4245 <td style="vertical-align: top;">Ascii </td> 4246 4247 4248 4249 4250 4251 <td style="vertical-align: top;"> 4252 4253 4254 4255 4256 4257 <p>This file contains data (possibly horizontally and/or 805 PLOT1D_DATA_1 </td> <td style="vertical-align: top;">O </td> <td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;"> <p>This file contains 806 data (possibly horizontally and/or 4258 807 temporally averaged) of the vertical profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>) 4259 written by the model in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>. It is created only if <a href="chapter_4.2.html#data_output_format">data_output_format</a> = <span style="font-style: italic;">'profil'</span> is assigned. This file's format is suitable to be read by the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>. 808 written by the model in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>. 809 It is created only if <a href="chapter_4.2.html#data_output_format">data_output_format</a> 810 = <span style="font-style: italic;">'profil'</span> 811 is assigned. This file's format is suitable to be read by the plot 812 software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>. 4260 813 Each data point of the profiles is output in one single line (1st 4261 814 column: height in m, 2nd column: value of the respective quantity). … … 4265 818 (<b>data_output_pr</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>,… 4266 819 means that the file starts with the data of the u-component profile, 4267 followed by the v-component profile, etc.). </p> 4268 <p><br> 820 followed by the v-component profile, etc.). </p> <p><br> 4269 821 The data can only be visualized with <span style="font-weight: bold;">profil</span> 4270 822 using NAMELIST-parameter sets, which are saved by the 4271 model into the local file <a href="#PLOT1D_PAR">PLOT1D_PAR</a>. </p> 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 <p>The profile data written to the file are described with the 823 model into the local file <a href="#PLOT1D_PAR">PLOT1D_PAR</a>. 824 </p> <p>The profile data written to the file are described 825 with the 4283 826 run parameter <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>. 4284 827 Plots produced with these data using the parameter file PLOT1D_PAR do … … 4304 847 to the file name (e.g. PLOT1D_DATA_1). The name of the file with the 4305 848 data of the total 4306 domain in this case reads PLOT1D_DATA_0. </p> 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 <p>For presentation in the same plot, profile data of the restart 849 domain in this case reads PLOT1D_DATA_0. </p> <p>For 850 presentation in the same plot, profile data of the restart 4318 851 runs can be attached to existing data of preceding runs of a job chain. 4319 852 One can do this with the file attribute <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#tra">tra</a> 4320 853 in the file connection statement. The model produces a parameter file 4321 854 (PLOT1D_PAR) for these combined data, if the run parameter is set <a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a> 4322 = <i>.T</i>. If this is omitted, then the parameter file gives 855 = <i>.T</i>. If this is omitted, then the parameter file 856 gives 4323 857 wrong plots (i.e. <span style="font-family: monospace;">use_prior_plot1d_parameters 4324 858 = .T.</span> and "<span style="font-family: monospace;">tra</span>" 4325 must be specified together)! </p> 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 <p>Further information about output of 859 must be specified together)! </p> <p>Further 860 information about output of 4337 861 vertical profile data is given in the description of the run parameter <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>.</p> 4338 4339 4340 4341 4342 4343 </td> 4344 4345 4346 4347 4348 4349 </tr> 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 <tr> 4362 4363 4364 4365 4366 4367 <td style="vertical-align: top; text-align: center;">80 </td> 4368 4369 4370 4371 4372 4373 <td style="vertical-align: top;"><a name="PARTICLE_INFOS"></a>PARTICLE_INFOS/ 4374 </td> 4375 4376 4377 4378 4379 4380 <td style="vertical-align: top;">O </td> 4381 4382 4383 4384 4385 4386 <td style="vertical-align: top;">Ascii </td> 4387 4388 4389 4390 4391 4392 <td style="vertical-align: top;">This 862 </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">80 </td> 863 <td style="vertical-align: top;"><a name="PARTICLE_INFOS"></a>PARTICLE_INFOS/ </td> 864 <td style="vertical-align: top;">O </td> <td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;">This 4393 865 file is created in case of particle transport (see the <a href="chapter_4.2.html#particles_package">particles 4394 package</a>). It contains statistical informations about the number of 866 package</a>). It contains statistical informations about the 867 number of 4395 868 particles used and about the number of particles exchanged between each 4396 869 single PE. These informations are output after every timestep if 4397 870 switched on by parameter <a href="chapter_4.2.html#write_particle_statistics">write_particle_statistics</a>. 4398 </td> 4399 4400 4401 4402 4403 4404 </tr> 4405 4406 4407 4408 4409 4410 <tr> 4411 4412 4413 4414 4415 4416 <td style="vertical-align: top; text-align: center;">81 </td> 4417 4418 4419 4420 4421 4422 <td style="vertical-align: top;"><a name="PLOTSP_X_PAR"></a>PLOTSP_X_PAR 4423 </td> 4424 4425 4426 4427 4428 4429 <td style="vertical-align: top;">O </td> 4430 4431 4432 4433 4434 4435 <td style="vertical-align: top;">Ascii/<br> 4436 4437 4438 4439 4440 4441 NAMELIST </td> 4442 4443 4444 4445 4446 4447 <td style="vertical-align: top;">This 871 </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">81 </td> 872 <td style="vertical-align: top;"><a name="PLOTSP_X_PAR"></a>PLOTSP_X_PAR 873 </td> <td style="vertical-align: top;">O </td> 874 <td style="vertical-align: top;">Ascii/<br> 875 NAMELIST </td> <td style="vertical-align: top;">This 4448 876 file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra 4449 package</a>). It contains the NAMELIST parameter set, with which the 877 package</a>). It contains the NAMELIST parameter set, with which 878 the 4450 879 layout of a plot 4451 880 of the data in the local file <a href="#PLOTSP_X_DATA">PLOTSP_X_DATA</a> 4452 881 can be steered, if these data are plotted with the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.<br> 4453 4454 4455 4456 4457 4458 4459 4460 4461 4462 4463 <p>It contains the so-called RAHMEN (frame)- and 4464 CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&RAHMEN and/or &CROSS</span>) 882 <p>It contains the so-called RAHMEN (frame)- and 883 CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&RAHMEN and/or 884 &CROSS</span>) 4465 885 needed by <span style="font-weight: bold;">profil</span>. 4466 886 The user can edit these parameter sets (and thus all details of the 4467 plot layout) after the run.<br> 4468 4469 4470 4471 4472 4473 </p> 4474 4475 4476 4477 4478 4479 4480 4481 4482 4483 4484 <p>By default, for one quantity, all spectra at different heights 887 plot layout) after the run.<br> </p> <p>By default, 888 for one quantity, all spectra at different heights 4485 889 are plotted into a single panel. Different colors and line styles are 4486 890 used for each height. Panels of up to four quantities are arranged on … … 4488 892 additional page(s). If there is more than one output time (see <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>), 4489 893 additional pages will be plotted for each single output time. </p> 4490 4491 4492 4493 4494 4495 </td> 4496 4497 4498 4499 4500 4501 </tr> 4502 4503 4504 4505 4506 4507 <tr> 4508 4509 4510 4511 4512 4513 <td style="vertical-align: top; text-align: center;">82<br> 4514 4515 4516 4517 4518 4519 </td> 4520 4521 4522 4523 4524 4525 <td style="vertical-align: top;"><a name="PLOTSP_X_DATA"></a>PLOTSP_X_DATA 4526 </td> 4527 4528 4529 4530 4531 4532 <td style="vertical-align: top;">O<br> 4533 4534 4535 4536 4537 4538 </td> 4539 4540 4541 4542 4543 4544 <td style="vertical-align: top;">Ascii<br> 4545 4546 4547 4548