Changes between Version 784 and Version 785 of doc/app/errmsg

Timestamp:

Jan 6, 2022 12:40:32 PM (3 years ago)

Author:

raasch

Comment:

--

doc/app/errmsg

@@ -350 +350 @@
 ||[=#PA0308 PA0308]   ||statistic regions on restart data file differ from the current run: statistic regions on file = "..." statistic regions from run = "..." statistic data may be lost!  || This message is a warning, the run will continue nonetheless. This will only happen in case the statistic [../initialization_parameters#statistic_regions regions] were changed from precursor to main run. See documentation of [../examples/turbinf tubulent inflow] for detailed information on the use of restart data for precursor runs. ||
 ||[=#PA0309 PA0309]   ||inflow profiles not temporally averaged. Averaging will be done now using ... samples.   || The [../examples/turbinf tubulent inflow] method needs time averaged inflow profiles. This warning occurs if the output of time averaged profiles ([../runtime_parameters#skip_time_dopr skip_time_dopr] + [../runtime_parameters#dt_dopr  dt_dopr]) is not an integral divisor of the [../runtime_parameters#end_time end_time] which is specified for the precursor run or if [../runtime_parameters#skip_time_dopr skip_time_dopr] + [../runtime_parameters#dt_dopr  dt_dopr] is larger than this [../runtime_parameters#end_time end_time]. ||
-||[=#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]) ||
+||[=#PA0310 PA0310]   ||unused   || ||
 ||[=#PA0311 PA0311]   ||number of gridpoints along x or/and y contain illegal factors only factors 2, 3, 5 are allowed   ||In case that [../initialization_parameters#fft_method fft_method]='temperton-algorithm', the number of horizontal grid points ([../initialization_parameters#nx nx]+1, [../initialization_parameters#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 [../initialization_parameters#fft_method fft_method].  ||
 ||[=#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 [../runtime_parameters#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 [../runtime_parameters#dt_max dt_max] in the NAMELIST file. Moreover, this error message may indicate for unrealistic settings of e.g. [../initialization_parameters#bc boundary conditions] or other NAMELIST parameters. For very small vertical grid spacing [../initialization_parameters#dz dz] this error might also occur if [../initialization_parameters#roughness_length roughness_length] >= [../initialization_parameters#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. In case the [../land_surface_parameters land-surface model] or the [../urban_surface_parameters building-surface model] is employed, surface temperatures might had become unstable during the time-integration. Please check for possibly mis-represented settings in your static input file. List to be continued.||