Changes between Version 274 and Version 275 of doc/app/errmsg

Timestamp:

Nov 8, 2016 3:50:59 PM (9 years ago)

Author:

gronemeier

Comment:

--

doc/app/errmsg

@@ -61 +61 @@
 ||[=#PA0036 PA0036]   ||humidity = .TRUE. and sloping_surface = .TRUE. are not allowed simultaneously   || If [../inipar#alpha_surface alpha_surface] is set to a non-zero value in order to use an inclined surface, the parameter sloping_surface is internally set ''.TRUE.''. I.e., in the case of [../inipar#alpha_surface alpha_surface] /= 0.0 the simultaneous use of [../inipar#humidity humidity] = ''.TRUE.'' is not allowed. ||
 ||[=#PA0037 PA0037]   ||negative weighting factor: ...  || The weighting factor of the cloud droplets is recalculated during the calculation of the droplet growth due to collision and coalescence. This error appears if the newly calculated value for the weighting factor is negative and the '' 'hall' '' or '' 'wang' '' collision kernel is used (see [../parpar#collision_kernel collision_kernel]). It may be caused by illegal values of the collision kernel. Please submit a [/newticket trouble ticket] if you have run into this error. ||
-||[=#PA0038 PA0038]   ||          || not used ||
+||[=#PA0038 PA0038]   || turbulent_outflow = .T. requires bc_lr = "dirichlet/radiation" || When using the turbulent outflow method, non-cyclic boundary condition along the x direction must be used. See also [../inipar#turbulent_outflow turbulent_outflow] ||
 ||[=#PA0039 PA0039]   ||negative weighting factor: ...  || The weighting factor of the cloud droplets is recalculated during the calculation of the droplet growth due to collision and coalescence. This error appears if the newly calculated value for the weighting factor is negative and the '' 'palm' '' collision kernel is used (see [../parpar#collision_kernel collision_kernel]). It may be caused by illegal values of the collision kernel. Please submit a [/newticket trouble ticket] if you have run into this error. ||
 ||[=#PA0040 PA0040]   ||LWC is not conserved during collision! LWC after condensation: ... LWC after collision: ... || This should not happen. Please write a [https://palm.muk.uni-hannover.de/trac/newticket ticket].  ||
@@ -185 +185 @@
 ||[=#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.   ||
-||[=#PA0145 PA0145]   ||   ||message number is unused  ||
+||[=#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.  ||
 ||[=#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.  ||