Ignore:
Timestamp:
Mar 19, 2010 5:30:02 AM (13 years ago)
Author:
raasch
Message:

NetCDF4 support for particle data; special character allowed for NetCDF variable names

File:
1 edited

Legend:

Unmodified
Added
Removed
  • palm/trunk/DOC/app/appendix_a.html

    r493 r519  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    22<html><head>
     3
    34
    45
     
    18761877         <td style="vertical-align: top;">
    18771878      maximum_number_of_particles needs to be increased
    1878                        but this is not allowed with NetCDF output switched on
    1879       </td><td style="vertical-align: top;"><br>
     1879                       but this is not allowed with netcdf_data_format &lt; 3
     1880      </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>
     1881      <br>
     1882If 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>,
     1883is not allowed to increase during the run, when the NetCDF3 data format
     1884is used, because NetCDF3 allows only one unlimited dimension, which is
     1885the time dimension. Anyhow, PALM tries to increase the size of the
     1886particle array, if the number of particles in a subdomain becomes
     1887larger than the size of this array. This may happen because of a flow
     1888convergence or because new sets of particles are released (see <a href="chapter_4.2.html#dt_prel">dt_prel</a>).<br>
     1889      <br>
     1890This 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>
     1891      <br>
     1892Alternatively, <a href="chapter_4.2.html#maximum_number_of_particles">maximum_number_of_particles</a> can be given a sufficiently large value.<br>
    18801893      </td>
    18811894
     
    18891902         <td style="vertical-align: top;">
    18901903      maximum_number_of_tails needs to be increased
    1891                        but this is not allowed with NetCDF output switched on
    1892       </td><td style="vertical-align: top;"><br>
     1904                       but this is not allowed with netcdf_data_format &lt; 3
     1905      </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>
     1906
     1907      <br>
     1908
     1909If 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>,
     1910is not allowed to increase during the run, when the NetCDF3 data format
     1911is used, because NetCDF3 allows only one unlimited dimension, which is
     1912the time dimension. Anyhow, PALM tries to increase the size of the
     1913particle tail array, if the number of particle tails in a subdomain becomes
     1914larger than the size of this array. This may happen because of a flow
     1915convergence or because new sets of particles are released (see <a href="chapter_4.2.html#dt_prel">dt_prel</a>).<br>
     1916
     1917      <br>
     1918
     1919This 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>
     1920
     1921      <br>
     1922
     1923Alternatively, <a href="chapter_4.2.html#maximum_number_of_tails">maximum_number_of_tails</a> can be given a sufficiently large value.
    18931924      </td>
    18941925
Note: See TracChangeset for help on using the changeset viewer.