Changes between Version 379 and Version 380 of doc/app/errmsg

Timestamp:

Jun 8, 2017 8:49:06 AM (8 years ago)

Author:

Giersch

Comment:

--

doc/app/errmsg

@@ -184 +184 @@
 ||[=#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=... ||This error occurs due to a spurious interaction of the production and depletion of supersaturations if the applied time step is too large. Please re-run the simulation with a shorter time step.  ||
-||[=#PA0144 PA0144]   ||  #1 k=... j=... i=... e_s=... e_a=... t_int=... delta_r=... particle_radius=... ||This error occurs if the droplet radius becomes negative. Please contact the developers if this error occurs.   ||
+||[=#PA0144 PA0144]   ||  #1 k=... j=... i=... e_s=... e_a=... t_int=... &delta_r=... particle_radius=... ||This error occurs if the droplet radius becomes negative. Please contact the developers if this error occurs and submit a new [/newticket trouble ticket].   ||
 ||[=#PA0145 PA0145]   || illegal value for outflow_source_plane:... || The position of the source plane for the turbulent outflow method is not given or outside the model domain. Assign a value inside the model domain: dx <= [../inipar#outflow_source_plane outflow_source_plane] <= nx*dx ||
 ||[=#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.  ||