Changes between Version 492 and Version 493 of doc/app/errmsg

Timestamp:

Mar 16, 2018 2:16:56 PM (7 years ago)

Author:

Giersch

Comment:

--

doc/app/errmsg

@@ -694 +694 @@
 ||[=#PA0471 PA0471]   ||  number of soil layers (...) does not match to the number of layers specified in soil_temperature (...) || For each soil layer an initial soil temperature must be prescribed (see [wiki:doc/app/lsmpar#soil_temperature soil_temperature]). ||
 ||[=#PA0472 PA0472]   || deep_soil_temperature is not set but must be /= 9999999.9 || Since r2729 the deep soil temperature is no longer part of the soil_temperature array and must be specific separately. The deep soil temperature serves as bottom boundary condition for heat diffusion in the soil model. Note that there is no analogous value for soil moisture as the bottom of the soil can either be set to bedrock (water accumulates) or free drainage (water is lost). ||
-||[=#PA0473 PA0473]   ||  ||  ||
+||[=#PA0473 PA0473]   || Vertical grid stretching is not allowed for complex_terrain = .T. ||  ||
 ||[=#PA0474 PA0474]   ||pavement_type = 0 (user_defined) requires setting of pavement_depth_level /= 0  ||When a user-defined pavement is prescribed, a depth must be asigned that determines how deep the pavement extends into the ground. The [../lsmpar#pavement_heat_capacity pavement heat capacity] and  [../lsmpar##pavement_heat_cond pavement heat conductivty] are then asigned to all those levels. ||
 ||[=#PA0475 PA0475]   ||  particle violated cfl criterion || this is that some of your particles moves too fast. ||
@@ -703 +703 @@
 ||[=#PA0480 PA0480]   ||  RMA window too small on child ||  ||
 ||[=#PA0481 PA0481]   ||  RMA window too small on parent ||  ||
+||[=#PA0482 PA0482]   ||  Version of binary SVF file "..." does not match the version of model "..." ||  ||
+||[=#PA0483 PA0483]   ||  Wrong number of SVF or CSF ||  ||
+||[=#PA0484 PA0484]   ||  Wrong structure of binary svf file ||  ||
 
 ||[=#UI0001 UI0001]   ||unknown location "..."   ||The location 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'.  ||
@@ -715 +718 @@
 ||[=#UI0010 UI0010]   ||Spectra of ... can not be calculated  || No CASE statement defined for '...' ||
 ||[=#UI0011 UI0011]   ||Spectra of ... are not defined   || No CASE statement defined for '...' ||
-||[=#UI0012 UI0012]   ||unknown variable named "..." found in data from prior run on PE   || During the initial run, a variable was written to [../iofiles#BINOUT BINOUT], that is not recognized during read-in of the restart run. Note that user variables have to be written during [../userint/int#user_last_actions user_last_actions] (not to the part of [../iofiles#BINOUT BINOUT] where standard output is written). It has to be read accordingly in [../userint/int#user_read_restart_data user_read_restart_data]. Also see: [../userint/output#part_3 user output]. ||
 ||[=#NC NC!**!**]   ||!**!** contains numbers in the range from 1-521   ||Internally, PALM calls the netCDF function {{{NF90_STRERROR}}} which returns an error message string provided by netCDF. Hence, no exact assignment between PALM error number and netCDF error string can be given. Most of the netCDF errors should never appear if the default code is used. The following list gives errors which may be caused by wrong steering or errors due to problems in the user interface. ||
 ||[=#NC0079 NC0079]   ||String match to name in use ||A netCDF variable name has been used twice. Possible reasons: a variable in the parameter file has been listed twice (e.g. in [../d3par#data_output data_output]) or a variable name that has been defined in the user interface is already used by PALM. ||