Changes between Version 558 and Version 559 of doc/app/errmsg


Ignore:
Timestamp:
Jul 16, 2018 6:23:30 AM (7 years ago)
Author:
raasch
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/errmsg

    v558 v559  
    353353||[=#PA0310 PA0310]   ||remote model "..." terminated with terminate_coupled_remote = ... local model "..." has terminate_coupled = ...   ||The remote model in a coupled run has been terminated. The reason for the termination is provided by {{{terminate_coupled}}}.\\\\Termination reasons:\\1 model was terminated (unknown reason)\\2 time step has reached minimum limit (see [#PA0312 PA0312])\\3 run will be terminated because it is running out of job cpu limit remaining time (see [#PA0163 PA0163])\\4 run will be terminated due to user settings of {{{dt_restart}}} (see [#PA0164 PA0164])\\5 run will be terminated due to user settings of {{{restart_time}}} (see [#PA0164 PA0164])\\6 unscheduled termination was forced by the user (see [#PA0398 PA0398]) ||
    354354||[=#PA0311 PA0311]   ||number of gridpoints along x or/and y contain illegal factors only factors 2, 3, 5 are allowed   ||In case that [../inipar#fft_method fft_method]='temperton-algorithm', the number of horizontal grid points ([../inipar#nx nx]+1, [../inipar#ny ny]+1) must be composed of prime factors 2,3 and 5. Higher prime factors such as 7 are not allowed. Please ensure that these restrictions are fulfilled or use 'singleton-algorithm' as [../inipar#fft_method fft_method].  ||
    355 ||[=#PA0312 PA0312]   ||Time step has reached minimum limit. \\dt = ... s Simulation is terminated.\\old_dt = ... s\\dt_u = ... s\\dt_v = ... s\\dt_w = ... s\\dt_diff = ... s\\u_max = ... m/s k=... j=... i=...\\v_max = ... m/s k=... j=... i=...\\w_max = ... m/s k=... j=... i=...   ||The time step is determined according to the CFL criterion to assure a stable numerical solution. This error message means that the required minimum time step, determined from the three velocity components, is several orders of magnitude smaller than [../d3par#dt_max dt_max]. Due to the large number of complex reasons it should be noted that this list is not complete, but it is intended to give general hints how to proceed in case of this error message. First, check for a unrealistic value of [../d3par#dt_max dt_max] in the NAMELIST file. Moreover, this error message may indicate for unrealistic settings of e.g. [../inipar#bc boundary conditions] or other NAMELIST parameters. For very small vertical grid spacing [../inipar#dz dz] this error might also occur if [../inipar#roughness_length roughness_length] >= [../inipar#dz dz]. Please also check if this error appears if you run without USERCODE. To compile and run the PALM and USERCODE with DEBUG-options might also give sometimes valuable hints.
     355||[=#PA0312 PA0312]   ||Time step has reached minimum limit. \\dt = ... s Simulation is terminated.\\old_dt = ... s\\dt_u = ... s\\dt_v = ... s\\dt_w = ... s\\dt_diff = ... s\\u_max = ... m/s k=... j=... i=...\\v_max = ... m/s k=... j=... i=...\\w_max = ... m/s k=... j=... i=...   ||The time step is determined according to the CFL criterion to assure a stable numerical solution. This error message means that the required minimum time step, determined from the three velocity components, is several orders of magnitude smaller than [../d3par#dt_max dt_max], or, in other words, that at least one of the velocity components got too large. Due to the large number of complex reasons it should be noted that this list is not complete, but it is intended to give general hints how to proceed in case of this error message. First, check for a unrealistic value of [../d3par#dt_max dt_max] in the NAMELIST file. Moreover, this error message may indicate for unrealistic settings of e.g. [../inipar#bc boundary conditions] or other NAMELIST parameters. For very small vertical grid spacing [../inipar#dz dz] this error might also occur if [../inipar#roughness_length roughness_length] >= [../inipar#dz dz]. Please also check if this error appears if you run without USERCODE. To compile and run the PALM and USERCODE with DEBUG-options might also give sometimes valuable hints.
    356356To be continued.||
    357357||[=#PA0313 PA0313]   ||illegal value for parameter particle_color: ...   || The parameter [../dvrpar#particle_color particle_color] allows to bind the displayed particle color to certain flow quantities. Possible values for this parameter are '' 'absuv' '', '' 'pt*' '' or '' 'z' ''. The default value is '' 'none' ''. Other values for [../dvrpar#particle_color particle_color] are not enabled. For detailed information see [../dvrpar#particle_color particle_color]. ||