Changes between Version 19 and Version 20 of doc/app/errmsg


Ignore:
Timestamp:
Sep 14, 2010 8:25:10 AM (14 years ago)
Author:
heinze
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/errmsg

    v19 v20  
    168168||PA0144   ||#1 k=... j=... i=... e_s=... e_a=... t_int=... d_radius=... delta_r=... particle_radius=...   ||  ||
    169169||PA0145   ||collision_efficiency out of range: ...   ||  ||
    170 ||PA0146   ||maximum_number_of_particles needs to be increased but this is not allowed with netcdf_data_format < 3  ||netCDF output is switched on ([../d3par#data_output_format] = '' 'netcdf' '') and a netCDF3 format is used ([../d3par#data_output_format] < 3).  ||
     170||PA0146   ||maximum_number_of_particles needs to be increased but this is not allowed with netcdf_data_format < 3  ||netCDF output is switched on ([../d3par#data_output_format data_output_format] = '' 'netcdf' '') and a netCDF3 format is used ([../d3par#netcdf_data_format  netcdf_data_format ] < 3). \\\\ If output of particle data is switched on (see [../d3par#dt_write_particle_data dt_write_particle_data]), the size of the particle array, given on each processor by [../d3par#maximum_number_of_particles maximum_number_of_particles], 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 [../d3par#dt_prel dt_prel]).\\\\This problem can be avoided by using the netCDF4 data format ([../d3par#netcdf_data_format netcdf_data_format] > 2), which allows more than one unlimited dimension.\\\\Alternatively, [../d3par#maximum_number_of_particles maximum_number_of_particles] can be given a sufficiently large value.  ||
    171171||PA0147   ||  ||  ||
    172172||PA0148   ||  ||  ||