Changes between Version 403 and Version 404 of doc/app/errmsg

Timestamp:

Jun 8, 2017 1:02:34 PM (8 years ago)

Author:

sward

Comment:

--

doc/app/errmsg

@@ -342 +342 @@
 ||[=#PA0302 PA0302]   ||unknown variable named "..." found in data from prior run on PE ...   ||  ||
 ||[=#PA0303 PA0303]   ||nz not found in restart data file   ||  ||
-||[=#PA0304 PA0304]   ||mismatch concerning number of gridpoints along z nz on file = "..." nz from run = "..."   ||  ||
-||[=#PA0305 PA0305]   ||max_pr_user not found in restart data file   ||  ||
-||[=#PA0306 PA0306]   ||number of user profiles on restart data file differs from the current run \\max_pr_user on file = "..." \\max_pr_user from run = "..."   || These should match. See See [../runs run]-documentation and [../userpar#data_output_pr_user data_output_pr_user] ||
-||[=#PA0307 PA0307]   ||statistic_regions not found in restart data file   || See [../runs run]-documentation. ||
-||[=#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!  ||  ||
+||[=#PA0303 PA0303]   ||nz not found in restart data file   || nz is necessary for the main run to continue. This will happen if the [../inipar inipar] list was altered between precursor and main run. See documentation of [../examples/turbinf tubulent inflow] for detailed information on the use of restart data for precursor runs. Also check if you altered [../inipar#nz nz] between precursor and main run. ||
+||[=#PA0304 PA0304]   ||mismatch concerning number of gridpoints along z \\nz on file = "..." \\nz from run = "..."   || The main run must have the same number of grid points in z-direction as the precursor run. x- and y-directions may differ. See documentation of [../examples/turbinf tubulent inflow] for detailed information on the use of restart data for precursor runs. ||
+||[=#PA0305 PA0305]   ||max_pr_user not found in restart data file   || max_pr_user is necessary for the main run to continue. This will happen if the [../inipar inipar] list was altered between precursor and main run. See documentation of [../examples/turbinf tubulent inflow] for detailed information on the use of restart data for precursor runs. Also check if you altered [../userpar#data_output_pr_user data_output_pr_user] between precursor and main run. ||
+||[=#PA0306 PA0306]   ||number of user profiles on restart data file differs from the current run \\max_pr_user on file = "..." \\max_pr_user from run = "..."   || This message is informative, the run will continue nontheless. This will only happen in case the number of user [../userpar#data_output_pr_user profiles] was 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.  ||
+||[=#PA0307 PA0307]   ||statistic_regions not found in restart data file  || [../inipar#statistic_regions statistic_regions] are necessary for the main run to continue. This will happen if the [../inipar inipar] list was altered between precursor and main run. See documentation of [../examples/turbinf tubulent inflow] for detailed information on the use of restart data for precursor runs. ||
+||[=#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 informative, the run will continue nontheless. This will only happen in case the statistic [../inipar#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.   ||  ||
 ||[=#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]) ||