Home

Context Navigation

errmsg

Timestamp:: Mar 26, 2018 9:44:17 PM (7 years ago)
Author:: maronga
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

doc/app/errmsg

-                      v499
+                      v500
 }}}
 ||='''Message identifier '''  =||='''Error message'''  =||='''Explanation'''  =||
 ||[=#PA0001 PA0001]   ||manual restart settings requires file activation string "restart" || Values for parameters {{{dt_restart}}} or/and {{{restart_time}}} have been given in the {{{&d3par}}}-NAMELIST. This also requires to give the file activation string {{{"restart"}}} with palmbuild-option {{{-a}}}, because otherwise the restart files wouldn't be generated at the end of the PALM run. \\\\Repeat the run with {{{-a ".... restart"}}} or remove parameters {{{dt_restart}}} or/and {{{restart_time}}} from your NAMELIST-file. ||
+||[=#PA0001 PA0001]   ||manual restart settings requires file activation string "restart" || Values for parameters {{{dt_restart}}} or/and {{{restart_time}}} have been given in the {{{&runtime_parameters}}}-NAMELIST. This also requires to give the file activation string {{{"restart"}}} with palmbuild-option {{{-a}}}, because otherwise the restart files wouldn't be generated at the end of the PALM run. \\\\Repeat the run with {{{-a ".... restart"}}} or remove parameters {{{dt_restart}}} or/and {{{restart_time}}} from your NAMELIST-file. ||
 ||[=#PA0002 PA0002]   ||illegal coupling mode: ...   || This message is related to the atmosphere-ocean coupling implemented in PALM. Internally, the variable {{{coupling_mode}}} defines the coupling setup used for the current respective model run. It may have one of the values "{{{atmosphere_to_ocean}}}" (atmospheric part of a coupled run), "{{{ocean_to_atmosphere}}} (ocean part of a coupled run), "{{{precursor_atmos}}}" (a precursor atmosphere run), "{{{precursor_ocean}}}" (a precursor ocean run),  or "{{{uncoupled}}}" (atmosphere or ocean run without any intended coupling). This error message means that the initialization of the coupling did fail because {{{coupling_mode}}} has a value different from the ones mentioned before. Possible reasons might be trying a coupling between two atmosphere runs (or two ocean runs), or problems with the {{{palmrun}}} script. ||
 ||[=#PA0003 PA0003]   ||dt_coupling is not set but required for coupling mode "..."   || This error appears if the temporal interval for the data exchange [../d3par#dt_coupling dt_coupling] is not explicitly set in case of runs with [../../app/examples/coupled coupled models] (e.g. atmosphere - ocean). ||
 …
 ||[=#PA0039 PA0039]   ||  Using synthetic turbulence generator in combination with turbulent_inflow = .T. is not allowed || A turbulent inflow can only be generated by either the synthetic turbulence generator or the turbulence recycling method. Using both at the same time is impossible. ||
 ||[=#PA0040 PA0040]   ||LWC is not conserved during collision! LWC after condensation: ... LWC after collision: ... || LWC means liquid water content. This should not happen. Please write a [https://palm.muk.uni-hannover.de/trac/newticket ticket].  ||
 ||[=#PA0041 PA0041]   ||plant_canopy = .TRUE. requires a non-zero drag coefficient, given value is canopy_drag_coeff = 0.0   || When simulating a plant canopy, a non-zero [../canpar#canopy_drag_coeff canopy_drag_coeff] must be set in the parameter file under NAMELIST {{{&canopy_par}}}. The [/wiki/doc/app/canpar canopy model] in PALM adds an additional sink/source terms to the momentum equations, the prognostic equation for temperature, and the subgrid scale turbulent kinetic energy equation. In case of [../inipar#humidity humidity] = ''.TRUE.'' or [../inipar#passive_scalar passive_scalar] = ''.TRUE.'', an additional source/sink term is added to the prognostic equation of the respective scalar.\\ If [../canpar#canopy_drag_coeff canopy_drag_coeff] = 0.0, the additional terms equal zero and there would be no effect on the flow.  ||
+||[=#PA0041 PA0041]   ||plant_canopy = .TRUE. requires a non-zero drag coefficient, given value is canopy_drag_coeff = 0.0   || When simulating a plant canopy, a non-zero [../canpar#canopy_drag_coeff canopy_drag_coeff] must be set in the parameter file under NAMELIST {{{&plant_canopy_parameters}}}. The [/wiki/doc/app/canpar canopy model] in PALM adds an additional sink/source terms to the momentum equations, the prognostic equation for temperature, and the subgrid scale turbulent kinetic energy equation. In case of [../inipar#humidity humidity] = ''.TRUE.'' or [../inipar#passive_scalar passive_scalar] = ''.TRUE.'', an additional source/sink term is added to the prognostic equation of the respective scalar.\\ If [../canpar#canopy_drag_coeff canopy_drag_coeff] = 0.0, the additional terms equal zero and there would be no effect on the flow.  ||
 ||[=#PA0042 PA0042]   ||use_top_fluxes must be .TRUE. in ocean mode   ||In [../inipar#ocean ocean] mode, fluxes at the water surface must be prescribed as driving boundary conditions. In atmosphere-ocean coupled runs, these fluxes are provided by the atmosphere run. ||
 ||[=#PA0043 PA0043]   ||ABS( alpha_surface = ... ) must be< 90.0   ||Upright surfaces are not allowed in case of sloping surfaces. ||
 …
 ||[=#PA0220 PA0220]   ||unknown boundary condition bc_par_ns = "..."   || See parameter [../parpar#bc_par_ns bc_par_ns] for allowed values, and appropriately correct your parameter file.  ||
 ||[=#PA0221 PA0221]   ||number of PEs of the prescribed topology (...) does not match the number of PEs available to the job (...)   ||In case that the number of PEs along the x- and y-direction of the virtual processor grid is set via [../d3par#npex npex] and [../d3par#npey npey], the product npey*npex has to match exactly the total number of processors which is assigned by the '''palmrun'''-option -X. ||
 ||[=#PA0222 PA0222]   ||if the processor topology is prescribed by the user, both values of "npex" and "npey" must be given in the NAMELIST-parameter file   || In case that only one number of processors along x- or y- direction [../d3par#npex npex] or [../d3par#npey npey] is set in the [../d3par#pgrid &d3par-Namelist], the remaining, so far not assigned, number of processors has to be set, too.   ||
+||[=#PA0222 PA0222]   ||if the processor topology is prescribed by the user, both values of "npex" and "npey" must be given in the NAMELIST-parameter file   || In case that only one number of processors along x- or y- direction [../d3par#npex npex] or [../d3par#npey npey] is set in the [../d3par#pgrid &runtime_parameters-Namelist], the remaining, so far not assigned, number of processors has to be set, too.   ||
 ||[=#PA0223 PA0223]   ||errors in \$nestpar   ||An unvalid variable name or value has been given in the nestpar-NAMELIST. Carefully check your nestpar-NAMELIST and compare with the parameters given and explained in the [wiki:doc/app/nestpar Nesting]-section of the model steering parameters.  ||
 ||[=#PA0224 PA0224]   ||   || message number is unused ||
 …
 ||[=#PA0269 PA0269]   ||netCDF file for particle time series from previous run found. This file will be extended.   || ** ||
 ||[=#PA0270 PA0270]   ||mode "..." not supported   || ** ||
 ||[=#PA0271 PA0271]   ||errors in &inipar or no &inipar-namelist found (CRAY-machines only)   ||One possible explanation: An old, meanwhile modified variable has been used in &inipar (e.g. ws_vertical_gradient (old) instead of [../inipar#subs_vertical_gradient subs_vertical_gradient] (new)). Please carefully check your inipar-NAMELIST and compare parameters and their values with those given and explained in the [wiki:doc/app/inipar initialization]-section of the model steering parameters.  ||
 ||[=#PA0272 PA0272]   ||no &inipar-namelist found   || Your parameter file must contain an &inipar-namelist. Parameters given in this namelist are required for model steering. Please take a look at this [/wiki/doc/tut/tec/control example parameter file] and appropriately correct your parameter file. One possible error might be a typo in the NAMELIST name, e.g. ''inpar'' instead of ''inipar''. ||
 ||[=#PA0273 PA0273]   ||no value or wrong value given for nx: nx=...   || See parameter [../inipar#nx nx] for allowed values, and check the &inipar-namelist in your parameter file. ||
 ||[=#PA0274 PA0274]   ||no value or wrong value given for ny: ny=...   || See parameter [../inipar#ny ny] for allowed values, and check the &inipar-namelist in your parameter file. ||
 ||[=#PA0275 PA0275]   ||no value or wrong value given for nz: nz=...   || See parameter [../inipar#nz nz] for allowed values, and check the &inipar-namelist in your parameter file. ||
+||[=#PA0271 PA0271]   ||errors in &initialization_parameters or no &initialization_parameters-namelist found (CRAY-machines only)   ||One possible explanation: An old, meanwhile modified variable has been used in &initialization_parameters (e.g. ws_vertical_gradient (old) instead of [../inipar#subs_vertical_gradient subs_vertical_gradient] (new)). Please carefully check your inipar-NAMELIST and compare parameters and their values with those given and explained in the [wiki:doc/app/inipar initialization]-section of the model steering parameters.  ||
+||[=#PA0272 PA0272]   ||no &initialization_parameters-namelist found   || Your parameter file must contain an &initialization_parameters-namelist. Parameters given in this namelist are required for model steering. Please take a look at this [/wiki/doc/tut/tec/control example parameter file] and appropriately correct your parameter file. One possible error might be a typo in the NAMELIST name, e.g. ''inpar'' instead of ''inipar''. ||
+||[=#PA0273 PA0273]   ||no value or wrong value given for nx: nx=...   || See parameter [../inipar#nx nx] for allowed values, and check the &initialization_parameters-namelist in your parameter file. ||
+||[=#PA0274 PA0274]   ||no value or wrong value given for ny: ny=...   || See parameter [../inipar#ny ny] for allowed values, and check the &initialization_parameters-namelist in your parameter file. ||
+||[=#PA0275 PA0275]   ||no value or wrong value given for nz: nz=...   || See parameter [../inipar#nz nz] for allowed values, and check the &initialization_parameters-namelist in your parameter file. ||
 ||[=#PA0276 PA0276]   ||local file ENVPAR not found, some variables for steering may not be properly set   || Some model steering parameters are passed to PALM through a namelist {{{&envpar}}} which is stored in local file {{{ENVPAR}}}. This file is created by the script [source:palm/trunk/SCRIPTS/palmrun palmrun] which can be used to start model runs. This message appears, if {{{ENVPAR}}} could not be found because it was not created by palmrun. Check if you changed anything in the script.  ||
 ||[=#PA0277 PA0277]   ||errors in local file ENVPAR some variables for steering may not be properly set   || The namelist {{{&envpar}}} expects certain model steering parameters (see [source:palm/trunk/SOURCE/parin.f90 parin.f90]). Some of these parameters have not been properly set or are missing entirely. This should only happen if (1) you didn't use palmrun to start your run, (2) you used an old version of palmrun that is not compatible with your model version anymore (then please update) or (3) you changed palmrun manually and set some parameters of the {{{&envpar}}} namelist incorrectly. (Also see [#PA0276 PA0276])  ||