1 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
---|
2 | <html><head> |
---|
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 |
---|
5 | output files</font></h3> |
---|
6 | <p style="line-height: 100%;"></p><p style="line-height: 100%;"><font color="#000000">The |
---|
7 | model works |
---|
8 | with a set of files, which are all located in the temporary working |
---|
9 | directory and which are either expected at the beginning of the run |
---|
10 | (the so-called input files) or which are |
---|
11 | produced during the run and/or at the end of the simulation (output |
---|
12 | files).</font><font color="#800000"> |
---|
13 | <font color="#000000">The following table lists all |
---|
14 | default files |
---|
15 | addressed by the model. They are arranged according to the |
---|
16 | associated FORTRAN unit (unit number).</font> </font><font color="#000000">The |
---|
17 | unit 90 is used for different files, which are opened only briefly |
---|
18 | and uniquely in the model and closed directly afterwards. |
---|
19 | Unit numbers 101 - 109, 111 - 113, and 116 refer to data files |
---|
20 | which have NetCDF format. |
---|
21 | These are not opened by a FORTRAN-OPEN-statement but by a corresponding |
---|
22 | NetCDF call (NF90_CREATE or NF90_OPEN). These files are only created on |
---|
23 | machines where a NetCDF library is available.<br> |
---|
24 | </font></p><p style="line-height: 100%;"><font color="#000000">The file |
---|
25 | names described in the list correspond to the names indicated in the |
---|
26 | respective OPEN instruction, i.e. the files are expected and saved |
---|
27 | under these names in the temporary working directory of the model. By |
---|
28 | default, file names are always written in capital letters. The |
---|
29 | third column indicates whether it is an input or output file (I |
---|
30 | and/or O). The NetCDF files can be both input and output files (I/O). |
---|
31 | If restart jobs shall append data to an existing NetCDF file (created |
---|
32 | by a previous job of the job chain), the respective file has to be |
---|
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 |
---|
38 | computers many of the files are read and/or written by the central |
---|
39 | processing element 0 (PE0) only. These files have processor-independent |
---|
40 | content (and therefore they can be read or written by other |
---|
41 | PEs just as well). However, certain files have processor-dependent |
---|
42 | content. For the binary output of data for restart runs (local file |
---|
43 | <a href="#BINOUT">BINOUT</a>), |
---|
44 | for example, <font color="#000000">each PE outputs only |
---|
45 | the data of |
---|
46 | its subdomain. So each processing element writes |
---|
47 | into its own file with its own file name. These files lie in a |
---|
48 | subdirectory of the temporary working directory. Their names are build |
---|
49 | off from the underline ("_ ") and the four digit |
---|
50 | processor ID. The data written for restart runs would be e.g. on the |
---|
51 | files BINOUT/_0000 (PE0), BINOUT/_0001 (PE1), BINOUT/_0002 (PE2) etc. |
---|
52 | Such files, which have processor-dependent content on parallel |
---|
53 | computers, are marked in the following list by the fact, that to the |
---|
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 |
---|
58 | files with processor-dependent content are supposed to be copied as |
---|
59 | input files into the temporary working directory of the model, you have |
---|
60 | to indicate a special file attribute in the appropriate file |
---|
61 | connection statement </font>(see <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#arpe">arpe</a>, |
---|
62 | <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#flpe">flpe</a> |
---|
63 | <font color="#000000">in the <b>mrun </b>description).</font><font color="#800000"> |
---|
64 | </font><font color="#000000">Then the permanent file |
---|
65 | name will be |
---|
66 | interpreted as a directory name, in which the input files are |
---|
67 | expected and/or to which output files are written. The file names in |
---|
68 | these directories are always named _0000, _0001, _0002 etc. </font> |
---|
69 | </font></p><font color="#000000"><font color="#000000">For internal use, |
---|
70 | the model may open a set of further files, which are not |
---|
71 | defined by the user but contain no usable information and |
---|
72 | therefore are not included in this list. <br> |
---|
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 |
---|
85 | is needed by the model in each case. Its content and structure is |
---|
86 | described in detail in</font> <a href="chapter_4.0.html">chapter |
---|
87 | 4.0</a>. <a href="chapter_4.4.html">Chapter |
---|
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 |
---|
95 | of a restart run (see <a href="chapter_3.3.html">chapter |
---|
96 | 3.3</a>). The appropriate file must have been written by the |
---|
97 | preceding |
---|
98 | job of the job chain (see <a href="#BINOUT">BINOUT</a>). |
---|
99 | This file contains the initial parameters (see <a href="chapter_4.1.html">chapter |
---|
100 | 4.1</a>) of the job chain, arrays of the prognostic and |
---|
101 | diagnostic |
---|
102 | variables as well as those parameters and variables for plots of |
---|
103 | horizontally averaged vertical profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>), |
---|
104 | which have been determined by the job chain so far. Concerning runs on |
---|
105 | several processors it has to be noted that each processing element |
---|
106 | reads its own file and the file content is processor-dependent. The |
---|
107 | number of processors which can be used must not be changed during a job |
---|
108 | chain and/or if a job chain is continued. </p> <p>Knowledge |
---|
109 | of the file structure is usually not necessary, |
---|
110 | because the file is produced and also read again by the model, but it |
---|
111 | can be useful for error determination in case of read errors . |
---|
112 | Therefore the file structure is described in the following. </p> |
---|
113 | <p>The first record of this file contains a version number (ten |
---|
114 | character string) of the subroutine, which, which output the data that |
---|
115 | follows (write_var_list.f90). This number has to |
---|
116 | agree with the version number subroutine which is reading the file |
---|
117 | (read_var_list.f90) in case of a restart run. Otherwise the model run |
---|
118 | is aborted. Version numbers are changed whenever new code revisions |
---|
119 | require a change of the file format. </p> <p>Starting |
---|
120 | from the second record, all initial parameters follow |
---|
121 | (exception: <a href="chapter_4.1.html#initializing_actions">initializing_actions</a>), |
---|
122 | whereby each parameter fills two records. In the first record the name |
---|
123 | of the parameter is saved as a character string (30 characters long, |
---|
124 | short names are filled by trailing blanks, longer names are cut off at |
---|
125 | the end), in the second record the value (or the values) of the |
---|
126 | parameter follow. The sequence of parameters on the file may be |
---|
127 | arbitrary, however the first and second variable must be <a href="chapter_4.1.html#nz">nz</a> |
---|
128 | and <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>. |
---|
129 | If a variable with unknown name is found the model run is |
---|
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 |
---|
136 | variables follow. This part of the file also begins with a record |
---|
137 | consisting of a character string of length 10, which contains the |
---|
138 | version number of the subroutine that wrote the arrays that follow |
---|
139 | (write_3d_binary.f90). It must agree with the number of the reading |
---|
140 | subroutine (read_3d_binary.f90). </p> <p>The |
---|
141 | following record contains the number of processors which |
---|
142 | were used in the model run producing this file, the processor ID of the |
---|
143 | special processor, which creates the file, as well as the lower and |
---|
144 | upper array indices of the subdomain belonging to this processing |
---|
145 | element. If no complete agreement with the values of the current model |
---|
146 | run exists, then this is aborted. This examination must be made in |
---|
147 | particular on parallel computers, because the jobs of a job chain |
---|
148 | always have to use the same number of processors and the same virtual |
---|
149 | processor grid. </p> <p>After these tests the |
---|
150 | individual arrays as well as parameters |
---|
151 | and variables for plots of horizontally averaged vertical profiles |
---|
152 | follow. Like the initialization parameters, they consist of two |
---|
153 | records. In the first record, the name of the array or the variable |
---|
154 | (character string, consisting of 20 characters, filled with trailing |
---|
155 | blanks) is located, in the second one its values follow. The sequence |
---|
156 | of the individual variables may be arbitrary again. The parameters for |
---|
157 | the plot and the respective variables are only read in if for the run |
---|
158 | parameter <a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a> |
---|
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 |
---|
164 | ***</i>"(filled up with trailing blanks up to a length of 20 |
---|
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 |
---|
172 | run and possibly needed by restart runs (see <a href="chapter_3.3.html">chapter |
---|
173 | 3.3</a>) for the initialization. This output file is then read in |
---|
174 | as |
---|
175 | file <a href="#BININ">BININ</a>. |
---|
176 | It contains the initial parameters (see <a href="chapter_4.1.html">chapter |
---|
177 | 4.1</a>) of the model run, arrays of the prognostic and |
---|
178 | diagnostic |
---|
179 | variables as well as those parameters determined so far during a job |
---|
180 | chain and variables for plots of horizontally averaged vertical |
---|
181 | profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>). |
---|
182 | With runs on several processors it has to be noted that each processing |
---|
183 | element writes its own file and the file content is |
---|
184 | processor-dependent. A specification of the file format can be found in |
---|
185 | 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 |
---|
191 | environment |
---|
192 | variable <span style="font-size: 10pt; font-family: monospace;">write_binary</span> |
---|
193 | (see <a href="chapter_3.3.html">chapter |
---|
194 | 3.3</a>). </p> <p>With large grid point |
---|
195 | numbers the file BINOUT (or the |
---|
196 | files residing in directory BINOUT/) will be very large and should |
---|
197 | be stored (if available) on the archive system of the remote computer.</p> |
---|
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 |
---|
201 | the model. At certain temporal intervals, which are described by the |
---|
202 | run |
---|
203 | parameter <a href="chapter_4.1.html#dt_run_control">dt_run_control</a>, |
---|
204 | a line with the values of certain control parameters is written into |
---|
205 | this |
---|
206 | file. Additionally, such a control line is always written, whenever the |
---|
207 | time step of the model changes. All data and quantities always refer to |
---|
208 | the entire model domain. </p> <p>If the |
---|
209 | 1D-model is switched on for the initialization of the |
---|
210 | 3D-models, then control lines are likewise written into this file at |
---|
211 | certain temporal intervals (see <a href="chapter_4.1.html#dt_run_control_1d">dt_run_control_1d</a>). |
---|
212 | </p> <p>By default, the file RUN_CONTROL only lists |
---|
213 | information |
---|
214 | about the selected model parameters at the beginning of the |
---|
215 | initial run. These informations are written at the beginnning of a run. |
---|
216 | They correspond to those of the file <a href="#HEADER">HEADER</a> |
---|
217 | (however without data concerning the consumed CPU time, because these |
---|
218 | are |
---|
219 | only known at the end of a run). With the run parameter <a href="chapter_4.2.html#force_print_header">force_print_header</a> |
---|
220 | it can be achieved that this information is also written at the |
---|
221 | beginning of the file RUN_CONTROL at restart runs. </p> |
---|
222 | <p>The individual columns of the 1D - time step control output |
---|
223 | have the following meaning (listed by the respective heading of the |
---|
224 | appropriate |
---|
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 |
---|
232 | velocity |
---|
233 | (u-component) (in m/s)</td> </tr> <tr> <td style="vertical-align: top;">VMAX</td> <td style="vertical-align: top;">Maximum absolute wind |
---|
234 | velocity |
---|
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 |
---|
238 | (to the x-axis) at the top of the |
---|
239 | Prandtl layer (k=1) (<font color="#000000">in </font>degrees)</td> |
---|
240 | </tr> <tr> <td style="vertical-align: middle;">ENERG.</td> |
---|
241 | <td style="vertical-align: top;">Kinetic energy of the |
---|
242 | 1D-model (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>), |
---|
243 | averaged over all grid points</td> </tr> </tbody> </table> |
---|
244 | <p> |
---|
245 | The individual columns of the 3D - time step control output |
---|
246 | have the following meaning (listed by the respective heading of the |
---|
247 | appropriate |
---|
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 |
---|
251 | in the job chain. The initial |
---|
252 | run has the number 0, restart runs accordingly have larger numbers.</td> |
---|
253 | </tr> <tr> <td style="vertical-align: top;">ITER.</td> |
---|
254 | <td style="vertical-align: top;">Number of time steps |
---|
255 | accomplished since starting time t=0 of |
---|
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: |
---|
258 | seconds) since starting time t=0 of 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 |
---|
260 | following character indicates whether the |
---|
261 | time |
---|
262 | step is limited by the advection criterion (A) or the diffusion |
---|
263 | criterion (D). After changes of the time step a further character |
---|
264 | follows, |
---|
265 | which indicates with which time step procedure the changed time step |
---|
266 | was accomplished (<span style="font-family: monospace;">L:</span> |
---|
267 | Leapfrog, <span style="font-family: monospace;">E:</span> |
---|
268 | Euler). This |
---|
269 | does |
---|
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 |
---|
275 | the |
---|
276 | appropriate output time a random disturbance was added to the |
---|
277 | horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>), |
---|
278 | the character D will appear directly after the velocity value.</td> |
---|
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 |
---|
283 | the |
---|
284 | appropriate output time a random disturbance was added to the |
---|
285 | horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>), |
---|
286 | the character D will appear directly after the velocity value.</td> |
---|
287 | </tr> <tr> <td style="vertical-align: top;">WMAX</td> |
---|
288 | <td style="vertical-align: top;">Maximum absolute wind |
---|
289 | velocity (w-component) (<font color="#000000">in </font>m/s).</td> |
---|
290 | </tr> <tr> <td style="vertical-align: top;">U |
---|
291 | *</td> <td style="vertical-align: top;">Horizontal |
---|
292 | average of the |
---|
293 | friction velocity (<font color="#000000">in </font>m/s).</td> |
---|
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 |
---|
303 | of the Prandtl - layer (<font color="#000000">in </font>K).</td> |
---|
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 |
---|
310 | energy of the flow field (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>), |
---|
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 |
---|
319 | of the velocity field (sum of |
---|
320 | the absolute values) (</font><font color="#000000">in |
---|
321 | </font><font color="#000000">1/s) before call of the |
---|
322 | pressure solver, |
---|
323 | normalized with the total number of grid points.</font></td> |
---|
324 | </tr> <tr> <td style="vertical-align: top;">DIVNEW</td> |
---|
325 | <td style="vertical-align: top;"><font color="#000000">Divergence |
---|
326 | of the velocity field (sum of |
---|
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 |
---|
332 | with the maximum absolute |
---|
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 |
---|
336 | with the maximum absolute |
---|
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 |
---|
340 | with the maximum absolute |
---|
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 |
---|
344 | coordinate system has been moved in |
---|
345 | x-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td> |
---|
346 | </tr> <tr> <td style="vertical-align: top;">ADVECY</td> |
---|
347 | <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the |
---|
348 | coordinate system has been moved in |
---|
349 | y-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td> |
---|
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 |
---|
353 | (and possibly temporally) |
---|
354 | averaged vertical profiles of some model variables. The quantities |
---|
355 | saved are set model-internally and can not be determined by the user. |
---|
356 | At each output time (see <a href="chapter_4.2.html#dt_dopr_listing">dt_dopr_listing</a>) |
---|
357 | two tables are written to the file consecutively. The first contains |
---|
358 | variables which are defined on the scalar / u-v-grid-levels, the |
---|
359 | second table contains variables which are defined on the w-grid-levels. |
---|
360 | If subdomains were defined with the initialization parameter <a href="chapter_4.1.html#statistic_regions">statistic_regions </a>for |
---|
361 | additional statistic evaluation, then the tables |
---|
362 | described above are written for each individual subdomain. The name of |
---|
363 | the respective subdomain (see <a href="chapter_4.3.html#region">region</a>) |
---|
364 | appears in the header of the respective table. <br> |
---|
365 | In each case the tables consist of a header, followed by the |
---|
366 | profiles arranged next to each other in columns. The header contains |
---|
367 | some basic information of the respective run (model version, run |
---|
368 | identifier consisting of |
---|
369 | basic file name and number of the job in the job chain, executing |
---|
370 | computer, date, time of the beginning of the run, name of the |
---|
371 | subdomain, output time, kind of averaging). On the u-v-level the |
---|
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 |
---|
377 | of the grid point |
---|
378 | level (<font color="#000000">in </font>m).</td> |
---|
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 |
---|
381 | of the wind |
---|
382 | velocity (<font color="#000000">in </font>m/s).</td> |
---|
383 | </tr> <tr> <td style="text-align: left; vertical-align: middle;">du<br> |
---|
384 | </td> <td style="text-align: left; vertical-align: middle;">Deviation |
---|
385 | of the |
---|
386 | u-component from the initial profile at the |
---|
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 |
---|
390 | of the wind |
---|
391 | velocity (<font color="#000000">in </font>m/s).</td> |
---|
392 | </tr> <tr> <td style="text-align: left; vertical-align: middle;">dv<br> |
---|
393 | </td> <td style="text-align: left; vertical-align: middle;">Deviation |
---|
394 | of the |
---|
395 | v-component from the initial profile at the |
---|
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 |
---|
399 | temperature (<font color="#000000">in </font>K).</td> |
---|
400 | </tr> <tr> <td style="text-align: left; vertical-align: middle;">dpt<br> |
---|
401 | </td> <td style="text-align: left; vertical-align: middle;">Deviation |
---|
402 | of potential |
---|
403 | temperature from the initial profile at |
---|
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 |
---|
407 | kinetic energy |
---|
408 | (subgrid-scale) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td> |
---|
409 | </tr> <tr> <td style="text-align: left; vertical-align: middle;">Km<br> |
---|
410 | </td> <td style="text-align: left; vertical-align: middle;">Turbulent |
---|
411 | diffusion |
---|
412 | coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td> |
---|
413 | </tr> <tr> <td style="text-align: left; vertical-align: middle;">Kh<br> |
---|
414 | </td> <td style="text-align: left; vertical-align: middle;">Turbulent |
---|
415 | diffusion |
---|
416 | coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td> |
---|
417 | </tr> <tr> <td style="text-align: left; vertical-align: middle;">l<br> |
---|
418 | </td> <td style="text-align: left; vertical-align: middle;">Mixing |
---|
419 | length (<font color="#000000">in </font>m).</td> |
---|
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 |
---|
429 | point |
---|
430 | level (<font color="#000000">in </font>m).</td> |
---|
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 ( |
---|
435 | subgrid-scale + resolved) |
---|
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 |
---|
442 | total |
---|
443 | vertical momentum flux ( |
---|
444 | subgrid-scale + resolved) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td> |
---|
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 |
---|
451 | total |
---|
452 | vertical momentum flux ( |
---|
453 | subgrid-scale + resolved) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td> |
---|
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 |
---|
457 | profiles calculated by the |
---|
458 | 1D-model within initial runs. The quantities saved are set |
---|
459 | model-internally and cannot be determined by the user. At the |
---|
460 | respective output times (see <a href="chapter_4.1.html#dt_pr_1d">dt_pr_1d</a>) |
---|
461 | a table with the following information is written to the file: The |
---|
462 | table header contains some basic information of the respective run |
---|
463 | (model version, run identifier consisting of basic file name and number |
---|
464 | of the job in the |
---|
465 | job chain (this number should always be 00, because the 1D-model is |
---|
466 | only switched on at initial runs), executing computer, date, |
---|
467 | time of the beginning of the run, output time). Afterwards the |
---|
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 |
---|
473 | of the grid point |
---|
474 | level (<font color="#000000">in </font>m).</td> |
---|
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 |
---|
477 | of the wind |
---|
478 | velocity (<font color="#000000">in </font>m/s).</td> |
---|
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 |
---|
481 | of the wind |
---|
482 | velocity (<font color="#000000">in </font>m/s).</td> |
---|
483 | </tr> <tr> <td style="text-align: left; vertical-align: middle;">pt<br> |
---|
484 | </td> <td style="text-align: left; vertical-align: middle;">Potential |
---|
485 | temperature (<font color="#000000">in </font>K).</td> |
---|
486 | </tr> <tr> <td style="text-align: left; vertical-align: middle;">e<br> |
---|
487 | </td> <td style="text-align: left; vertical-align: middle;">Turbulent |
---|
488 | kinetic energy (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td> |
---|
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 |
---|
493 | diffusion |
---|
494 | coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td> |
---|
495 | </tr> <tr> <td style="text-align: left; vertical-align: middle;">Kh<br> |
---|
496 | </td> <td style="text-align: left; vertical-align: middle;">Turbulent |
---|
497 | diffusion |
---|
498 | coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td> |
---|
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 |
---|
506 | accomplished through the subroutine <span style="font-family: monospace;">cpu_log.f90.</span><span style="font-size: 10pt;"></span> The file |
---|
507 | CPU_MEASURES contains a header with some basic information of the |
---|
508 | respective run |
---|
509 | (model version, run identifier consisting of basic file name and |
---|
510 | number of the job in the job chain, executing computer, date, time of |
---|
511 | the beginning of the run) and afterwards two tables with data of CPU |
---|
512 | times which have been consumed by certain model parts. The model parts |
---|
513 | analyzed in the first table do not overlap and the CPU times needed for |
---|
514 | them therefore approximately add up to the “total” |
---|
515 | value given in the |
---|
516 | first line of this table. In the second table (heading: special |
---|
517 | measures) overlaps (in particular with the parts described in the first |
---|
518 | table) are possible. <br> |
---|
519 | For each model part it is indicated in the following columns how much |
---|
520 | CPU time was needed (absolutely and relative), and how often it was |
---|
521 | called. With runs on several processors the average values of |
---|
522 | all |
---|
523 | processors are indicated. In the case of parallel runs information for |
---|
524 | those processors with the largest and smallest CPU time follow as |
---|
525 | well as the standard deviation of all PEs from the average value. With |
---|
526 | good |
---|
527 | parallelization the CPU times on the individual processors should |
---|
528 | differ only little from each other and the standard deviation should be |
---|
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 |
---|
537 | parameters |
---|
538 | (numerical procedures, computing grid and model dimensions, boundary |
---|
539 | conditions, physical dimension, turbulence quantities, actions during |
---|
540 | the simulation, 1D-model-parameters) as well as data concerning the |
---|
541 | selected plot and list outputs. The headlines of the file list the |
---|
542 | program version used, date and time of the beginning of the run, the |
---|
543 | name of the executing computer, the run identifier (corresponds to the |
---|
544 | selected base file name) and the number of the run (number of the |
---|
545 | restart run). With parallel runs the number of processors as well as |
---|
546 | the assigned virtual processor net also appear. After these headlines |
---|
547 | run time and time step information appear (point of starting time, |
---|
548 | related to t=0 of the initial run, end-time, time actually reached, CPU |
---|
549 | time, etc.). If a model run is incorrectly terminated (e.g. |
---|
550 | run time error or excess of the permitted CPU time), information over |
---|
551 | the time reached and the necessary CPU time is missing (to understand: |
---|
552 | the file HEADER is written twice by the model; once briefly after |
---|
553 | beginning of the simulation (naturally here the information over the |
---|
554 | time reached is missing etc.) and then briefly before the normal end of |
---|
555 | the simulation. The second, now complete output overwrites the first |
---|
556 | output.). </p> <p>At the end of the file, |
---|
557 | information about the values of user |
---|
558 | parameters (see <a href="chapter_3.7.html">chapter |
---|
559 | 3.7</a> and <a href="targetliste:chapter_1.0.html#chapter%204.3">chapter |
---|
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 |
---|
563 | the file <tt><font style="font-size: 10pt;" size="2">user_interface.f90</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>” |
---|
566 | appears at the end of the file. |
---|
567 | If user parameters were indicated, the string “<tt><font style="font-size: 11pt;" size="2">user-defined |
---|
568 | variables and actions</font></tt>” |
---|
569 | is printed, followed by informations about the user-defined subdomains |
---|
570 | for which |
---|
571 | profiles and time series are output. All further information to appear |
---|
572 | here, must be provided by the user (by appropriate |
---|
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 |
---|
580 | cross sections written by the model (see <a href="chapter_4.2.html#data_output">data_output</a>) |
---|
581 | in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a> |
---|
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 |
---|
584 | the individual arrays follow). The data are visualized with the help of |
---|
585 | ISO2D using |
---|
586 | NAMELIST - parameter sets, which are directly written by the model to |
---|
587 | the |
---|
588 | local files <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a> |
---|
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>, |
---|
595 | whereby <processor-Id> is a four digit number (e.g. |
---|
596 | PLOT2D_XY_0000). These files are not suitable for ISO2D, but after the |
---|
597 | end |
---|
598 | of the model run they can be combined to one file readable by ISO2D |
---|
599 | with |
---|
600 | the help of the program <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>. |
---|
601 | This tool expects the files of the individual processing |
---|
602 | elements under the names described above and outputs the combined file |
---|
603 | under the name PLOT2D_XY. Usually it is called by an appropriate OUTPUT |
---|
604 | - command (OC:) in the MRUN-configuration file. The tool writes |
---|
605 | informative messages about the actions accomplished into the job |
---|
606 | protocol (e.g., even if no files were found). |
---|
607 | By the call of <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt> |
---|
608 | possibly existing files of the other cross sections (xz and/or yz) |
---|
609 | and three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>) |
---|
610 | are also combined. </p> <p>Further information |
---|
611 | about the output of plots of |
---|
612 | two-dimensional cross sections is found in the description of the run |
---|
613 | parameter <a href="chapter_4.2.html#data_output">data_output</a>.</p> |
---|
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 |
---|
617 | cross sections written by the model. </p> |
---|
618 | The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a> |
---|
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 |
---|
623 | cross sections written by the model. </p> |
---|
624 | The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a> |
---|
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 |
---|
631 | data in the local file <a href="#PLOT2D_XY">PLOT2D_XY</a> |
---|
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>. |
---|
633 | This file contains the so-called local parameter set (NAMELIST - group |
---|
634 | name: &LOCAL) required by ISO2D (one parameter set for each |
---|
635 | field |
---|
636 | present at the file PLOT2D_XY). After the model run these parameter |
---|
637 | sets can be edited by the user, if neccessary. </p> <p>Additionally |
---|
638 | ISO2D still needs another so-called global |
---|
639 | parameter set. This is saved by the model to the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>. |
---|
640 | Due to the fact that ISO2D expects global and local parameter sets on |
---|
641 | one and the same |
---|
642 | file, in fact the global parameter set first, the user has to append |
---|
643 | the |
---|
644 | contents of the file PLOT2D_XY_LOCAL to the file PLOT2D_XY_GLOBAL |
---|
645 | before the call of ISO2D (e.g. by an OUTPUT-command in the |
---|
646 | MRUN-configuration file: “PLOT2D_XY_LOCAL >> |
---|
647 | PLOT2D_XY_GLOBAL”). |
---|
648 | This relatively pedantic proceeding is due to the fact that the model |
---|
649 | can produce the file PLOT2D_XY_GLOBAL only at the end of the simulation |
---|
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> |
---|
651 | is known), while the local parameter sets are written continuously |
---|
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 |
---|
658 | data in the local file <a href="#PLOT2D_XZ">PLOT2D_XZ</a> |
---|
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>. |
---|
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 |
---|
667 | data in the local file <a href="#PLOT2D_YZ">PLOT2D_YZ</a> |
---|
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>. |
---|
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 |
---|
674 | (see <a href="chapter_4.2.html#data_output">data_output</a>) |
---|
675 | written by the model in a format readable for the visualization |
---|
676 | software AVS. Beyond that AVS |
---|
677 | needs coordinate information, which are output into the |
---|
678 | local file <a href="#PLOT3D_COOR">PLOT3D_COOR</a>, |
---|
679 | as well as the local files <a href="#PLOT3D_FLD">PLOT3D_FLD</a> |
---|
680 | and <a href="#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>, |
---|
681 | which describe the structure of the files PLOT3D_DATA and PLOT3D_COOR |
---|
682 | in the so-called AVS-FLD-format. Due to |
---|
683 | the fact that AVS expects these information in only one (so-called FLD |
---|
684 | -) file, the content of the file PLOT3D_FLD_COOR must be appended to |
---|
685 | the file PLOT3D_FLD by the user after the end of the model run (e.g. |
---|
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 |
---|
689 | its subdomain to a separate file with the name |
---|
690 | PLOT3D_DATA_<Processor-Id>, where |
---|
691 | <Processor-Id> is a |
---|
692 | four digit number (e.g. PLOT3D_DATA_0000). These files are not suitable |
---|
693 | for AVS, but after the end of the model run they can be combined to one |
---|
694 | file readable for AVS with the help of the program <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>. |
---|
695 | This tool expects the files of the individual processing |
---|
696 | elements under the names described above and outputs the combined file |
---|
697 | into a new file PLOT3D_DATA. Usually it is called by an appropriate |
---|
698 | OUTPUT - command in the MRUN-configuration file. The tool |
---|
699 | writes informative messages about the accomplished actions into |
---|
700 | the job protocol (e.g., even if no files were |
---|
701 | found). By the call of <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt> |
---|
702 | also possibly existing files with two-dimensional plot data (see e.g. <a href="#PLOT2D_XY">PLOT2D_XY</a>) |
---|
703 | are combined. </p> <p>With parallel runs the |
---|
704 | output of data of large volume is also |
---|
705 | possible in compressed form. For this purpose the initialization |
---|
706 | parameter <a href="chapter_4.2.html#do3d_compress">do3d_compress</a> |
---|
707 | = <i>.TRUE.</i> must be set and the desired output |
---|
708 | accuracy has to be |
---|
709 | indicated |
---|
710 | with the help of <a href="chapter_4.2.html#do3d_precision">do3d_precision</a>. |
---|
711 | In favorable cases the file size can be reduced by |
---|
712 | a factor of up to 5. For the visualization of compressed data a special |
---|
713 | AVS module (<tt><font style="font-size: 11pt;" size="2">read_compressed_field</font></tt>) |
---|
714 | and a further entry in the MRUN-configuration file are needed. More |
---|
715 | details can be found in <a href="chapter_4.5.6.html">chapter |
---|
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 |
---|
719 | the three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>) |
---|
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 |
---|
728 | array data, saved by the model into the local file <a href="#PLOT3D_DATA">PLOT3D_DATA</a>, |
---|
729 | needed by the visualization software AVS. </p> <p>This |
---|
730 | file describes the structure of the file PLOT3D_DATA |
---|
731 | (e.g. number of arrays, array dimensions, data type etc.). It uses the |
---|
732 | so-called AVS-Fld-format. It also contains the name of the file |
---|
733 | (inclusive cycle number, but without path) under which the local file |
---|
734 | PLOT3D_DATA is saved (this is the file name given in the file |
---|
735 | connection statement of the MRUN – configuration) in the |
---|
736 | permanent |
---|
737 | directory of the user (possibly on remote computers). Under this name |
---|
738 | AVS expects the data which are to be visualized. If there is no file |
---|
739 | connection statement for PLOT3D_DATA indicated in the configuration |
---|
740 | file, that file (filename) is registered “unknown” |
---|
741 | in the file |
---|
742 | PLOT3D_FLD and the |
---|
743 | actual name must be inserted later by hand. The file PLOT3D_FLD should |
---|
744 | be saved by the user in the same permanent directory as PLOT3D_DATA, so |
---|
745 | that AVS can find the file PLOT3D_DATA without any problems. If the two |
---|
746 | files lie in different directories, then the path name of the file |
---|
747 | PLOT3D_DATA must be added. </p> <p>AVS-fld-files |
---|
748 | are expected by AVS to have the |
---|
749 | suffix "<span style="font-family: monospace;">.fld</span>"<font face="Cumberland, monospace">.</font> |
---|
750 | Cycle numbers must not be attached behind this "<span style="font-family: monospace;">.fld</span>" suffix. |
---|
751 | This suffix is |
---|
752 | attached to the permanent file names (still after |
---|
753 | possible cycle numbers) by <span style="font-weight: bold;">mrun</span> |
---|
754 | if "<span style="font-family: monospace;">fld</span>" |
---|
755 | is indicated in the <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Spalte6">column |
---|
756 | 6 </a>of the file connection statement. </p> <p>Likewise, |
---|
757 | AVS expects information about the coordinate |
---|
758 | system underlying the arrays on this file. This information is output |
---|
759 | by the model |
---|
760 | into the local file <a href="#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>, |
---|
761 | whose content the user has to append to the file PLOT3D_FLD after the |
---|
762 | end of the model run (e.g. with an appropriate OUTPUT-command in the |
---|
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 |
---|
772 | by the model into the local file <a href="#PLOT3D_COOR">PLOT3D_COOR</a>, |
---|
773 | which is needed for the visualization of three-dimensional array data |
---|
774 | by visualization-software AVS. </p> <p>This |
---|
775 | file describes the structure of the file PLOT3D_COOR |
---|
776 | (e.g. grid spacing, data type etc.) using the so-called AVS-Fld-format. |
---|
777 | It also contains the name of the file (inclusive cycle number, but |
---|
778 | without path) into which the local file PLOT3D_COOR (this is the file |
---|
779 | name described in the file connection statement of the MRUN - |
---|
780 | configuration file) is output in the permanent directory of the user |
---|
781 | (possibly on remote computers). Under this name AVS expects the data |
---|
782 | which are to be visualized. If there is no file connection statement |
---|
783 | for |
---|
784 | PLOT3D_COOR indicated in the configuration file, that file is |
---|
785 | registered as "unknown" in the file |
---|
786 | PLOT3D_FLD_COOR and the actual name |
---|
787 | must be inserted later by hand. </p> <p>AVS |
---|
788 | expects the information contained in the file |
---|
789 | PLOT3D_FLD_COOR, as well as the remaining information about the |
---|
790 | three-dimensional arrays output by the model (see <a href="#PLOT3D_FLD">PLOT3D_FLD</a>) |
---|
791 | in one and the same file. This is satisfied by appending the file |
---|
792 | PLOT3D_FLD_COOR after the end of a run are to the |
---|
793 | file PLOT3D_FLD (e.g. with an appropriate OUTPUT-command in the |
---|
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> |
---|
803 | possibly </p> |
---|
804 | PLOT1D_DATA_0 <br> |
---|
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 |
---|
807 | temporally averaged) of the vertical profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</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>. |
---|
813 | Each data point of the profiles is output in one single line (1st |
---|
814 | column: height in m, 2nd column: value of the respective quantity). |
---|
815 | Within the file, data |
---|
816 | of the individual profiles are located one behind the other. The order |
---|
817 | of the data in the file follows the order used in the assignment for <b>data_output_pr</b> |
---|
818 | (<b>data_output_pr</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>,… |
---|
819 | means that the file starts with the data of the u-component profile, |
---|
820 | followed by the v-component profile, etc.). </p> <p><br> |
---|
821 | The data can only be visualized with <span style="font-weight: bold;">profil</span> |
---|
822 | using NAMELIST-parameter sets, which are saved by 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 |
---|
826 | run parameter <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>. |
---|
827 | Plots produced with these data using the parameter file PLOT1D_PAR do |
---|
828 | not have to contain all these profiles. The profiles which can be drawn |
---|
829 | in the plot are described with run parameter <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>. |
---|
830 | By subsequent editing of the file PLOT1D_PAR all profiles can be |
---|
831 | plotted (also the basic layout of the plots can be |
---|
832 | changed). For orientation, each profile existing on the file |
---|
833 | PLOT1D_DATA, starts with a comment line, which indicates the |
---|
834 | presented variable and the output time. The text of these comment |
---|
835 | lines is used as a legend in the plot. The very first line of the file |
---|
836 | is a |
---|
837 | comment line, containing information about the used model version, the |
---|
838 | run identifier (base file name + number of the respective restart |
---|
839 | run), the name of the executing computer, as well as the date and time |
---|
840 | of the beginning of the run. At the end of this comment line is the |
---|
841 | name |
---|
842 | of the subdomain, to which the profiles belong (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>). |
---|
843 | By default, the profiles present averages of the total model domain. If |
---|
844 | the model has to produce profiles for other subdomains beyond that, up |
---|
845 | to 9 further files (units No. 41-49) are created, whereby the number of |
---|
846 | the respective subdomain is attached |
---|
847 | to the file name (e.g. PLOT1D_DATA_1). The name of the file with the |
---|
848 | data of the total |
---|
849 | domain in this case reads PLOT1D_DATA_0. </p> <p>For |
---|
850 | presentation in the same plot, profile data of the restart |
---|
851 | runs can be attached to existing data of preceding runs of a job chain. |
---|
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> |
---|
853 | in the file connection statement. The model produces a parameter file |
---|
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> |
---|
855 | = <i>.T</i>. If this is omitted, then the parameter file |
---|
856 | gives |
---|
857 | wrong plots (i.e. <span style="font-family: monospace;">use_prior_plot1d_parameters |
---|
858 | = .T.</span> and "<span style="font-family: monospace;">tra</span>" |
---|
859 | must be specified together)! </p> <p>Further |
---|
860 | information about output of |
---|
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> |
---|
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 |
---|
865 | file is created in case of particle transport (see the <a href="chapter_4.2.html#particles_package">particles |
---|
866 | package</a>). It contains statistical informations about the |
---|
867 | number of |
---|
868 | particles used and about the number of particles exchanged between each |
---|
869 | single PE. These informations are output after every timestep if |
---|
870 | switched on by parameter <a href="chapter_4.2.html#write_particle_statistics">write_particle_statistics</a>. |
---|
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 |
---|
876 | file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra |
---|
877 | package</a>). It contains the NAMELIST parameter set, with which |
---|
878 | the |
---|
879 | layout of a plot |
---|
880 | of the data in the local file <a href="#PLOTSP_X_DATA">PLOTSP_X_DATA</a> |
---|
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> |
---|
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>) |
---|
885 | needed by <span style="font-weight: bold;">profil</span>. |
---|
886 | The user can edit these parameter sets (and thus all details of the |
---|
887 | plot layout) after the run.<br> </p> <p>By default, |
---|
888 | for one quantity, all spectra at different heights |
---|
889 | are plotted into a single panel. Different colors and line styles are |
---|
890 | used for each height. Panels of up to four quantities are arranged on |
---|
891 | one page in two lines (and two columns). More quantities are plotted on |
---|
892 | additional page(s). If there is more than one output time (see <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>), |
---|
893 | additional pages will be plotted for each single output time. </p> |
---|
894 | </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">82<br> |
---|
895 | </td> <td style="vertical-align: top;"><a name="PLOTSP_X_DATA"></a>PLOTSP_X_DATA </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii<br> </td> <td style="vertical-align: top;">This |
---|
896 | file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra |
---|
897 | package</a>). It contains the spectral data along x (see <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>) |
---|
898 | in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>. |
---|
899 | The data can only be visualized with <span style="font-weight: bold;">profil</span> |
---|
900 | using NAMELIST parameter sets, which are written by |
---|
901 | the model to the local file <a href="#PLOTSP_X_PAR">PLOTSP_X_PAR</a>.<br> |
---|
902 | <br> |
---|
903 | Regardless of the (sub)set of spectra specified by <a href="chapter_4.2.html#plot_spectra_level">plot_spectra_level</a> |
---|
904 | for actual plotting, this file contains all data of spectra specified |
---|
905 | by <a href="chapter_4.2.html#comp_spectra_level">comp_spectra_level</a>.<br> |
---|
906 | <br> <font>Each data point of a spectrum is output in a |
---|
907 | single line |
---|
908 | (1st column: |
---|
909 | wavenumber, 2nd column: spectral coefficient). If spectra are to be |
---|
910 | calculated and output for more than one height (see </font><font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font><font>), |
---|
911 | the spectral coefficients for the further heights can be found in the |
---|
912 | subsequent columns. </font>The order |
---|
913 | of the data in the file follows the order used in the assignment for <span style="font-style: italic;"></span><span style="font-style: italic;"></span><a href="chapter_4.2.html#data_output_sp">data_output_sp</a>.<br> |
---|
914 | <br> |
---|
915 | For orientation, a header of comment lines (one for each height level) |
---|
916 | is placed in front of the spectral data of each quantity. They indicate |
---|
917 | the respective quantity and the output time. The text of these comment |
---|
918 | lines is used as a legend in the plot. </td> </tr> <tr> |
---|
919 | <td style="vertical-align: top; text-align: center;">83<br> |
---|
920 | </td> <td style="vertical-align: top;"><a name="PLOTSP_Y_PAR"></a>PLOTSP_Y_PAR </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii<br> </td> <td style="vertical-align: top;">This |
---|
921 | file is created if spectra along y are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra |
---|
922 | package</a>). It contains the NAMELIST parameter set, with which |
---|
923 | the |
---|
924 | layout of a plot |
---|
925 | of the data in the local file <a href="#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a> |
---|
926 | 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> |
---|
927 | <br> |
---|
928 | For more details see <a href="#PLOTSP_X_PAR">PLOTSP_X_PAR</a>.<br> |
---|
929 | </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">84<br> |
---|
930 | </td> <td style="vertical-align: top;"><a name="PLOTSP_Y_DATA"></a>PLOTSP_Y_DATA</td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii<br> </td> <td style="vertical-align: top;">This |
---|
931 | file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra |
---|
932 | package</a>). It contains the spectral data along y (see <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>) |
---|
933 | in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>. |
---|
934 | The data can only be visualized with <span style="font-weight: bold;">profil</span> |
---|
935 | using NAMELIST parameter sets, which are written by |
---|
936 | the model to the local file <a href="#PLOTSP_Y_PAR">PLOTSP_Y_PAR</a>.<br> |
---|
937 | <br> |
---|
938 | For more details see <a href="#PLOTSP_X_DATA">PLOTSP_X_DATA</a>.</td> |
---|
939 | </tr> <tr> <td style="vertical-align: top; text-align: center;">85<br> |
---|
940 | </td> <td style="vertical-align: top;"><a name="PARTICLE_DATA"></a>PARTICLE_DATA/</td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Binary<br> </td> <td style="vertical-align: top;">This |
---|
941 | file is created if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles |
---|
942 | package</a>) and contains all particle data for one or several |
---|
943 | output |
---|
944 | times (see <a href="chapter_4.2.html#dt_write_particle_data">dt_write_particle_data</a>).<br> |
---|
945 | <br> |
---|
946 | The first record of this file contains an identification string (PALM |
---|
947 | version number, run identifier, etc., 80 characters long). The second |
---|
948 | record also contains a version string (80 characters long) followed by |
---|
949 | two records with particle group informations (see file <span style="font-family: monospace;">check_open.f90</span>). |
---|
950 | Then, for each |
---|
951 | output time, two records follow, where the first one gives some general |
---|
952 | information (numbers of particles, etc.) and the second one contains |
---|
953 | the actual particle data. A FORTRAN TYPE structure is used for storing |
---|
954 | the particle attributes. See file <span style="font-family: monospace;">advec_particles.f90</span> |
---|
955 | for the detailed format.</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">90</td> |
---|
956 | <td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br> |
---|
957 | DATA_IN/</td> <td style="vertical-align: top;">I<br> |
---|
958 | </td> <td style="vertical-align: top;">Binary<br> |
---|
959 | </td> <td style="vertical-align: top;">Binary |
---|
960 | data, which are read in by the model at the beginning |
---|
961 | of a restart run (see <a href="chapter_3.3.html">chapter |
---|
962 | 3.3</a>). The appropriate file must have been written by the |
---|
963 | preceding |
---|
964 | job of the job chain (see <a href="#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a>). |
---|
965 | This file is needed if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles |
---|
966 | package</a>) and contains all particle informations (particle |
---|
967 | positions, velocities, etc.) from the end of the preceding run. |
---|
968 | Concerning runs on |
---|
969 | several processors it has to be noted that each processing element |
---|
970 | reads its own file and that the file content is processor-dependent. |
---|
971 | The |
---|
972 | number of processors which can be used must not be changed during a job |
---|
973 | chain and/or if a job chain is continued. <br> <br> |
---|
974 | The first record of this file contains a version number (four character |
---|
975 | string) of the subroutine, which output the data that follows (<span style="font-family: monospace;">write_particles</span>, |
---|
976 | see end of |
---|
977 | file <span style="font-family: monospace;">advec_particles.f90</span>). |
---|
978 | This number has to |
---|
979 | agree with the version number of the subroutine which is reading the |
---|
980 | file |
---|
981 | (<span style="font-family: monospace;">init_parrticles.f90</span>) |
---|
982 | in |
---|
983 | case of a restart run. Otherwise the model run |
---|
984 | is aborted. Version numbers are changed whenever new code revisions |
---|
985 | require a change of the file format. Some general informations like the |
---|
986 | number of particles stored in the file, the number of particle groups, |
---|
987 | etc.. are stored in the second record. The third record includes the |
---|
988 | particles to be released at the source and the fourth record contains |
---|
989 | all current particles. In case that particle tails are used (see <a href="chapter_4.2.html#maximum_number_of_tailpoints">maximum_number_of_tailpoints</a>), |
---|
990 | a further record may follow, which contains the particle tail |
---|
991 | informations. A FORTRAN TYPE structure is used for storing the particle |
---|
992 | attributes. For detailed informations about the file format see the |
---|
993 | corresponding READ statements in file <span style="font-family: monospace;">init_particles.f90</span> |
---|
994 | .<br> </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">90<br> |
---|
995 | </td> <td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br> |
---|
996 | DATA_OUT/</td> <td style="vertical-align: top;">O<br> |
---|
997 | </td> <td style="vertical-align: top;">Binary<br> |
---|
998 | </td> <td style="vertical-align: top;">Binary |
---|
999 | data, which are output at the end of the |
---|
1000 | run and possibly needed by restart runs (see <a href="chapter_3.3.html">chapter |
---|
1001 | 3.3</a>) for the initialization. This output file is then read as |
---|
1002 | file <a href="#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>. |
---|
1003 | The file is only written if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles |
---|
1004 | package</a>). For a more detailed description of the file |
---|
1005 | structure see <a href="#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>.</td> |
---|
1006 | </tr> <tr> <td style="vertical-align: top; text-align: center;">90<br> |
---|
1007 | </td> <td style="vertical-align: top;"> <p><a name="PLOT1D_PAR"></a>PLOT1D_PAR </p> |
---|
1008 | <p>and/or <br> |
---|
1009 | possibly </p> <p>PLOT1D_PAR_0 <br> |
---|
1010 | PLOT1D_PAR_1 <br> |
---|
1011 | |
---|
1012 | . <br> |
---|
1013 | |
---|
1014 | . <br> |
---|
1015 | |
---|
1016 | . <br> |
---|
1017 | PLOT1D_PAR_9</p> </td> <td style="vertical-align: top;">O<br> |
---|
1018 | </td> <td style="vertical-align: top;">Ascii/ |
---|
1019 | NAMELIST<br> </td> <td style="vertical-align: top;"> |
---|
1020 | <p>NAMELIST parameter set, with which the layout of a plot |
---|
1021 | of the data in the local file <a href="#PLOT1D_DATA">PLOT1D_DATA</a> |
---|
1022 | can be steered, if these data are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>. |
---|
1023 | </p> <p>This file contains the so-called RAHMEN (frame)- |
---|
1024 | and |
---|
1025 | CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&RAHMEN and/or |
---|
1026 | &CROSS</span>) |
---|
1027 | needed by <span style="font-weight: bold;">profil</span>. |
---|
1028 | These parameter sets (and thus all details of the plot layout) can be |
---|
1029 | edited after the model run by the user. By default, all profiles of one |
---|
1030 | variable saved at different times are drawn into one panel. Different |
---|
1031 | colors are used for each output time. Which profiles are drawn |
---|
1032 | into which plane and how these planes are arranged on the |
---|
1033 | plot, is determined with the parameters <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>, |
---|
1034 | <a href="chapter_4.2.html#profile_columns">profile_columns</a> |
---|
1035 | and <a href="chapter_4.2.html#profile_rows">profile_rows</a>. |
---|
1036 | </p> <p>The file PLOT1D_PAR is created by the model |
---|
1037 | briefly before |
---|
1038 | the end of a run. If a model run crashes uncontrolled (run time |
---|
1039 | errors or CPU - time exceeded), this file is usually missing, although |
---|
1040 | profile data were saved to the file PLOT1D_DATA. </p> <p>If |
---|
1041 | the model has to create profiles for different subdomains |
---|
1042 | (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>), |
---|
1043 | further files are created, whereby the file name includes the number of |
---|
1044 | the respective subdomain (e.g. PLOT1D_PAR_1). In this case the name of |
---|
1045 | the file with NAMELIST parameters of the total domain is |
---|
1046 | PLOT1D_PAR_0. </p> <p>For presentation in the |
---|
1047 | same plot, profile data of the restart |
---|
1048 | runs can be appended to existing data of preceding runs of a job chain. |
---|
1049 | One can do this with the file attribute <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#tra">tra</a> |
---|
1050 | in the file connection statement for PLOT1D_DATA. The model produces |
---|
1051 | a parameter file PLOT1D_PAR for these combined data, if the run |
---|
1052 | parameter is set <a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a> |
---|
1053 | = <i>.T</i>. If this is omitted, then the parameter file |
---|
1054 | gives |
---|
1055 | wrong plots (i.e. <span style="font-family: monospace;">use_prior_plot1d_parameters |
---|
1056 | = .T.</span> and "<span style="font-family: monospace;">tra</span>" |
---|
1057 | must be specified together)!</p> </td> </tr> <tr> |
---|
1058 | <td style="vertical-align: top; text-align: center;">90<br> |
---|
1059 | </td> <td style="vertical-align: top;"><a name="PLOT2D_XY_GLOBAL"></a>PLOT2D_XY_GLOBAL</td> |
---|
1060 | <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ <br> |
---|
1061 | NAMELIST</td> <td style="vertical-align: top;"> <p>NAMELIST |
---|
1062 | parameter set, with which the plot layout |
---|
1063 | of the data in local file <a href="#PLOT2D_XY">PLOT2D_XY</a> |
---|
1064 | 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>. |
---|
1065 | This file contains the so-called global parameter set (NAMELIST - group |
---|
1066 | name: &GLOBAL) needed by <span style="font-weight: bold;">iso2d</span>. |
---|
1067 | This parameter set can be edited |
---|
1068 | after the model run by the user. By default, the arrays are drawn using |
---|
1069 | isolines and each array |
---|
1070 | will be drawn onto a separate page (thus no color shading |
---|
1071 | presentation, no vector arrows, streamlines etc.). </p> |
---|
1072 | <p>Additionally <span style="font-weight: bold;">iso2d</span> |
---|
1073 | needs the so-called local parameter |
---|
1074 | sets. These are saved by the model to the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>. |
---|
1075 | Due to the fact that <span style="font-weight: bold;">iso2d</span> |
---|
1076 | expects global and local parameter sets on one and the same |
---|
1077 | file, in fact the global parameter set first, the user has to append |
---|
1078 | the contents of the file PLOT2D_XY_LOCAL to the file PLOT2D_XY_GLOBAL |
---|
1079 | before call of <span style="font-weight: bold;">iso2d</span> |
---|
1080 | (e.g. by |
---|
1081 | an OUTPUT - command in the MRUN - |
---|
1082 | configuration file: “cat PLOT2D_XY_LOCAL >> |
---|
1083 | PLOT2D_XY_GLOBAL”). |
---|
1084 | This |
---|
1085 | relatively pedantic proceedure is due to the fact that the model can |
---|
1086 | create the file PLOT2D_XY_GLOBAL only at the end of the simulation |
---|
1087 | (only then, when the final value of the global <span style="font-weight: bold;">iso2d</span>-parameter <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#PLANZ">planz</a> |
---|
1088 | is known), while the local parameter sets are written continuously |
---|
1089 | to the file PLOT2D_XY_LOCAL during the run. Since the file |
---|
1090 | PLOT2D_XY_GLOBAL needs to be addressed only briefly once, output-unit |
---|
1091 | 90 is used, which is also used for other files.</p> </td> </tr> |
---|
1092 | <tr> <td style="vertical-align: top; text-align: center;">90<br> |
---|
1093 | </td> <td style="vertical-align: top;"><a name="PLOT2D_XZ_GLOBAL"></a>PLOT2D_XZ_GLOBAL</td> |
---|
1094 | <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ <br> |
---|
1095 | NAMELIST</td> <td style="vertical-align: top;"> <p>NAMELIST |
---|
1096 | parameter set, with which the plot layout of the data |
---|
1097 | in the local file <a href="#PLOT2D_XZ">PLOT2D_XZ</a> |
---|
1098 | 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>. |
---|
1099 | </p> <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a> |
---|
1100 | applies to this file, respectively.</p> </td> </tr> |
---|
1101 | <tr> <td style="vertical-align: top; text-align: center;">90<br> |
---|
1102 | </td> <td style="vertical-align: top;"><a name="PLOT2D_YZ_GLOBAL"></a>PLOT2D_YZ_GLOBAL</td> |
---|
1103 | <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ <br> |
---|
1104 | NAMELIST</td> <td style="vertical-align: top;"> <p>NAMELIST |
---|
1105 | parameter set, with which the plot layout of the data |
---|
1106 | in the local file <a href="#PLOT2D_YZ">PLOT2D_YZ</a> |
---|
1107 | 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>. |
---|
1108 | </p> <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a> |
---|
1109 | applies to this file, respectively.</p> </td> </tr> |
---|
1110 | <tr> <td style="vertical-align: top; text-align: center;">90</td> |
---|
1111 | <td style="vertical-align: top;"><a name="TOPOGRAPHY_DATA"></a>TOPOGRAPHY_DATA</td> <td style="vertical-align: top;">I</td> <td style="vertical-align: top;">Ascii</td> <td>Two-dimensional <font color="#000000">topography height information</font> |
---|
1112 | in m.<br> |
---|
1113 | In case of <a href="chapter_4.1.html#topography">topography</a> |
---|
1114 | = <span style="font-style: italic;">'read_from_file'</span> |
---|
1115 | the subroutine <span style="font-family: Cumberland AMT;">init_grid</span> reads |
---|
1116 | the topography height information in m for each grid point in |
---|
1117 | a free floating point format. The data on file are laid out naturally, |
---|
1118 | i.e. in W-E orientation horizontally and in S-N orientation vertically, |
---|
1119 | they must thus be organized as follows:<br> <ul> <li>each |
---|
1120 | line contains height information in m from <span style="font-style: italic;">i = 0, ..., nx</span>,</li> |
---|
1121 | <li>the top line contains height information in m for <span style="font-style: italic;">j = ny</span> (North), the |
---|
1122 | bottom line for <span style="font-style: italic;">j = 0</span> |
---|
1123 | (South),</li> <li>individual data must be separated by at |
---|
1124 | least one blank.</li> </ul> |
---|
1125 | Layout sketch:<br> <span style="font-family: Cumberland AMT;"> |
---|
1126 | |
---|
1127 | N<br> |
---|
1128 | (0,ny) </span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny) |
---|
1129 | </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny) |
---|
1130 | ... </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny) |
---|
1131 | <span style="font-family: Times New Roman,Times,serif;"></span></span></font><font color="#000000"> top of file</font><font color="#000000"><span style="font-family: Cumberland AMT;"><span style="font-family: Times New Roman,Times,serif;"></span></span></font><br> |
---|
1132 | <font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"> |
---|
1133 | (0,ny-1) </span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny-1) </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny-1) |
---|
1134 | ... </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny-1) <br> |
---|
1135 | </span></font></font><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">W |
---|
1136 | (0,ny-2) </span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny-2) </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny-2) |
---|
1137 | ... </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny-2) E<br> |
---|
1138 | </span></font></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"> |
---|
1139 | |
---|
1140 | :<br> |
---|
1141 | |
---|
1142 | |
---|
1143 | :<br> </span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"> |
---|
1144 | (0,0) </span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,0) |
---|
1145 | </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,0) |
---|
1146 | ... </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,0) |
---|
1147 | </span></font></font></font><font color="#000000"> bottom of file</font><br> |
---|
1148 | <font color="#000000"><span style="font-family: Cumberland AMT;"> |
---|
1149 | |
---|
1150 | S</span></font><br> |
---|
1151 | <span style="font-family: Arial;"></span><br> |
---|
1152 | These data must exactly match the horizontal grid.<br> |
---|
1153 | Alternatively, the user may add code to the user interface subroutine <a href="chapter_3.5.1.html#user_init_grid">user_init_grid</a> |
---|
1154 | to allow different data formats.</td> <td><br> </td> |
---|
1155 | </tr> <tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">101</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XY_NETCDF"></a>DATA_2D_XY_NETCDF</font></td> |
---|
1156 | <td style="vertical-align: top;"><font color="#000000">I/O</font></td> |
---|
1157 | <td style="vertical-align: top;"><font color="#000000">Binary/<br> |
---|
1158 | NetCDF-<br> |
---|
1159 | format</font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000">This file |
---|
1160 | contains data of the two-dimensional horizontal |
---|
1161 | cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>) |
---|
1162 | in NetCDF format. The data in this file can be visualized by any |
---|
1163 | graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> |
---|
1164 | More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></td> |
---|
1165 | <td style="vertical-align: top;"><br> </td> </tr> |
---|
1166 | <tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">102</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XZ_NETCDF"></a>DATA_2D_XZ_NETCDF</font></td> |
---|
1167 | <td style="vertical-align: top;"><font color="#000000">I/O</font></td> |
---|
1168 | <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> |
---|
1169 | NetCDF-<br> |
---|
1170 | format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file |
---|
1171 | contains data of the two-dimensional vertical (xz) |
---|
1172 | cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>) |
---|
1173 | in NetCDF format. The data in this file can be visualized by any |
---|
1174 | graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> |
---|
1175 | More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></td> |
---|
1176 | <td style="vertical-align: top;"><br> </td> </tr> |
---|
1177 | <tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">103</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_NETCDF"></a>DATA_2D_YZ_NETCDF</font></td> |
---|
1178 | <td style="vertical-align: top;"><font color="#000000">I/O</font></td> |
---|
1179 | <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> |
---|
1180 | NetCDF-<br> |
---|
1181 | format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file |
---|
1182 | contains data of the two-dimensional vertical |
---|
1183 | (yz) cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>) |
---|
1184 | in NetCDF format. The data in this file can be visualized by any |
---|
1185 | graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> |
---|
1186 | More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></td> |
---|
1187 | <td style="vertical-align: top;"><br> </td> </tr> |
---|
1188 | <tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">104</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_PR_NETCDF"></a>DATA_1D_PR_NETCDF</font></td> |
---|
1189 | <td style="vertical-align: top;"><font color="#000000">I/O</font></td> |
---|
1190 | <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> |
---|
1191 | NetCDF-<br> |
---|
1192 | format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file |
---|
1193 | contains data of the horizontally averaged vertical profiles (see <a href="../app/chapter_4.2.html#data_output_pr">data_output_pr</a>) |
---|
1194 | in NetCDF format. The data in this file can be visualized by any |
---|
1195 | graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> |
---|
1196 | More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></td> |
---|
1197 | <td style="vertical-align: top;"><br> </td> </tr> |
---|
1198 | <tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">105</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_TS_NETCDF"></a>DATA_1D_TS_NETCDF</font></td> |
---|
1199 | <td style="vertical-align: top;"><font color="#000000">I/O</font></td> |
---|
1200 | <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> |
---|
1201 | NetCDF-<br> |
---|
1202 | format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file |
---|
1203 | contains data of the timeseries (see <a href="chapter_4.2.html#dt_dots">dt_dots</a>) |
---|
1204 | in NetCDF format. The data in this file can be visualized by any |
---|
1205 | graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> |
---|
1206 | More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></td> |
---|
1207 | <td style="vertical-align: top;"><br> </td> </tr> |
---|
1208 | <tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">106</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_NETCDF"></a>DATA_3D_NETCDF</font></td> |
---|
1209 | <td style="vertical-align: top;"><font color="#000000">I/O</font></td> |
---|
1210 | <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> |
---|
1211 | NetCDF-<br> |
---|
1212 | format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file |
---|
1213 | contains data of the 3d-volume data (see <a href="../app/chapter_4.2.html#data_output">data_output</a>) |
---|
1214 | in NetCDF format. The data in this file can be visualized by any |
---|
1215 | graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> |
---|
1216 | More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></td> |
---|
1217 | <td style="vertical-align: top;"><br> </td> </tr> |
---|
1218 | <tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">107</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_SP_NETCDF"></a>DATA_1D_SP_NETCDF</font></td> |
---|
1219 | <td style="vertical-align: top;"><font color="#000000">I/O</font></td> |
---|
1220 | <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> |
---|
1221 | NetCDF-<br> |
---|
1222 | format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file |
---|
1223 | contains data of the horizontal spectra (see <a href="../app/chapter_4.2.html#data_output_sp">data_output_sp</a>) |
---|
1224 | in NetCDF format. The data in this file can be visualized by any |
---|
1225 | graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> |
---|
1226 | More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></td> |
---|
1227 | <td style="vertical-align: top;"><br> </td> </tr> |
---|
1228 | <tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">108</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_PRT_NETCDF"></a>DATA_PRT_NETCDF/</font></td> |
---|
1229 | <td style="vertical-align: top;"><font color="#000000">I/O</font></td> |
---|
1230 | <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> |
---|
1231 | NetCDF-<br> |
---|
1232 | format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file |
---|
1233 | contains particle data (see <a href="../app/chapter_4.2.html#dt_prel">dt_prel</a>) |
---|
1234 | in NetCDF format. The data in this file can be visualized by any |
---|
1235 | graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> |
---|
1236 | More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></td> |
---|
1237 | <td style="vertical-align: top;"><br> </td> </tr> |
---|
1238 | <tr> <td style="vertical-align: top; text-align: center;">109</td> |
---|
1239 | <td align="left" valign="top"><a name="DATA_1D_PTS_NETCDF"></a>DATA_1D_PTS_NETCDF</td> |
---|
1240 | <td align="left" valign="top">I/O</td> <td align="left" valign="top">Binary/<br> |
---|
1241 | NetCDF-<br> |
---|
1242 | format</td> <td align="left" valign="top">This |
---|
1243 | file contains data of the timeseries of particle quantities (<font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">see <a href="chapter_4.2.html#dt_prel">dt_prel</a>) |
---|
1244 | in NetCDF format. </font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">The data |
---|
1245 | in this file can be visualized by any graphic software which provides a |
---|
1246 | NetCDF interface (e.g. <span style="font-weight: bold;">NCL |
---|
1247 | </span>or<span style="font-weight: bold;"> ferret</span>). |
---|
1248 | For a list of available output quantities see </font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"> <a href="chapter_4.2.html#dt_dopts">dt_dopts</a>.</font></font></font></font></font><br> |
---|
1249 | <font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><br> |
---|
1250 | </font></font></font></font><span lang="en-GB"><font face="Thorndale">In case of |
---|
1251 | using more than one particle group (see <a href="chapter_4.2.html#number_of_particle_groups">number_of_particle_groups</a>), |
---|
1252 | seperate time series are output for each of the groups. The long names |
---|
1253 | of the variables in the NetCDF file containing the respective |
---|
1254 | timeseries all end with the string</font><span style="font-style: italic; font-family: monospace;">' PG ##'</span><font face="Thorndale">, where ## is the number of the particle |
---|
1255 | group (<span style="font-style: italic;">01</span>, <span style="font-style: italic;">02</span>, etc.). <br> |
---|
1256 | <br> </font></span><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">More detailed informations about the |
---|
1257 | PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter |
---|
1258 | 4.5.1</a>.</font></font></font></font></td> |
---|
1259 | <td align="left" valign="top"></td> </tr> |
---|
1260 | <tr> <td style="text-align: center; vertical-align: top;">111</td> |
---|
1261 | <td style="vertical-align: top;"><a name="DATA_2D_XY_AV_NETCDF"></a>DATA_2D_XY_AV_NETCDF</td> |
---|
1262 | <td style="vertical-align: top;">I/O</td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br> |
---|
1263 | NetCDF-<br> |
---|
1264 | format</font></font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file |
---|
1265 | contains data of the temporally averaged two-dimensional horizontal |
---|
1266 | cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>) |
---|
1267 | in NetCDF format. The data in this file can be visualized by any |
---|
1268 | graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> |
---|
1269 | More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></td> |
---|
1270 | <td></td> </tr> <tr> <td style="text-align: center; vertical-align: top;">112</td> |
---|
1271 | <td style="vertical-align: top;"><a name="DATA_2D_XZ_AV_NETCDF"></a>DATA_2D_XZ_AV_NETCDF</td> |
---|
1272 | <td style="vertical-align: top;">I/O</td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br> |
---|
1273 | NetCDF-<br> |
---|
1274 | format</font></font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the temporally |
---|
1275 | averaged two-dimensional vertical (xz) |
---|
1276 | cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>) |
---|
1277 | in NetCDF format. The data in this file can be visualized by any |
---|
1278 | graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> |
---|
1279 | More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></font></td> |
---|
1280 | <td></td> </tr> <tr> <td style="text-align: center; vertical-align: top;">113</td> |
---|
1281 | <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_AV_NETCDF"></a>DATA_2D_YZ_AV_NETCDF</font></td> |
---|
1282 | <td style="vertical-align: top;">I/O</td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br> |
---|
1283 | NetCDF-<br> |
---|
1284 | format</font></font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the temporally |
---|
1285 | averaged two-dimensional vertical |
---|
1286 | (yz) cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>) |
---|
1287 | in NetCDF format. The data in this file can be visualized by any |
---|
1288 | graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> |
---|
1289 | More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></font></td> |
---|
1290 | <td></td> </tr> <tr> <td style="text-align: center; vertical-align: top;">116</td> |
---|
1291 | <td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_AV_NETCDF"></a>DATA_3D_AV_NETCDF</font></td> |
---|
1292 | <td style="vertical-align: top;">I/O</td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br> |
---|
1293 | NetCDF-<br> |
---|
1294 | format</font></font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the temporally |
---|
1295 | averaged 3d-volume data (see <a href="chapter_4.2.html#data_output">data_output</a>) |
---|
1296 | in NetCDF format. The data in this file can be visualized by any |
---|
1297 | graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> |
---|
1298 | More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></font></td> |
---|
1299 | <td></td> </tr> </tbody> |
---|
1300 | </table><font color="#000000"><br> |
---|
1301 | </font><br> |
---|
1302 | <font color="#000080"><font color="#000080"><a href="chapter_3.3.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.5.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font><br> |
---|
1303 | <br> |
---|
1304 | |
---|
1305 | <span style="font-style: italic;">Last change:</span> |
---|
1306 | $Id: chapter_3.4.html 62 2007-03-13 02:52:40Z letzel $<br> |
---|
1307 | </font><br></body></html> |
---|