Changes between Version 223 and Version 224 of doc/app/errmsg

Timestamp:

Apr 6, 2016 12:07:01 PM (9 years ago)

Author:

raasch

Comment:

--

doc/app/errmsg

@@ -183 +183 @@
 ||[=#PA0141 PA0141]   ||coupling requires PALM to be called with "mrun -K parallel"   ||Coupling is only allowed in parallel and not in serial mode.  ||
 ||[=#PA0142 PA0142]   ||absolute temperature < 0.0 at zu(...) = ...   || Within the PALM code (in {{{init_cloud_physics}}}), the hydrostatic pressure profile is calculated for a neutrally stratified temperature profile {{{t(z) = t_surface-g/c_p*z(k)}}}. If the height of the model domain is too large, the absolute temperature will become negative, which is not allowed. This error usually appears when both grid stretching is switched on and too many grid points along z are used. Try to reduce the number of grid points ([../inipar#nz nz]), switch on the grid stretching at larger heights (see [../inipar#dz_stretch_level dz_stretch_level]) or reduce the grid stretching factor ([../inipar#dz_stretch_factor dz_stretch_factor]).  ||
-||[=#PA0143 PA0143]   ||k=... j=... i=... ql_c=... part(...)%wf=... delta_r=...   ||  ||
-||[=#PA0144 PA0144]   ||!#1 k=... j=... i=... e_s=... e_a=... t_int=... d_radius=... delta_r=... particle_radius=...   || Theres ||
-||[=#PA0145 PA0145]   ||collision_efficiency out of range: ...   || Theres ||
+||[=#PA0143 PA0143]   ||   ||message number is unused  ||
+||[=#PA0144 PA0144]   ||   ||message number is unused  ||
+||[=#PA0145 PA0145]   ||   ||message number is unused  ||
 ||[=#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.  ||
 ||[=#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.  ||