Changes between Version 695 and Version 696 of doc/app/errmsg

Timestamp:

May 16, 2020 1:15:28 PM (5 years ago)

Author:

raasch

Comment:

--

doc/app/errmsg

@@ -914 +914 @@
 ||[=#PA0718 PA0718]  || boundary conditions bc_cs_n and bc_cs_s must both be cyclic or non-cyclic. || See parameter descriptions under [wiki:doc/app/chemistry_parameters#bc_cs_n bc_cs_n] and [wiki:doc/app/chemistry_parameters#bc_cs_s bc_cs_s], and appropriately correct your parameter file. ||
 ||[=#PA0719 PA0719]  || ql must be larger than zero. || values smaller than zero can occur if the time-stpe is not appropiate.  ||
+||[=#PA0720 PA0720]  || illegal action "..." for opening restart files || Only actions "read" or "write" are allowed. This is a PALM internall conding problem. Please contact the PALM developers / submit a trouble ticket. ||
+||[=#PA0721 PA0721]  || error opening restart file for posix I/O. || A serial run (on one core) was unable to open the restart file for reading or writing. In case of reading check your job log if the restart file has been copied to the temporary working directory before execution of PALM. ||
+||[=#PA0722 PA0722]  || CHARACTER/INTEGER/REAL variable/array "..." not found in restart file. || The indicated variable was not found in the restart file. If you are doing restart I/O in your user-interface, please check that input- and output variables exactly match. ||
+||[=#PA0723 PA0723]  || 2d-INTEGER array "..." to be read from restart file is defined with illegal dimensions in the PALM code. || This problem may appear in your user-interface, if you try to write/read 2d-INTEGER arrays with ghost boundaries to/from the restart file. 2d-INTEGER arrays in restart files are not allowed to have ghost boundaries so far. ||
 ||[=#UI0001 UI0001]   ||unknown location "..."   ||The location of the CALL of user_actions has to be one of 'before_timestep', 'after_integration', 'after_timestep', 'u_tendency' 'v_tendency', 'w_tendency', 'pt_tendency', 'sa_tendency', 'e_tendency', 'q_tendency', 's_tendency'. The location of the CALL of user_actions_ij has to be one of 'u_tendency' 'v_tendency', 'w_tendency', 'pt_tendency', 'sa_tendency', 'e_tendency', 'q_tendency', 's_tendency'.   ||
 ||[=#UI0002 UI0002]   ||location "..." is not allowed to be called with parameters "i" and "j"   || The location of the CALL of user_actions_ij must not be 'before_timestep', 'after_integration', 'after_timestep' ||