source: palm/trunk/DOC/app/chapter_3.4.html @ 97

Last change on this file since 97 was 97, checked in by raasch, 16 years ago

ocean version including prognostic equation for salinity and equation of state for seawater. Routine buoyancy can be used with both temperature and density.
+ inipar-parameters bc_sa_t, bottom_salinityflux, ocean, sa_surface, sa_vertical_gradient, sa_vertical_gradient_level, top_salinityflux

advec_s_bc, average_3d_data, boundary_conds, buoyancy, check_parameters, data_output_2d, data_output_3d, diffusion_e, flow_statistics, header, init_grid, init_3d_model, modules, netcdf, parin, production_e, prognostic_equations, read_var_list, sum_up_3d_data, swap_timelevel, time_integration, user_interface, write_var_list, write_3d_binary

eqn_state_seawater, init_ocean


inipar-parameter use_pt_reference renamed use_reference

hydro_press renamed hyp, routine calc_mean_pt_profile renamed calc_mean_profile

format adjustments for the ocean version (run_control)

advec_particles, buoyancy, calc_liquid_water_content, check_parameters, diffusion_e, diffusivities, header, init_cloud_physics, modules, production_e, prognostic_equations, run_control


Bugfix: height above topography instead of height above level k=0 is used for calculating the mixing length (diffusion_e and diffusivities).

Bugfix: error in boundary condition for TKE removed (advec_s_bc)

advec_s_bc, diffusion_e, prognostic_equations

  • Property svn:keywords set to Id
