Changeset 519 for palm/trunk/DOC/app
- Timestamp:
- Mar 19, 2010 5:30:02 AM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
palm/trunk/DOC/app/appendix_a.html
r493 r519 1 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2 2 <html><head> 3 3 4 4 5 … … 1876 1877 <td style="vertical-align: top;"> 1877 1878 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 < 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>< <span style="font-style: italic;">3</span>).<br> 1881 <br> 1882 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>, 1883 is not allowed to increase during the run, when the NetCDF3 data format 1884 is used, because NetCDF3 allows only one unlimited dimension, which is 1885 the time dimension. Anyhow, PALM tries to increase the size of the 1886 particle array, if the number of particles in a subdomain becomes 1887 larger than the size of this array. This may happen because of a flow 1888 convergence or because new sets of particles are released (see <a href="chapter_4.2.html#dt_prel">dt_prel</a>).<br> 1889 <br> 1890 This problem can be avoided by using the NetCDF4 data format (<a href="chapter_4.2.html#netcdf_data_format">netcdf_data_format</a> > <span style="font-style: italic;">2</span>), which allows more than one unlimited dimension.<br> 1891 <br> 1892 Alternatively, <a href="chapter_4.2.html#maximum_number_of_particles">maximum_number_of_particles</a> can be given a sufficiently large value.<br> 1880 1893 </td> 1881 1894 … … 1889 1902 <td style="vertical-align: top;"> 1890 1903 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 < 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> < <span style="font-style: italic;">3</span>).<br> 1906 1907 <br> 1908 1909 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>, 1910 is not allowed to increase during the run, when the NetCDF3 data format 1911 is used, because NetCDF3 allows only one unlimited dimension, which is 1912 the time dimension. Anyhow, PALM tries to increase the size of the 1913 particle tail array, if the number of particle tails in a subdomain becomes 1914 larger than the size of this array. This may happen because of a flow 1915 convergence 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 1919 This problem can be avoided by using the NetCDF4 data format (<a href="chapter_4.2.html#netcdf_data_format">netcdf_data_format</a> > <span style="font-style: italic;">2</span>), which allows more than one unlimited dimension.<br> 1920 1921 <br> 1922 1923 Alternatively, <a href="chapter_4.2.html#maximum_number_of_tails">maximum_number_of_tails</a> can be given a sufficiently large value. 1893 1924 </td> 1894 1925
Note: See TracChangeset
for help on using the changeset viewer.