Index: palm/trunk/DOC/app/appendix_a.html
===================================================================
--- palm/trunk/DOC/app/appendix_a.html	(revision 493)
+++ palm/trunk/DOC/app/appendix_a.html	(revision 519)
@@ -1,4 +1,5 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html><head>
+
 
 
@@ -1876,6 +1877,18 @@
          <td style="vertical-align: top;">
       maximum_number_of_particles needs to be increased 
-                       but this is not allowed with NetCDF output switched on
-      </td><td style="vertical-align: top;"><br>
+                       but this is not allowed with netcdf_data_format &lt; 3
+      </td><td style="vertical-align: top;">NetCDF output is switched on (<a href="chapter_4.2.html#data_output_format">data_output_format</a> = <span style="font-style: italic;">'netcdf'</span>) and a NetCDF3 format is used (<a href="chapter_4.2.html#netcdf_data_format">netcdf_data_format </a>&lt; <span style="font-style: italic;">3</span>).<br>
+      <br>
+If output of particle data is switched on (see <a href="chapter_4.2.html#dt_write_particle_data">dt_write_particle_data</a>), the size of the particle array, given on each processor by <a href="chapter_4.2.html#maximum_number_of_particles">maximum_number_of_particles</a>,
+is not allowed to increase during the run, when the NetCDF3 data format
+is used, because NetCDF3 allows only one unlimited dimension, which is
+the time dimension. Anyhow, PALM tries to increase the size of the
+particle array, if the number of particles in a subdomain becomes
+larger than the size of this array. This may happen because of a flow
+convergence or because new sets of particles are released (see <a href="chapter_4.2.html#dt_prel">dt_prel</a>).<br>
+      <br>
+This problem can be avoided by using the NetCDF4 data format (<a href="chapter_4.2.html#netcdf_data_format">netcdf_data_format</a> &gt; <span style="font-style: italic;">2</span>), which allows more than one unlimited dimension.<br>
+      <br>
+Alternatively, <a href="chapter_4.2.html#maximum_number_of_particles">maximum_number_of_particles</a> can be given a sufficiently large value.<br>
       </td>
 
@@ -1889,6 +1902,24 @@
          <td style="vertical-align: top;">
       maximum_number_of_tails needs to be increased 
-                       but this is not allowed with NetCDF output switched on
-      </td><td style="vertical-align: top;"><br>
+                       but this is not allowed with netcdf_data_format &lt; 3
+      </td><td style="vertical-align: top;">NetCDF output is switched on (<a href="chapter_4.2.html#data_output_format">data_output_format</a> = <span style="font-style: italic;">'netcdf'</span>) and a NetCDF3 format is used (<a href="chapter_4.2.html#netcdf_data_format">netcdf_data_format</a> &lt; <span style="font-style: italic;">3</span>).<br>
+
+      <br>
+
+If output of particle data is switched on (see <a href="chapter_4.2.html#dt_write_particle_data">dt_write_particle_data</a>), the size of the particle tail array, given on each processor by <a href="chapter_4.2.html#maximum_number_of_tails">maximum_number_of_tails</a>,
+is not allowed to increase during the run, when the NetCDF3 data format
+is used, because NetCDF3 allows only one unlimited dimension, which is
+the time dimension. Anyhow, PALM tries to increase the size of the
+particle tail array, if the number of particle tails in a subdomain becomes
+larger than the size of this array. This may happen because of a flow
+convergence or because new sets of particles are released (see <a href="chapter_4.2.html#dt_prel">dt_prel</a>).<br>
+
+      <br>
+
+This problem can be avoided by using the NetCDF4 data format (<a href="chapter_4.2.html#netcdf_data_format">netcdf_data_format</a> &gt; <span style="font-style: italic;">2</span>), which allows more than one unlimited dimension.<br>
+
+      <br>
+
+Alternatively, <a href="chapter_4.2.html#maximum_number_of_tails">maximum_number_of_tails</a> can be given a sufficiently large value.
       </td>
 
