Home


About us
PALM
PALM-4U
Installation
Release notes
Documentation
Getting Help
Gallery
Developers area

Changes between Version 478 and Version 479 of doc/app/errmsg


Ignore:
Timestamp:
Sep 8, 2017 8:16:49 AM (8 years ago)
Author:
raasch
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • doc/app/errmsg

    v478 v479  
    2424}}}
    2525||='''Message identifier '''  =||='''Error message'''  =||='''Explanation'''  =||
    26 ||[=#PA0001 PA0001]   ||  || message number is unused    ||
    27 ||[=#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 {{{mrun}}} script. ||
     26||[=#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. ||
     27||[=#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. ||
    2828||[=#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). ||
    2929||[=#PA0004 PA0004]   ||coupling mode "...": dt_coupling = ... is not equal to dt_coupling_remote = ...   || For coupled runs the temporal interval for the data exchange [../d3par#dt_coupling dt_coupling] must be explicitly set and must have the same value in both models ([../d3par#dt_coupling dt_coupling] has to be set in [../iofiles#PARIN PARIN] and [../iofiles#PARIN_O PARIN_O]). See also [../examples/coupled coupled runs]. ||
    … …  
    181181||[=#PA0139 PA0139]   ||'pavement_type = 0 (user_defined) requires setting of pavement_heat_conduct /= 9999999.9 ||In case of a user-defined pavement type, the heat conductivity of the pavement must be given ||
    182182||[=#PA0140 PA00140]   || invalid soil layer configuration found: dz_soil(k) <= 0.0)  ||By setting zs (the center of the soil layers), the depths of the individual layers is calculated by PALM itself. This errors points towards a misconfiguration because a soil level is set within an already established soil layer. ||
    183 ||[=#PA0141 PA0141]   ||coupling requires PALM to be called with "mrun -K parallel"   ||Coupling is only allowed in parallel and not in serial mode. ||
     183||[=#PA0141 PA0141]   ||coupling requires PALM to be compiled with cpp-option "-D__parallel"   ||Coupling is only allowed in parallel and not in serial mode. You have to compile PALM with the preprocessor option "-D__parallel". Add this option to the {{{%cpp_options}}} line in your configuration file {{{.palm.config....}}} ||
    184184||[=#PA0142 PA0142]   ||absolute temperature < 0.0 at zu(...) = ...   || Within the PALM code (in {{{init_cloud_physics}}}), the hydrostatic pressure profile is calculated for a neutrally stratified temperature profile {{{t(z) = t_surface-g/c_p*z(k)}}}. If the height of the model domain is too large, the absolute temperature will become negative, which is not allowed. This error usually appears when both grid stretching is switched on and too many grid points along z are used. Try to reduce the number of grid points ([../inipar#nz nz]), switch on the grid stretching at larger heights (see [../inipar#dz_stretch_level dz_stretch_level]) or reduce the grid stretching factor ([../inipar#dz_stretch_factor dz_stretch_factor]).  ||
    185185||[=#PA0143 PA0143]   ||  k=... j=... i=... ql_c=... part(...)%wf=... delta_r=... ||This error occurs due to a spurious interaction of the production and depletion of supersaturations if the applied time step is too large. Please re-run the simulation with a shorter time step.  ||
    … …  
    261261||[=#PA0219 PA0219]   ||unknown boundary condition bc_par_lr = "..."   || See parameter [../parpar#bc_par_lr bc_par_lr] for allowed values, and appropriately correct your parameter file.  ||
    262262||[=#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.  ||
    263 ||[=#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 '''mrun'''-option -X. ||
     263||[=#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. ||
    264264||[=#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.   ||
    265265||[=#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.  ||
    … …  
    269269||[=#PA0227 PA0227]   ||y-direction: gridpoint number (...) is not an integral divisor of the number of processors (...)   || The division of the number of grid points along the y-direction given by [../inipar#ny ny]+1 by the number of processors along the y-direction has a rest and is therefore not an integral divisor of the number of processors. To solve this problem you must ensure that the aforementioned division is without rest for example by setting the number of PEs in y-direction manually (see [../d3par#npey npey]) or by changing [../inipar#ny ny]. It might also be the case that you did not think about that [../inipar#ny ny]+1 is the total number of gridpoints along the y-direction instead of [../inipar#ny ny]. ||
    270270||[=#PA0228 PA0228]   ||y-direction: ny does not match the requirements given by the number of PEs used please use ny = ... instead of ny =...   ||  ||
    271 ||[=#PA0229 PA0229]   ||nesting-setup requires more MPI procs (...) than provided (...)   ||This message appears for nested runs, if the total number of MPI processes for all nested domains given in the nestpar-NAMELIST is larger than the number of MPI processes which has been allowed for the run, e.g. with mrun-option -X. (Attention: For hybrid OpenMP/MPI-runs the number of MPI processes allowed for the run is the number given by -X divided by the number of threads per MPI-task, as given with mrun-option -O.) You either have to provide the run more resources (i.e. more cores) or you have to decrease the number of MPI processes in $nestpar. ||
     271||[=#PA0229 PA0229]   ||nesting-setup requires more MPI procs (...) than provided (...)   ||This message appears for nested runs, if the total number of MPI processes for all nested domains given in the nestpar-NAMELIST is larger than the number of MPI processes which has been allowed for the run, e.g. with palmrun-option -X. (Attention: For hybrid OpenMP/MPI-runs the number of MPI processes allowed for the run is the number given by -X divided by the number of threads per MPI-task, as given with palmrun-option -O.) You either have to provide the run more resources (i.e. more cores) or you have to decrease the number of MPI processes in $nestpar. ||
    272272||[=#PA0230 PA0230]   ||transposition z --> x: nz=... is not an integral divisor of pdims(1)= ...   ||Due to restrictions in data transposition, the division of [../inipar#nz nz] by the number of processors in x-direction has to be without rest. Please ensure this by changing [../inipar#nz nz] or setting the number of gridpoints in x-direction (pdims(1)) manually by [../d3par#npex npex].  ||
    273273||[=#PA0231 PA0231]   ||transposition x --> y: nx+1=... is not an integral divisor of pdims(2)= ...   || Due to restrictions in data transposition, the division of [../inipar#nx nx]+1 by the number of processors in y-direction has to be without rest. Please ensure this by changing [../inipar#nx nx] or setting the number of gridpoints in y-direction (pdims(2)) manually by [../d3par#npey npex]. ||
    … …  
    316316||[=#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. ||
    317317||[=#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. ||
    318 ||[=#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/mrun mrun] which can be used to start model runs. This message appears, if {{{ENVPAR}}} could not be found because it was not created by mrun. Check if you changed anything in the script.  ||
    319 ||[=#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 mrun to start your run, (2) you used an old version of mrun that is not compatible with your model version anymore (then please update) or (3) you changed mrun manually and set some parameters of the {{{&envpar}}} namelist incorrectly. (Also see [#PA0276 PA0276])  ||
    320 ||[=#PA0278 PA0278]   ||no envpar-NAMELIST found in local file ENVPAR 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/mrun mrun] which can be used to start model runs. The {{{&envpar}}} namelist was not found. This is possible if you (1) did not use mrun to start your run or (2) changed mrun manually so that the namelist is not properly created.  ||
     318||[=#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.  ||
     319||[=#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])  ||
     320||[=#PA0278 PA0278]   ||no envpar-NAMELIST found in local file ENVPAR 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. The {{{&envpar}}} namelist was not found. This is possible if you (1) did not use palmrun to start your run or (2) changed palmrun manually so that the namelist is not properly created.  ||
    321321||[=#PA0279 PA0279]   ||wrong component: ...   || This message is produced by the procedure pcm_tendency of the plant canopy model. It calculates drag for velocity components and scalar quantities. The calculated components are: u, v, w, pt, q, e, s (1-7). The subroutine is only called for these 7 quantities. If this error occured, you called the routine from your own code for a component that is out of range. If you wish to do this, you must adjust procedures pcm_tendency and pcm_tendency_ij in file [source:palm/trunk/SOURCE/plant_canopy_model_mod.f90  plant_canopy_model_mod.f90] accordingly. ||
    322322||[=#PA0280 PA0280]   ||No tunnel width is given.   || This error occurs if you have set [../inipar#topography topography]='' 'tunnel' '' in you parameter file but you did not specify [../inipar#tunnel_width_x tunnel_width_x] or [../inipar#tunnel_width_y tunnel_width_y]  ||
    … …  
    358358||[=#PA0315 PA0315]   ||color_interval(2) <= color_interval(1)   || Two values can be given for parameter [../dvrpar#color_interval color_interval], but the first value must be smaller than the second value, e.g. [../dvrpar#color_interval color_interval] = 0.0, 1.0. For details see parameters [../dvrpar#color_interval color_interval] and [../dvrpar#particle_color particle_color]. ||
    359359||[=#PA0316 PA0316]   ||dvrpsize_interval(2) <= dvrpsize_interval(1)   || Two values can be given for parameter [../dvrpar#dvrpsize_interval dvrpsize_interval], but the first value must be smaller than the second value, e.g. [../dvrpar#dvrpsize_interval dvrpsize_interval] = 0.0, 1.0. For details see parameters [../dvrpar#dvrpsize_interval dvrpsize_interval] and [../dvrpar#particle_dvrpsize particle_dvrpsize]. ||
    360 ||[=#PA0317 PA0317]   ||ocean = .F. does not allow coupling_char = ... set by mrun-option "-y"   || The mrun option "-y" must not be used for atmosphere runs. The option is only required for ocean precursor runs, which are followed by [../examples/coupled atmosphere-ocean coupled] restart runs. ||
     360||[=#PA0317 PA0317]   ||ocean = .F. does not allow coupling_char = ... set by palmrun-option "-y"   || The palmrun option "-y" must not be used for atmosphere runs. The option is only required for ocean precursor runs, which are followed by [../examples/coupled atmosphere-ocean coupled] restart runs. ||
    361361||[=#PA0318 PA0318]   ||inflow_damping_height must be explicitly specified because the inversion height calculated by the prerun is zero   ||See [../inipar#inflow_damping_height inflow_damping_height].  ||
    362362||[=#PA0319 PA0319]   ||section_xy must be <= nz + 1 = ...   || ** ||
                                                                                                                                                                                                                                                                                                                                                                               
  | Impressum | ©Leibniz Universität Hannover |