File size: 88.5 KB
1<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
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
5output files</font></h3>
6<p style="line-height: 100%;"></p><p style="line-height: 100%;"><font color="#000000">The
7model works
8with a set of files, which are all located in the temporary working
9directory and which are either expected at the beginning of the run
10(the so-called input files) or which are
11produced during the run and/or at the end of the simulation (output
12files).</font><font color="#800000">
13<font color="#000000">The following table lists all
14default files
15addressed by the model. They are arranged according to the
16associated FORTRAN unit (unit number).</font> </font><font color="#000000">The
17unit 90 is used for different files, which are opened only briefly
18and uniquely in the model and closed directly afterwards.
19Unit numbers 101 - 109, 111 - 113, and 116&nbsp;refer to data files
20which have NetCDF format.
21These are not opened by a FORTRAN-OPEN-statement but by a corresponding
22NetCDF call (NF90_CREATE or NF90_OPEN). These files are only created on
23machines where a NetCDF library is available.<br>
24</font></p><p style="line-height: 100%;"><font color="#000000">The file
25names described in the list correspond to the names indicated in the
26respective OPEN instruction, i.e. the files are expected and saved
27under these names in the temporary working directory of the model. By
28default, file names are always written in capital letters. The
29third column indicates whether it is an input or output file (I
30and/or O). The NetCDF files can be both input and output files (I/O).
31If restart jobs shall append data to an existing NetCDF file (created
32by a previous job of the job chain), the respective file has to be
33given as an input file (see also <a href="../app/chapter_4.5.1.html">chapter
344.5.1</a> which gives more details about the PALM-NetCDF-output).</font>
36<p style="line-height: 100%;"> </p><p style="line-height: 100%;"><font color="#000000">On
38computers many of the files are read and/or written by the central
39processing element 0 (PE0) only. These files have processor-independent
40content (and therefore they can be read or written by other
41PEs just as well). However, certain files have processor-dependent
42content. For the binary output of data for restart runs (local file
43<a href="#BINOUT">BINOUT</a>),
44for example, <font color="#000000">each PE outputs only
45the data of
46its subdomain. So each processing element writes
47into its own file with its own file name. These files lie in a
48subdirectory of the temporary working directory. Their names are build
49off from the underline ("_ ") and the four digit
50processor ID. The data written for restart runs would be e.g. on the
51files BINOUT/_0000 (PE0), BINOUT/_0001 (PE1), BINOUT/_0002 (PE2) etc.
52Such files, which have processor-dependent content on parallel
53computers, are marked in the following list by the fact, that to the
54file name a line (&rdquo;/&ldquo;) is attached. If appropriate
56files are to be copied through <b>mrun</b> to permanent
57files, and/or
58files with processor-dependent content are supposed to be copied as
59input files into the temporary working directory of the model, you have
60to indicate a special file attribute in the appropriate file
61connection statement </font>(see <a href="">arpe</a>,
62<a href="">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
65name will be
66interpreted as a directory name, in which the input files are
67expected and/or to which output files are written. The file names in
68these directories are always named _0000, _0001, _0002 etc. </font>
69</font></p><font color="#000000"><font color="#000000">For internal use,
70the model may open a set of further files, which are not
71defined by the user but contain no usable information and
72therefore are not included in this list. <br>
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/&nbsp;
83<br>NAMELIST</p> </td> <td colspan="1" width="67%"> <p><font color="#000000">Parameter
84for model steering. This file
85is needed by the model in each case. Its content and structure is
86described in detail in</font> <a href="chapter_4.0.html">chapter
874.0</a>. <a href="chapter_4.4.1.html">Chapter
884.4.1</a> <font color="#000000">shows a simple
89example. </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,
94which are read in by the model at the beginning
95of a restart run (see <a href="chapter_3.3.html">chapter
963.3</a>). The appropriate file must have been written by the
98job of the job chain (see <a href="#BINOUT">BINOUT</a>).
99This file contains the initial parameters (see <a href="chapter_4.1.html">chapter
1004.1</a>) of the job chain, arrays of the prognostic and
102variables as well as those parameters and variables for plots of
103horizontally averaged vertical profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>),
104which have been determined by the job chain so far. Concerning runs on
105several processors it has to be noted that each processing element
106reads its own file and the file content is processor-dependent. The
107number of processors which can be used must not be changed during a job
108chain and/or if a job chain is continued.&nbsp; </p> <p>Knowledge
109of the file structure is usually not necessary,
110because the file is produced and also read again by the model, but it
111can be useful for error determination in case of read errors .
112Therefore the file structure is described in the following.&nbsp; </p>
113<p>The first record of this file contains a version number (ten
114character string) of the subroutine, which, which output the data that
115follows (write_var_list.f90). This number has to
116agree 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
118is aborted. Version numbers are changed whenever new code revisions
119require a change of the file format.&nbsp; </p> <p>Starting
120from the second record, all initial parameters follow
121(exception: <a href="chapter_4.1.html#initializing_actions">initializing_actions</a>),
122whereby each parameter fills two records. In the first record the name
123of the parameter is saved as a character string (30 characters long,
124short names are filled by trailing blanks, longer names are cut off at
125the end), in the second record the value (or the values) of the
126parameter follow. The sequence of parameters on the file may be
127arbitrary, however the first and second variable must be <a href="chapter_4.1.html#nz">nz</a>
128and <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>.
129If a variable with unknown name is found the model run is
130aborted.&nbsp; </p> <p>At the end of the initial
131parameters a record with the string "<i>***
132end ***</i>"follows (filled up with trailing blanks up to a
133length of
13430 characters).&nbsp; </p> <p>Afterwards the fields
135of the prognostic and diagnostic
136variables follow. This part of the file also begins with a record
137consisting of a character string of length 10, which contains the
138version number of the subroutine that wrote the arrays that follow
139(write_3d_binary.f90). It must agree with the number of the reading
140subroutine (read_3d_binary.f90).&nbsp; </p> <p>The
141following record contains the number of processors which
142were used in the model run producing this file, the processor ID of the
143special processor, which creates the file, as well as the lower and
144upper array indices of the subdomain belonging to this processing
145element. If no complete agreement with the values of the current model
146run exists, then this is aborted. This examination must be made in
147particular on parallel computers, because the jobs of a job chain
148always have to use the same number of processors and the same virtual
149processor grid.&nbsp; </p> <p>After these tests the
150individual arrays as well as parameters
151and variables for plots of horizontally averaged vertical profiles
152follow. Like the initialization parameters, they consist of two
153records. In the first record, the name of the array or the variable
154(character string, consisting of 20 characters, filled with trailing
155blanks) is located, in the second one its values follow. The sequence
156of the individual variables may be arbitrary again. The parameters for
157the plot and the respective variables are only read in if for the run
158parameter <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
160skipped.&nbsp; </p> <p>At the end of the file there
161has to be a record with the
162character string "<span style="font-style: italic;"></span><i>***
164***</i>"(filled up with trailing blanks up to a length of 20
165characters).</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,
171which are written by the model at the end of the
172run and possibly needed by restart runs (see <a href="chapter_3.3.html">chapter
1733.3</a>) for the initialization. This output file is then read in
175file <a href="#BININ">BININ</a>.
176It contains the initial parameters (see <a href="chapter_4.1.html">chapter
1774.1</a>) of the model run, arrays of the prognostic and
179variables as well as those parameters determined so far during a job
180chain and variables for plots of horizontally averaged vertical
181profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>).
182With runs on several processors it has to be noted that each processing
183element writes its own file and the file content is
184processor-dependent. A specification of the file format can be found in
186description of the file <a href="#BININ">BININ</a>.&nbsp;
187</p> <p>The file BINOUT is written by the model only if,
188with the help
189of the <b>mrun</b>-configuration file, the <font face="Thorndale, serif">value</font> <span style="font-family: monospace;">true</span> is
190assigned for the
192variable <span style="font-size: 10pt; font-family: monospace;">write_binary</span>
193(see <a href="chapter_3.3.html">chapter
1943.3</a>).&nbsp; </p> <p>With large grid point
195numbers the file BINOUT (or the
196files residing in directory BINOUT/) will be very large and should
197be 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
200the so-called time step control output of
201the model. At certain temporal intervals, which are described by the
203parameter <a href="chapter_4.1.html#dt_run_control">dt_run_control</a>,
204a line with the values of certain control parameters is written into
206file. Additionally, such a control line is always written, whenever the
207time step of the model changes. All data and quantities always refer to
208the entire model domain.&nbsp; </p> <p>If the
2091D-model is switched on for the initialization of the
2103D-models, then control lines are likewise written into this file at
211certain temporal intervals (see <a href="chapter_4.1.html#dt_run_control_1d">dt_run_control_1d</a>).&nbsp;
212</p> <p>By default, the file RUN_CONTROL only lists
214about the selected model parameters at the beginning of the
215initial run. These informations are written at the beginnning of a run.
216They correspond to those of the file <a href="#HEADER">HEADER</a>
217(however without data concerning the consumed CPU time, because these
219only known at the end of a run). With the run parameter <a href="chapter_4.2.html#force_print_header">force_print_header</a>
220it can be achieved that this information is also written at the
221beginning of the file RUN_CONTROL at restart runs.&nbsp; </p>
222<p>The individual columns of the 1D - time step control output
223have the following meaning (listed by the respective heading of the
225column in the file):&nbsp; <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
228accomplished so far</td> </tr> <tr> <td style="vertical-align: top;">HH:MM:SS</td> <td style="vertical-align: top;">Time (in hours: minutes:
229seconds)</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
233(u-component) (in m/s)</td> </tr> <tr> <td style="vertical-align: top;">VMAX</td> <td style="vertical-align: top;">Maximum absolute wind
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
239Prandtl 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
2421D-model (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>),
243averaged over all grid points</td> </tr> </tbody> </table>
245The individual columns of the 3D - time step control output
246have the following meaning (listed by the respective heading of the
248column 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
251in the job chain. The initial
252run 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
255accomplished since starting time t=0 of
256the 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:
258seconds) since starting time t=0 of the
259initial 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
260following character indicates whether the
262step is limited by the advection criterion (A) or the diffusion
263criterion (D). After changes of the time step a further character
265which indicates with which time step procedure the changed time step
266was accomplished (<span style="font-family: monospace;">L:</span>
267Leapfrog, <span style="font-family: monospace;">E:</span>
268Euler). This
270not 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
273velocity (u-component) (<font color="#000000">in </font>m/s).
274If at
276appropriate output time a random disturbance was added to the
277horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>),
278the 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
281velocity (v-component) (<font color="#000000">in </font>m/s).
282If at
284appropriate output time a random disturbance was added to the
285horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>),
286the 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
289velocity (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
292average of the
293friction 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
296velocity scale
297(<font color="#000000">in </font>m/s). The assumed
298boundary layer
299height 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
303of 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
306boundary layer (<font color="#000000">in </font>m),
307determined via
308the 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
310energy of the flow field (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>),
311normalized 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
314disturbance energy of flow field (<font color="#000000">in
316normalized 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
319of the velocity field (sum of
320the absolute values) (</font><font color="#000000">in
321</font><font color="#000000">1/s) before call of the
322pressure solver,
323normalized 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
326of the velocity field (sum of
327the absolute values) (</font><font color="#000000">in
328</font><font color="#000000">1/s) after call of the
329pressure solver, normalized</font>
330with 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
332with the maximum absolute
333u-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
336with the maximum absolute
337v-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
340with the maximum absolute
341w-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
344coordinate system has been moved in
345x-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
348coordinate system has been moved in
349y-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)
354averaged vertical profiles of some model variables. The quantities
355saved are set model-internally and can not be determined by the user.
356At each output time (see <a href="chapter_4.2.html#dt_dopr_listing">dt_dopr_listing</a>)
357two tables are written to the file consecutively. The first contains
358variables which are defined on the scalar / u-v-grid-levels, the
359second table contains variables which are defined on the w-grid-levels.
360If subdomains were defined with the initialization parameter <a href="chapter_4.1.html#statistic_regions">statistic_regions </a>for
361additional statistic evaluation, then the tables
362described above are written for each individual subdomain. The name of
363the respective subdomain (see <a href="chapter_4.3.html#region">region</a>)
364appears in the header of the respective table. <br>
365In each case the tables consist of a header, followed by the
366profiles arranged next to each other in columns. The header contains
367some basic information of the respective run (model version, run
368identifier consisting of
369basic file name and number of the job in the job chain, executing
370computer, date, time of the beginning of the run, name of the
371subdomain, output time, kind of averaging). On the u-v-level the
372following 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
375grid 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
377of the grid point
378level (<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
381of the wind
382velocity (<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
385of the
386u-component from the initial profile at the
387time 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
390of the wind
391velocity (<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
394of the
395v-component from the initial profile at the
396time t=0 (initialization profile) (<font color="#000000">in
397</font>m/s).</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">pt&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
398<br> </td> <td style="text-align: left; vertical-align: middle;">Potential
399temperature (<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
402of potential
403temperature from the initial profile at
404the 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
407kinetic 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
412coefficient 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
416coefficient 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
419length (<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>
423On 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
427grid point
428index.</td> </tr> <tr> <td style="vertical-align: middle;">zw<br> </td> <td style="vertical-align: middle;">Height of the grid
430level (<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
433kinematic heat flux (<font color="#000000">in </font>K
434m/s).</td> </tr> <tr> <td style="vertical-align: middle;">wpt</td> <td style="vertical-align: middle;">Vertical total (
435subgrid-scale + resolved)
436kinematic heat flux (<font color="#000000">in </font>K
437m/s).</td> </tr> <tr> <td style="vertical-align: middle;">w'u'</td> <td style="vertical-align: middle;">u-component of the
438vertical subgrid-scale momentum flux (<font color="#000000">in
440</tr> <tr> <td style="vertical-align: middle;">wu</td>
441<td style="vertical-align: middle;">u-component of the
443vertical momentum flux (
444subgrid-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
447vertical subgrid-scale momentum flux (<font color="#000000">in
449</tr> <tr> <td style="vertical-align: middle;">wv</td>
450<td style="vertical-align: middle;">v-component of the
452vertical momentum flux (
453subgrid-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
457profiles calculated by the
4581D-model within initial runs. The quantities saved are set
459model-internally and cannot be determined by the user. At the
460respective output times (see <a href="chapter_4.1.html#dt_pr_1d">dt_pr_1d</a>)
461a table with the following information is written to the file: The
462table header contains some basic information of the respective run
463(model version, run identifier consisting of basic file name and number
464of the job in the
465job chain (this number should always be 00, because the 1D-model is
466only switched on at initial runs), executing computer, date,
467time of the beginning of the run, output time). Afterwards the
468following 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
471grid 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
473of the grid point
474level (<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
477of the wind
478velocity (<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
481of the wind
482velocity (<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
485temperature (<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
488kinetic 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
491Richardson 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
494coefficient 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
498coefficient 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
501length (</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
506accomplished through the subroutine <span style="font-family: monospace;">cpu_log.f90.</span><span style="font-size: 10pt;"></span> The file
507CPU_MEASURES contains a header with some basic information of the
508respective run
509(model version, run identifier consisting of basic file name and
510number of the job in the job chain, executing computer, date, time of
511the beginning of the run) and afterwards two tables with data of CPU
512times which have been consumed by certain model parts. The model parts
513analyzed in the first table do not overlap and the CPU times needed for
514them therefore approximately add up to the &ldquo;total&rdquo;
515value given in the
516first line of this table. In the second table (heading: special
517measures) overlaps (in particular with the parts described in the first
518table) are possible.&nbsp; <br>
519For each model part it is indicated in the following columns how much
520CPU time was needed (absolutely and relative), and how often it was
521called.&nbsp; With runs on several processors the average values of
523processors are indicated. In the case of parallel runs information for
524those processors with the largest and smallest CPU time follow as
525well as the standard deviation of all PEs from the average value. With
527parallelization the CPU times on the individual processors should
528differ only little from each other and the standard deviation should be
529small.&nbsp; </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
533the selected model parameters (physical and
534numerical values) as well as general information about the
535run.&nbsp; </p> <p>This file contains the values of
536all important steering
538(numerical procedures, computing grid and model dimensions, boundary
539conditions, physical dimension, turbulence quantities, actions during
540the simulation, 1D-model-parameters) as well as data concerning the
541selected plot and list outputs. The headlines of the file list the
542program version used, date and time of the beginning of the run, the
543name of the executing computer, the run identifier (corresponds to the
544selected base file name) and the number of the run (number of the
545restart run). With parallel runs the number of processors as well as
546the assigned virtual processor net also appear. After these headlines
547run time and time step information appear (point of starting time,
548related to t=0 of the initial run, end-time, time actually reached, CPU
549time, etc.). If a model run is incorrectly terminated (e.g.
550run time error or excess of the permitted CPU time), information over
551the time reached and the necessary CPU time is missing (to understand:
552the file HEADER is written twice by the model; once briefly after
553beginning of the simulation (naturally here the information over the
554time reached is missing etc.) and then briefly before the normal end of
555the simulation. The second, now complete output overwrites the first
556output.).&nbsp; </p> <p>At the end of the file,
557information about the values of user
558parameters (see <a href="chapter_3.7.html">chapter
5593.7</a> and <a href="targetliste:chapter_1.0.html#chapter%204.3">chapter
5604.3</a>) can be output by the user with the help of the
561subroutine <tt><font style="font-size: 11pt;" size="2">user_header</font></tt>
562(located in
563the file <tt><font style="font-size: 10pt;" size="2">user_interface.f90</font></tt>).
564If no user parameters were found, the string &ldquo;<tt><font style="font-size: 10pt;" size="2">*** no user-defined
565variables found</font></tt>&rdquo;
566appears at the end of the file.
567If user parameters were indicated, the string &ldquo;<tt><font style="font-size: 11pt;" size="2">user-defined
568variables and actions</font></tt>&rdquo;
569is printed, followed by informations about the user-defined subdomains
570for which
571profiles and time series are output. All further information to appear
572here, must be provided by the user (by appropriate
573WRITE 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
579contains data of the two-dimensional horizontal
580cross sections written by the model (see <a href="chapter_4.2.html#data_output">data_output</a>)
581in a format readable by <a href="">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>,
584the individual arrays follow). The data are visualized with the help of
585ISO2D using
586NAMELIST - parameter sets, which are directly written by the model to
588local files <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
589and <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>.&nbsp;
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
592its subdomain
593to a separate file with the name
595whereby &lt;processor-Id&gt; is a four digit number (e.g.
596PLOT2D_XY_0000). These files are not suitable for ISO2D, but after the
598of the model run they can be combined to one file readable by ISO2D
600the help of the program <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>.
601This tool expects the files of the individual processing
602elements under the names described above and outputs the combined file
603under the name PLOT2D_XY. Usually it is called by an appropriate OUTPUT
604- command (OC:) in the MRUN-configuration file. The tool writes
605informative messages about the actions accomplished into the job
606protocol (e.g., even if no files were found).
607By the call of <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
608possibly existing files of the other cross sections (xz and/or yz)
609and three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>)
610are also combined.&nbsp; </p> <p>Further information
611about the output of plots of
612two-dimensional cross sections is found in the description of the run
613parameter <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
616the data of the xz
617cross sections written by the model.&nbsp; </p>
618The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
619applies 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
622the data of the xz
623cross sections written by the model.&nbsp; </p>
624The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
625applies 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 -
630parameter sets, with which the plot layout of the
631data in the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
632can be steered, if they are visualized with the plot program <a href="">ISO2D</a>.
633This file contains the so-called local parameter set (NAMELIST - group
634name: &amp;LOCAL) required by ISO2D (one parameter set for each
636present at the file PLOT2D_XY). After the model run these parameter
637sets can be edited by the user, if neccessary.&nbsp; </p> <p>Additionally
638ISO2D still needs another so-called global
639parameter set. This is saved by the model to the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>.
640Due to the fact that ISO2D expects global and local parameter sets on
641one and the same
642file, in fact the global parameter set first, the user has to append
644contents of the file PLOT2D_XY_LOCAL to the file PLOT2D_XY_GLOBAL
645before the call of ISO2D (e.g. by an OUTPUT-command in the
646MRUN-configuration file: &ldquo;PLOT2D_XY_LOCAL &gt;&gt;
648This relatively pedantic proceeding is due to the fact that the model
649can 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="">planz</a>
651is known), while the local parameter sets are written continuously
652to 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 -
657parameter sets, with which the plot layout of the
658data in the local file <a href="#PLOT2D_XZ">PLOT2D_XZ</a>
659can be steered, if they are visualized with the plot program <a href="">ISO2D</a>.&nbsp;
660</p> <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>
661applies 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 -
666parameter sets, with which the plot layout of the
667data in the local file <a href="#PLOT2D_YZ">PLOT2D_YZ</a>
668can be steered, if they are visualized with the plot program <a href="">ISO2D</a>.&nbsp;
669</p> <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>
670applies 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
673the data of the three-dimensional arrays
674(see <a href="chapter_4.2.html#data_output">data_output</a>)
675written by the model in a format readable for the visualization
676software AVS. Beyond that AVS
677needs coordinate information, which are output into the
678local file <a href="#PLOT3D_COOR">PLOT3D_COOR</a>,
679as well as the local files <a href="#PLOT3D_FLD">PLOT3D_FLD</a>
680and <a href="#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>,
681which describe the structure of the files PLOT3D_DATA and PLOT3D_COOR
682in the so-called AVS-FLD-format. Due to
683the 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
685the file PLOT3D_FLD by the user after the end of the model run (e.g.
686with an appropriate OUTPUT - command in the MRUN - configuration file: "<span style="font-family: monospace;">cat PLOT3D_FLD_COOR
687&gt;&gt; PLOT3D_FLD</span>").&nbsp; </p> <p>With
688parallel runs each processing element writes the data of
689its subdomain to a separate file with the name
690PLOT3D_DATA_&lt;Processor-Id&gt;, where
691&lt;Processor-Id&gt; is a
692four digit number (e.g. PLOT3D_DATA_0000). These files are not suitable
693for AVS, but after the end of the model run they can be combined to one
694file readable for AVS with the help of the program <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>.
695This tool expects the files of the individual processing
696elements under the names described above and outputs the combined file
697into a new file PLOT3D_DATA. Usually it is called by an appropriate
698OUTPUT - command in the MRUN-configuration file. The tool
699writes informative messages about the accomplished actions into
700the job protocol (e.g., even if no files were
701found). By the call of <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
702also possibly existing files with two-dimensional plot data (see e.g. <a href="#PLOT2D_XY">PLOT2D_XY</a>)
703are combined.&nbsp; </p> <p>With parallel runs the
704output of data of large volume is also
705possible in compressed form. For this purpose the initialization
706parameter&nbsp; <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>
707= <i>.TRUE.</i> must be set and the desired output
708accuracy has to be
710with the help of <a href="chapter_4.2.html#do3d_precision">do3d_precision</a>.
711In favorable cases the file size can be reduced by
712a factor of up to 5. For the visualization of compressed data a special
713AVS module (<tt><font style="font-size: 11pt;" size="2">read_compressed_field</font></tt>)
714and a further entry in the MRUN-configuration file are needed. More
715details can be found in <a href="chapter_4.5.6.html">chapter
7164.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
718information concerning
719the three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>)
720needed by the visualization software AVS.&nbsp; </p> <p>The
721file PLOT3D_COOR should be saved by the user into the same
722permanent directory as the file PLOT3D_DATA.&nbsp; </p> <p>For
723parallel 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/&nbsp; <br>
726AVS-Fld </td> <td style="vertical-align: top;"> <p>AVS-fld-file
727describing the three-dimensional
728array data, saved by the model into the local file <a href="#PLOT3D_DATA">PLOT3D_DATA</a>,
729needed by the visualization software AVS.&nbsp; </p> <p>This
730file describes the structure of the file PLOT3D_DATA
731(e.g. number of arrays, array dimensions, data type etc.). It uses the
732so-called AVS-Fld-format. It also contains the name of the file
733(inclusive cycle number, but without path) under which the local file
734PLOT3D_DATA is saved (this is the file name given in the file
735connection statement of the MRUN &ndash; configuration) in the
737directory of the user (possibly on remote computers). Under this name
738AVS expects the data which are to be visualized. If there is no file
739connection statement for PLOT3D_DATA indicated in the configuration
740file, that file (filename) is registered &ldquo;unknown&rdquo;
741in the file
742PLOT3D_FLD and the
743actual name must be inserted later by hand. The file PLOT3D_FLD should
744be saved by the user in the same permanent directory as PLOT3D_DATA, so
745that AVS can find the file PLOT3D_DATA without any problems. If the two
746files lie in different directories, then the path name of the file
747PLOT3D_DATA must be added.&nbsp; </p> <p>AVS-fld-files
748are expected by AVS to have the
749suffix "<span style="font-family: monospace;">.fld</span>"<font face="Cumberland, monospace">.</font>
750Cycle numbers must not be attached behind this "<span style="font-family: monospace;">.fld</span>" suffix.
751This suffix is
752attached to the permanent file names (still after
753possible cycle numbers) by <span style="font-weight: bold;">mrun</span>
754if&nbsp;"<span style="font-family: monospace;">fld</span>"
755is indicated in the <a href="">column
7566 </a>of the file connection statement.&nbsp; </p> <p>Likewise,
757AVS expects information about the coordinate
758system underlying the arrays on this file. This information is output
759by the model
760into the local file <a href="#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>,
761whose content the user has to append to the file PLOT3D_FLD after the
762end of the model run (e.g. with an appropriate OUTPUT-command in the
763MRUN-configuration file: &ldquo;cat PLOT3D_FLD_COOR
765PLOT3D_FLD&rdquo;).&nbsp; </p> <p>For parallel
766runs, 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/&nbsp; <br>
770AVS-Fld </td> <td style="vertical-align: top;"> <p>File
771for the description of the coordinate information output
772by the model into the local file <a href="#PLOT3D_COOR">PLOT3D_COOR</a>,
773which is needed for the visualization of three-dimensional array data
774by visualization-software AVS.&nbsp; </p> <p>This
775file describes the structure of the file PLOT3D_COOR
776(e.g. grid spacing, data type etc.) using the so-called AVS-Fld-format.
777It also contains the name of the file (inclusive cycle number, but
778without path) into which the local file PLOT3D_COOR (this is the file
779name described in the file connection statement of the MRUN -
780configuration file) is output in the permanent directory of the user
781(possibly on remote computers). Under this name AVS expects the data
782which are to be visualized. If there is no file connection statement
784PLOT3D_COOR indicated in the configuration file, that file is
785registered as "unknown" in the file
786PLOT3D_FLD_COOR and the actual name
787must be inserted later by hand.&nbsp; </p> <p>AVS
788expects the information contained in the file
789PLOT3D_FLD_COOR, as well as the remaining information about the
790three-dimensional arrays output by the model (see <a href="#PLOT3D_FLD">PLOT3D_FLD</a>)
791in one and the same file. This is satisfied by appending the file
792PLOT3D_FLD_COOR after the end of a run are to the
793file PLOT3D_FLD (e.g. with an appropriate OUTPUT-command in the
794MRUN-configuration file: &ldquo;cat PLOT3D_FLD_COOR
796PLOT3D_FLD&rdquo;).&nbsp; </p> <p>For parallel
797runs, 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&nbsp; </p> <p align="center">and/or&nbsp; <br>
800possibly&nbsp; </p> <p align="center">40-49</p>
801</td> <td style="vertical-align: top;"> <p><a name="PLOT1D_DATA"></a>PLOT1D_DATA&nbsp; </p>
802<p>and/or&nbsp; <br>
803possibly&nbsp; </p>
804PLOT1D_DATA_0&nbsp; <br>
805PLOT1D_DATA_1&nbsp; </td> <td style="vertical-align: top;">O </td> <td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;"> <p>This file contains
806data (possibly horizontally and/or
807temporally averaged) of the vertical profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>)
808written by the model in a format readable by <a href="">profil</a>.
809It 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>
811is assigned. This file's format is suitable to be read by the plot
812software <a href="">profil</a>.
813Each data point of the profiles is output in one single line (1st
814column: height in m, 2nd column: value of the respective quantity).
815Within the file, data
816of the individual profiles are located one behind the other. The order
817of 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>,&hellip;
819means that the file starts with the data of the u-component profile,
820followed by the v-component profile, etc.).&nbsp;</p> <p><br>
821The data can only be visualized with <span style="font-weight: bold;">profil</span>
822using NAMELIST-parameter sets, which are saved by the
823model into the local file <a href="#PLOT1D_PAR">PLOT1D_PAR</a>.&nbsp;
824</p> <p>The profile data written to the file are described
825with the
826run parameter <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>.
827Plots produced with these data using the parameter file PLOT1D_PAR do
828not have to contain all these profiles. The profiles which can be drawn
829in the plot are described with run parameter <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>.
830By subsequent editing of the file PLOT1D_PAR all profiles can be
831plotted (also the basic layout of the plots can be
832changed). For orientation, each profile existing on the file
833PLOT1D_DATA, starts with a comment line, which indicates the
834presented variable and the output time. The text of these comment
835lines is used as a legend in the plot. The very first line of the file
836is a
837comment line, containing information about the used model version, the
838run identifier (base file name + number of the respective restart
839run), the name of the executing computer, as well as the date and time
840of the beginning of the run. At the end of this comment line is the
842of the subdomain, to which the profiles belong (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
843By default, the profiles present averages of the total model domain. If
844the model has to produce profiles for other subdomains beyond that, up
845to 9 further files (units No. 41-49) are created, whereby the number of
846the respective subdomain is attached
847to the file name (e.g. PLOT1D_DATA_1). The name of the file with the
848data of the total
849domain in this case reads PLOT1D_DATA_0.&nbsp; </p> <p>For
850presentation in the same plot, profile data of the restart
851runs can be attached to existing data of preceding runs of a job chain.
852One can do this with the file attribute <a href="">tra</a>
853in 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
857wrong plots (i.e. <span style="font-family: monospace;">use_prior_plot1d_parameters
858= .T.</span> and "<span style="font-family: monospace;">tra</span>"
859must be specified together)!&nbsp; </p> <p>Further
860information about output of
861vertical 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
865file is created in case of particle transport (see the <a href="chapter_4.2.html#particles_package">particles
866package</a>). It contains statistical informations about the
867number of
868particles used and about the number of particles exchanged between each
869single PE. These informations are output after every timestep if
870switched 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>
875NAMELIST </td> <td style="vertical-align: top;">This
876file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
877package</a>). It contains the NAMELIST parameter set, with which
879layout of a plot
880of the data in the local file <a href="#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
881can be steered, if these data are plotted with the plot software <a href="">profil</a>.<br>
882<p>It contains the so-called RAHMEN (frame)- and
883CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&amp;RAHMEN and/or
885needed by <span style="font-weight: bold;">profil</span>.
886The user can edit these parameter sets (and thus all details of the
887plot layout) after the run.<br> </p> <p>By default,
888for one quantity, all spectra at different heights
889are plotted into a single panel. Different colors and line styles are
890used for each height. Panels of up to four quantities are arranged on
891one page in two lines (and two columns). More quantities are plotted on
892additional page(s). If there is more than one output time (see <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>),
893additional 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
896file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
897package</a>). It contains the spectral data along x (see <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>)
898in a format readable by <a href="">profil</a>.
899The data can only be visualized with <span style="font-weight: bold;">profil</span>
900using NAMELIST parameter sets, which are written by
901the model to the local file <a href="#PLOTSP_X_PAR">PLOTSP_X_PAR</a>.<br>
903Regardless of the (sub)set of spectra specified by <a href="chapter_4.2.html#plot_spectra_level">plot_spectra_level</a>
904for actual plotting, this file contains all data of spectra specified
905by <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
907single line
908(1st column:
909wavenumber, 2nd column: spectral coefficient). If spectra are to be
910calculated 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>),
911the spectral coefficients for the further heights can be found in the
912subsequent columns. </font>The order
913of 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>
915For orientation, a header of comment lines (one for each height level)
916is placed in front of the spectral data of each quantity. They indicate
917the respective quantity and the output time. The text of these comment
918lines 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
921file is created if spectra along y are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
922package</a>). It contains the NAMELIST parameter set, with which
924layout of a plot
925of the data in the local file <a href="#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
926can be steered, if these data are plotted with the plot software <a href="">profil</a>.<br>
928For 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
931file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
932package</a>). It contains the spectral data along y (see <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>)
933in a format readable by <a href="">profil</a>.
934The data can only be visualized with <span style="font-weight: bold;">profil</span>
935using NAMELIST parameter sets, which are written by
936the model to the local file <a href="#PLOTSP_Y_PAR">PLOTSP_Y_PAR</a>.<br>
938For 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
941file is created if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles
942package</a>) and contains all particle data for one or several
944times (see <a href="chapter_4.2.html#dt_write_particle_data">dt_write_particle_data</a>).<br>
946The first record of this file contains an identification string (PALM
947version number, run identifier, etc., 80 characters long). The second
948record also contains a version string (80 characters long) followed by
949two records with particle group informations (see file <span style="font-family: monospace;">check_open.f90</span>).
950Then, for each
951output time, two records follow, where the first one gives some general
952information (numbers of particles, etc.) and the second one contains
953the actual particle data. A FORTRAN TYPE structure is used for storing
954the particle attributes. See file <span style="font-family: monospace;">advec_particles.f90</span>
955for 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>
957DATA_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
960data, which are read in by the model at the beginning
961of a restart run (see <a href="chapter_3.3.html">chapter
9623.3</a>). The appropriate file must have been written by the
964job of the job chain (see <a href="#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a>).
965This file is needed if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles
966package</a>) and contains all particle informations (particle
967positions, velocities, etc.) from the end of the preceding run.
968Concerning runs on
969several processors it has to be noted that each processing element
970reads its own file and that the file content is processor-dependent.
972number of processors which can be used must not be changed during a job
973chain and/or if a job chain is continued. <br> <br>
974The first record of this file contains a version number (four character
975string) of the subroutine, which output the data that follows (<span style="font-family: monospace;">write_particles</span>,
976see end of
977file <span style="font-family: monospace;">advec_particles.f90</span>).
978This number has to
979agree with the version number of the subroutine which is reading the
981(<span style="font-family: monospace;">init_parrticles.f90</span>)
983case of a restart run. Otherwise the model run
984is aborted. Version numbers are changed whenever new code revisions
985require a change of the file format. Some general informations like the
986number of particles stored in the file, the number of particle groups,
987etc.. are stored in the second record. The third record includes the
988particles to be released at the source and the fourth record contains
989all 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>),
990a further record may follow, which contains the particle tail
991informations. A FORTRAN TYPE structure is used for storing the particle
992attributes. For detailed informations about the file format see the
993corresponding 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>
996DATA_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
999data, which are output at the end of the
1000run and possibly needed by restart runs (see <a href="chapter_3.3.html">chapter
10013.3</a>) for the initialization. This output file is then read as
1003The file is only written if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles
1004package</a>). For a more detailed description of the file
1005structure 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&nbsp; </p>
1008<p>and/or&nbsp; <br>
1009possibly&nbsp; </p> <p>PLOT1D_PAR_0&nbsp; <br>
1010PLOT1D_PAR_1&nbsp; <br>
1012.&nbsp; <br>
1014.&nbsp; <br>
1016.&nbsp; <br>
1017PLOT1D_PAR_9</p> </td> <td style="vertical-align: top;">O<br>
1018</td> <td style="vertical-align: top;">Ascii/
1019NAMELIST<br> </td> <td style="vertical-align: top;">
1020<p>NAMELIST parameter set, with which the layout of a plot
1021of the data in the local file <a href="#PLOT1D_DATA">PLOT1D_DATA</a>
1022can be steered, if these data are visualized with the plot program <a href="">profil</a>.&nbsp;
1023</p> <p>This file contains the so-called RAHMEN (frame)-
1025CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&amp;RAHMEN and/or
1027needed by <span style="font-weight: bold;">profil</span>.
1028These parameter sets (and thus all details of the plot layout) can be
1029edited after the model run by the user. By default, all profiles of one
1030variable saved at different times are drawn into one panel. Different
1031colors are used for each output time. Which profiles are drawn
1032into which plane and how these planes are arranged on the
1033plot, 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>
1035and <a href="chapter_4.2.html#profile_rows">profile_rows</a>.&nbsp;
1036</p> <p>The file PLOT1D_PAR is created by the model
1037briefly before
1038the end of a run. If a model run crashes uncontrolled (run time
1039errors or CPU - time exceeded), this file is usually missing, although
1040profile data were saved to the file PLOT1D_DATA.&nbsp; </p> <p>If
1041the model has to create profiles for different subdomains
1042(see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>),
1043further files are created, whereby the file name includes the number of
1044the respective subdomain (e.g. PLOT1D_PAR_1). In this case the name of
1045the file with NAMELIST parameters of the total domain is
1046PLOT1D_PAR_0.&nbsp; </p> <p>For presentation in the
1047same plot, profile data of the restart
1048runs can be appended to existing data of preceding runs of a job chain.
1049One can do this with the file attribute <a href="">tra</a>
1050in the file connection statement for PLOT1D_DATA. The model produces
1051a parameter file PLOT1D_PAR for these combined data, if the run
1052parameter 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
1055wrong plots (i.e. <span style="font-family: monospace;">use_prior_plot1d_parameters
1056= .T.</span> and "<span style="font-family: monospace;">tra</span>"
1057must 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/&nbsp; <br>
1061NAMELIST</td> <td style="vertical-align: top;"> <p>NAMELIST
1062parameter set, with which the plot layout
1063of the data in local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
1064can be steered, if they are visualized with the plot program <a href="">iso2d</a>.
1065This file contains the so-called global parameter set (NAMELIST - group
1066name: &amp;GLOBAL) needed by <span style="font-weight: bold;">iso2d</span>.
1067This parameter set can be edited
1068after the model run by the user. By default, the arrays are drawn using
1069isolines and each array
1070will be drawn onto a separate page (thus no color shading
1071presentation, no vector arrows, streamlines etc.).&nbsp; </p>
1072<p>Additionally <span style="font-weight: bold;">iso2d</span>
1073needs the so-called local parameter
1074sets. These are saved by the model to the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>.
1075Due to the fact that <span style="font-weight: bold;">iso2d</span>
1076expects global and local parameter sets on one and the same
1077file, in fact the global parameter set first, the user has to append
1078the contents of the file PLOT2D_XY_LOCAL to the file PLOT2D_XY_GLOBAL
1079before call of <span style="font-weight: bold;">iso2d</span>
1080(e.g. by
1081an OUTPUT - command in the MRUN -
1082configuration file: &ldquo;cat PLOT2D_XY_LOCAL &gt;&gt;
1085relatively pedantic proceedure is due to the fact that the model can
1086create 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="">planz</a>
1088is known), while the local parameter sets are written continuously
1089to the file PLOT2D_XY_LOCAL during the run. Since the file
1090PLOT2D_XY_GLOBAL needs to be addressed only briefly once, output-unit
109190 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/&nbsp; <br>
1095NAMELIST</td> <td style="vertical-align: top;"> <p>NAMELIST
1096parameter set, with which the plot layout of the data
1097in the local file <a href="#PLOT2D_XZ">PLOT2D_XZ</a>
1098can be steered, if they are visualized with the plot program <a href="">iso2d</a>.&nbsp;
1099</p> <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
1100applies 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/&nbsp; <br>
1104NAMELIST</td> <td style="vertical-align: top;"> <p>NAMELIST
1105parameter set, with which the plot layout of the data
1106in the local file <a href="#PLOT2D_YZ">PLOT2D_YZ</a>
1107can be steered, if they are visualized with the plot program <a href="">iso2d</a>.&nbsp;
1108</p> <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
1109applies 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&nbsp;<font color="#000000">topography height information</font>
1112in m.<br>
1113In case of &nbsp;<a href="chapter_4.1.html#topography">topography</a>
1114= <span style="font-style: italic;">'read_from_file'</span>
1115the&nbsp;subroutine <span style="font-family: Cumberland AMT;">init_grid</span>&nbsp;reads
1116the topography height information in m for each grid point in
1117a free floating point format. The data on file are laid out naturally,
1118i.e. in W-E orientation horizontally and in S-N orientation vertically,
1119they must thus be organized as follows:<br> <ul> <li>each
1120line 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
1122bottom line for <span style="font-style: italic;">j = 0</span>
1123(South),</li> <li>individual data must be separated by at
1124least one blank.</li> </ul>
1125Layout sketch:<br> <span style="font-family: Cumberland AMT;">&nbsp;
1126&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
1127&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp;N<br>
1128&nbsp; &nbsp; (0,ny) &nbsp;&nbsp;</span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny)
1129&nbsp;&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny) &nbsp;
1130...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny) &nbsp;
1131&nbsp; &nbsp;<span style="font-family: Times New Roman,Times,serif;"></span></span></font><font color="#000000">&nbsp;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;">&nbsp; &nbsp;
1133(0,ny-1)&nbsp;</span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny-1)&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny-1)
1134...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny-1) &nbsp;<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 &nbsp;
1136(0,ny-2)&nbsp;</span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny-2)&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny-2)
1137...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny-2) &nbsp; E<br>
1138</span></font></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp;
1139&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
1140&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;:<br>
1141&nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp;
1142&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
1143&nbsp;:<br> </span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp;
1144(0,0) &nbsp;&nbsp;&nbsp;</span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,0)
1145&nbsp;&nbsp;&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,0)
1146&nbsp; &nbsp;...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,0)
1147&nbsp; &nbsp; &nbsp;&nbsp;</span></font></font></font><font color="#000000">&nbsp;bottom of file</font><br>
1148<font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp;
1149&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
1150&nbsp; &nbsp; &nbsp;&nbsp; &nbsp;S</span></font><br>
1151<span style="font-family: Arial;"></span><br>
1152These data must exactly match the horizontal grid.<br>
1153Alternatively, the user may add code to the user interface subroutine <a href="chapter_3.5.1.html#user_init_grid">user_init_grid</a>
1154to 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>
1159format</font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000">This file
1160contains data of the two-dimensional horizontal
1161cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
1162in NetCDF format. The data in this file can be visualized by any
1163graphic 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>
1164More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 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>
1170format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
1171contains data of the two-dimensional vertical (xz)
1172cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
1173in NetCDF format. The data in this file can be visualized by any
1174graphic 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>
1175More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 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>
1181format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
1182contains data of the two-dimensional vertical
1183(yz) cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
1184in NetCDF format. The data in this file can be visualized by any
1185graphic 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>
1186More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 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>
1192format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
1193contains data of the horizontally averaged vertical profiles (see <a href="../app/chapter_4.2.html#data_output_pr">data_output_pr</a>)
1194in NetCDF format. The data in this file can be visualized by any
1195graphic 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>
1196More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 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>
1202format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
1203contains data of the timeseries (see <a href="chapter_4.2.html#dt_dots">dt_dots</a>)
1204in NetCDF format. The data in this file can be visualized by any
1205graphic 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>
1206More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 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>
1212format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
1213contains data of the 3d-volume data (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
1214in NetCDF format. The data in this file can be visualized by any
1215graphic 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>
1216More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 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>
1222format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
1223contains data of the horizontal spectra (see <a href="../app/chapter_4.2.html#data_output_sp">data_output_sp</a>)
1224in NetCDF format. The data in this file can be visualized by any
1225graphic 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>
1226More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 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>
1232format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
1233contains particle data (see <a href="../app/chapter_4.2.html#dt_prel">dt_prel</a>)
1234in NetCDF format. The data in this file can be visualized by any
1235graphic 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>
1236More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 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>
1242format</td> <td align="left" valign="top">This
1243file 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>)
1244in NetCDF format.&nbsp;</font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">The data
1245in this file can be visualized by any graphic software which provides a
1246NetCDF interface (e.g. <span style="font-weight: bold;">NCL
1247</span>or<span style="font-weight: bold;"> ferret</span>).
1248For 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
1251using more than one particle group (see <a href="chapter_4.2.html#number_of_particle_groups">number_of_particle_groups</a>),
1252seperate time series are output for each of the groups. The long names
1253of the variables in the NetCDF file containing the respective
1254timeseries 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
1255group (<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
1257PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter&nbsp;
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>
1264format</font></font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
1265contains data of the temporally averaged two-dimensional horizontal
1266cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
1267in NetCDF format. The data in this file can be visualized by any
1268graphic 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>
1269More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter&nbsp; 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>
1274format</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
1275averaged two-dimensional vertical (xz)
1276cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
1277in NetCDF format. The data in this file can be visualized by any
1278graphic 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>
1279More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter&nbsp; 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>
1284format</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
1285averaged two-dimensional vertical
1286(yz) cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
1287in NetCDF format. The data in this file can be visualized by any
1288graphic 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>
1289More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter&nbsp; 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>
1294format</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
1295averaged 3d-volume data (see <a href="chapter_4.2.html#data_output">data_output</a>)
1296in NetCDF format. The data in this file can be visualized by any
1297graphic 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>
1298More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></font></td>
1299<td></td> </tr> </tbody>
1300</table><font color="#000000"><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>&nbsp;
1305<span style="font-style: italic;">Last change:</span>
1306$Id: chapter_3.4.html 97 2007-06-21 08:23:15Z raasch $<br>
Note: See TracBrowser for help on using the repository browser.