Home

Context Navigation

errmsg

Timestamp:: Mar 20, 2014 4:44:36 PM (11 years ago)
Author:: heinze
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

doc/app/errmsg

-                      v170
+                      v171
 ||[=#PA0137 PA0137]   ||mixing_length_1d = "..." is unknown   ||See parameter [../inipar#mixing_length_1d mixing_length_1d] for allowed values, and appropriately correct your parameter file.  ||
 ||[=#PA0138 PA0138]   ||dissipation_1d = "..." is unknown   ||See parameter [../inipar#dissipation_1d dissipation_1d] for allowed values, and appropriately correct your parameter file.  ||
 ||[=#PA0139 PA0139]   ||termination_time_needed = ... must be > 30.0 on host ...   ||  ||
 ||[=#PA0140 PA0140]   ||termination_time_needed = ... should be >= 300.0 on host "..."   ||  ||
 ||[=#PA0141 PA0141]   ||coupling requires PALM to be called with "mrun -K parallel"   ||  ||
+||[=#PA0139 PA0139]   ||termination_time_needed = ... must be > 30.0 on host ...   ||Choose a [../d3par#termination_time_needed termination_time_needed] that is larger than 30 seconds because a specific amount of time is needed to finish the job for example for copying files, compiling, data output, ... .  ||
+||[=#PA0140 PA0140]   ||termination_time_needed = ... should be >= 300.0 on host "..."   ||Choose a [../d3par#termination_time_needed termination_time_needed] that is larger than 300 seconds because a specific amount of time is needed to finish the job for example for copying files, compiling, data output, ... . ||
+||[=#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=...   ||  ||
 …
 ||[=#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.  ||
 ||[=#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.  ||
 ||[=#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. ||
+||[=#PA0148 PA0148]   ||particle too fast. n = ...   ||  ||
 ||[=#PA0149 PA0149]   ||particle out of range: i=... j=... k=... nxl=... nxr=... nys=... nyn=... nzb=... nzt=...     ||  ||
 ||[=#PA0150 PA0150]   ||Both dp_external and conserve_volume_flow are .TRUE., but one of them must be .FALSE.   || Simultaneous use of an external pressure gradient forcing ([../inipar#dp_external dp_external] = .TRUE.) and [../inipar#conserve_volume_flow conserve_volume_flow] is not allowed. Please correct your parameter file appropriately. ||
 ||[=#PA0151 PA0151]   ||dp_level_b = ... is out of range   || [../inipar#dp_level_b dp_level_b] is outside of the vertical bounds of the model domain. Please check the prescribed value for [../inipar#dp_level_b dp_level_b] in your parameter file. ||
 ||[=#PA0152 PA0152]   ||dp_external is .TRUE. but dpdxy is zero, i.e. the external pressure gradient will not be applied   || If the flow forcing shall be accomplished by an external pressure gradient, i.e. [../inipar#dp_external dp_external] is .TRUE., [../inipar#dpdxy dpdxy] must be set to a non-zero value in your parameter file. ||
 ||[=#PA0153 PA0153]   ||dpdxy is nonzero but dp_external is .FALSE., i.e. the external pressure gradient will not be applied   || If the flow forcing shall be accomplished by an external pressure gradient, i.e. [../inipar#dpdxy dpdxy] is set to a non-zero value,  [../inipar#dp_external dp_external] = .TRUE. must be set in your parameter file. ||
 ||[=#PA0154 PA0154]   ||unknown conserve_volume_flow_mode: ...   || See parameter [../inipar#conserve_volume_flow_mode conserve_volume_flow_mode] for allowed values, and appropriately correct your parameter file.  ||
+||[=#PA0150 PA0150]   ||Both dp_external and conserve_volume_flow are .TRUE. but one of them must be .FALSE.   ||  ||
+||[=#PA0151 PA0151]   ||dp_level_b = ... is out of range   ||  ||
+||[=#PA0152 PA0152]   ||dp_external is .TRUE. but dpdxy is zero, i.e. the external pressure gradient will not be applied   ||  ||
+||[=#PA0153 PA0153]   ||dpdxy is nonzero but dp_external is .FALSE., i.e. the external pressure gradient will not be applied   ||  ||
+||[=#PA0154 PA0154]   ||unknown conserve_volume_flow_mode: ...   ||  ||
 ||[=#PA0155 PA0155]   ||noncyclic boundary conditions require conserve_volume_flow_mode = "inflow_profile"   || Micha ||
 ||[=#PA0156 PA0156]   ||noncyclic boundary conditions require conserve_volume_flow_mode = "inflow_profile"   || Micha ||
 …
 ||[=#PA0163 PA0163]   ||run will be terminated because it is running out of job cpu limit remaining time: ... s termination time needed: ... s   ||In case that [../d3par#restart_time restart_time] has not been set manually, PALM determines internally when a new restart run has to be carried out depending on the setting of [../d3par#termination_time_needed termination_time_needed]. Within the remaining time PALM will, for example, copy binary files for restart runs, archive or transfer result data. Have a look at [../runs Initialization and restart runs] for further information. ||
 ||[=#PA0164 PA0164]   ||run will be terminated due to user settings of restart_time / dt_restart new restart time is: ... s   ||A restart run is established by PALM due to the setting of  [../d3par#restart_time restart_time] and/or [../d3par#dt_restart dt_restart] and the new restart time is calculated. Have a look at [../runs Initialization and restart runs] for further information.  ||
 ||[=#PA0165 PA0165]   ||re-open of unit 14 is not verified. Please check results!   ||  ||
+||[=#PA0165 PA0165]   ||re-open of unit 14 is not verified. Please check results!   ||The file with unit number 14 contains the binaries  [http://palm.muk.uni-hannover.de/wiki/doc/app/iofiles BINOUT]. It was opened at least a second time by user specific settings. This is not verified, so check the results carefully.  ||
 ||[=#PA0166 PA0166]   ||re-opening of file-id ... is not allowed   ||  ||
 ||[=#PA0167 PA0167]   ||opening file-id ... not allowed for PE ...   ||  ||