Index: palm/trunk/DOC/app/chapter_4.5.1.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.5.1.html	(revision 97)
+++ palm/trunk/DOC/app/chapter_4.5.1.html	(revision 519)
@@ -1,4 +1,5 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <html><head>
+
 <meta content="text/html; charset=windows-1252" http-equiv="CONTENT-TYPE"><title>PALM chapter 4.5.1</title>
 <meta content="StarOffice 7 (Win32)" name="GENERATOR">
@@ -7,11 +8,10 @@
 @page { size: 21cm 29.7cm }
 -->
-</style></head>
-<body style="direction: ltr;" lang="en-US"><h4 style="line-height: 100%;"><font size="4">4.5.1
+</style></head><body style="direction: ltr;" lang="en-US"><h4 style="line-height: 100%;"><font size="4">4.5.1
 NetCDF data output&nbsp;<span style="color: rgb(255, 0, 0);"></span></font></h4>
 <p style="line-height: 100%;">The standard data output of
 PALM is NetCDF (<span style="font-weight: bold;">Net</span>work
-<span style="font-weight: bold;">C</span>ommon <span style="font-weight: bold;">D</span>ata <span style="font-weight: bold;">F</span>orm). NetCDF is an
-interface to a library of data access functions<br>for
+<span style="font-weight: bold;">C</span>ommon <span style="font-weight: bold;">D</span>ata <span style="font-weight: bold;">F</span>orm) in 64-bit offset format. NetCDF is an
+interface to a library of data access functions for
 storing and retrieving data in the form of arrays. NetCDF is an
 abstraction that supports a view of data as a collection of
@@ -36,5 +36,5 @@
 on <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/manual/netcdf/netcdf-3_f90_tutorial.pdf">our
 web server</a>.</p><p style="line-height: 100%;">The
-output format of PALM data is determined by the runtime-parameter <a href="chapter_4.2.html#data_output_format">data_output_format</a>
+general output format of PALM data is determined by the runtime-parameter <a href="chapter_4.2.html#data_output_format">data_output_format</a>
 (<span style="font-weight: bold;">data_output_format</span>
 = <span style="font-style: italic;">'netcdf'</span>,
@@ -42,11 +42,12 @@
 selected (see <a href="chapter_4.2.html#data_output_format">data_output_format</a>).
 The accuracy of the NetCDF output data can be set with parameter <a href="chapter_4.1.html#netcdf_precision">netcdf_precision</a>.
-By default, data have single (4 byte) precision. Also by default,
-NetCDF datasets (files) are not allowed to be larger than 2 GByte.
-Larger datasets can be created&nbsp;by setting <a href="chapter_4.2.html#netcdf_64bit">netcdf_64bit</a>
-= <span style="font-style: italic;">.TRUE.</span>.
-These files then have the so-called 64bit-offset format. However,
-currently, many of the existing application programs may not support
-this 64-bit offset format.<br></p>PALM allows the output of
+By default, data have single (4 byte) precision. Runtime-parameter <a href="chapter_4.2.html#netcdf_data_format">netcdf_data_format</a>
+can be used to choose between the different NetCDF file formats
+(classic, 64-bit offset, NetCDF4/HDF5). The 64-bit offset format allows
+creating large files (file size only limited by the underlying file
+system), but each output variable (array) is still limited to 2GB. In
+NetCDF4 format, there is no limit for the size of variables, and it
+also allows parallel I/O into one output file. However, some (graphic)
+software still does not support NetCDF4 format.<br></p>PALM allows the output of
 various
 data (e.g. cross sections, vertical profiles, timeseries, etc.) into
@@ -157,5 +158,7 @@
 or <a href="chapter_4.2.html#skip_time_do3d">skip_time_do3d</a>)</td></tr><tr><td align="undefined" valign="undefined">particle
 timeseries</td><td style="vertical-align: top;"><a href="chapter_3.4.html#DATA_1D_PTS_NETCDF">DATA_1D_PTS_NETCDF</a></td><td style="vertical-align: top;"><a href="chapter_4.2.html#dt_data_output">dt_data_output</a>
-(or <a href="chapter_4.2.html#dt_dopts">dt_dopts</a>)</td><td align="undefined" valign="undefined"></td></tr><tr><td align="left" valign="top">particle attributes</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_PRT_NETCDF">DATA_PRT_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#dt_write_particle_data">dt_write_particle_data</a></td><td align="left" valign="top"></td></tr></tbody></table><br><br><span style="font-weight: bold;">Creating, contents and
+(or <a href="chapter_4.2.html#dt_dopts">dt_dopts</a>)</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="left" valign="top">particle attributes</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_PRT_NETCDF">DATA_PRT_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#dt_write_particle_data">dt_write_particle_data</a></td><td align="left" valign="top"><br>
+</td></tr></tbody></table><br><br><span style="font-weight: bold;">Creating, contents and
 post-processing of a PALM NetCDF file</span><br><br>This
 section describes, step-by-step, the creation, storage, and
@@ -208,5 +211,5 @@
 the respective <b>mrun</b> call is
 like<br><br><span style="font-family: monospace;">&nbsp;
-&nbsp;mrun -d&nbsp; test -r &ldquo;xy#&rdquo; ... </span><br style="font-family: monospace;"><br>then the local
+&nbsp;mrun -d&nbsp; test -r xy# ... </span><br style="font-family: monospace;"><br>then the local
 file <tt><font style="font-size: 10pt;" size="2">DATA_2D_XY_NETCDF</font></tt>
 is copied to the permanent file <tt><font style="font-size: 10pt;" size="2">~/test/OUTPUT/test/test_xy.nc</font>
@@ -229,5 +232,5 @@
 which requires an additional file connection statement<br><br><span style="font-family: monospace;">&nbsp;&nbsp;
 DATA_2D_XY_AV_NETCDF out:loc:tr&nbsp; xy#&nbsp;
-~/$fname/OUTPUT/$fname&nbsp; _xy_av nc&nbsp;&nbsp; .</span><br></p></li><li>With
+~/$fname/OUTPUT/$fname&nbsp; _xy_av nc&nbsp;&nbsp; .</span><br></p></li><li>Using <a href="chapter_4.2.html#netcdf_data_format">netcdf_data_format</a> &gt; <span style="font-style: italic;">2</span> or <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a> = <span style="font-style: italic;">.F.</span> generates a single NetCDF file containing data from all propcessors. However, 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>
 = <i>.T.</i>
@@ -293,5 +296,5 @@
 example program.<br><br><br></li><li>By
 default, each PALM job creates its own NetCDF files. If permanent files
-with respective filenames are already existing then new files with
+with respective filenames are already existing, then new files with
 higher cycle numbers will be created. However, in case of a job chain,
 it is possible to extend the NetCDF datasets created by the initial
