Changes between Version 195 and Version 196 of doc/app/errmsg


Ignore:
Timestamp:
Feb 19, 2015 12:06:02 PM (10 years ago)
Author:
raasch
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/errmsg

    v195 v196  
    186186||[=#PA0144 PA0144]   ||!#1 k=... j=... i=... e_s=... e_a=... t_int=... d_radius=... delta_r=... particle_radius=...   || Theres ||
    187187||[=#PA0145 PA0145]   ||collision_efficiency out of range: ...   || Theres ||
    188 ||[=#PA0146 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.  ||
    189 ||[=#PA0147 PA0147]   ||maximum_number_of_tails 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_tails maximum_number_of_tails], 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.  ||
     188||[=#PA0146 PA0146]  ||maximum_number_of_particles needs to be increased but this is not allowed with netcdf_data_format < 3  ||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.  ||
     189||[=#PA0147 PA0147]   ||maximum_number_of_tails needs to be increased but this is not allowed with netcdf_data_format < 3   ||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_tails maximum_number_of_tails], 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.  ||
    190190||[=#PA0148 PA0148]   ||particle too fast. n = ...   || Particle has moved further than the length of one PE subdomain within on timestep. This is not allowed, since particles can only be transferred from one subdomain to the neighboring subdomain. Please check if subdomains are too small or velocities are unrealistically high. ||
    191191||[=#PA0149 PA0149]   ||particle out of range: i=... j=... k=... nxl=... nxr=... nys=... nyn=... nzb=... nzt=...     ||  ||