Home


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

Changes between Version 554 and Version 555 of doc/app/errmsg


Ignore:
Timestamp:
Jun 12, 2018 1:32:14 PM (7 years ago)
Author:
Giersch
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • doc/app/errmsg

    v554 v555  
    197197||[=#PA0154 PA0154]   ||unknown conserve_volume_flow_mode: ...   || See parameter [../inipar#conserve_volume_flow_mode conserve_volume_flow_mode] for allowed values, and appropriately correct your parameter file.  ||
    198198||[=#PA0155 PA0155]   ||noncyclic boundary conditions require conserve_volume_flow_mode = "initial_profiles"   || See parameter [../inipar#conserve_volume_flow_mode conserve_volume_flow_mode] for allowed values. [../inipar#conserve_volume_flow_mode conserve_volume_flow_mode] = 'bulk_velocity' is not allowed when you are using non-cyclic boundary conditions.  ||
    199 ||[=#PA0156 PA0156]   ||   ||   Message number is unused. ||
     199||[=#PA0156 PA0156]   || The number of values for dz = ... has to be the same than the number of values for dz_stretch_level_end + 1 = ...  || Self-explanatory. Please add/remove values for [../inipar#dz dz] or for [../inipar#dz_stretch_level_end dz_stretch_level_end] appropriately. ||
    200200||[=#PA0157 PA0157]   ||nonzero bulk velocity requires conserve_volume_flow = .T. and conserve_volume_flow_mode = "bulk_velocity"   || The bulk velocity is used to prescribe a volume flow which then should be conserved. This, however, requires [../inipar#conserve_volume_flow conserve_volume_flow] = .T. and [../inipar#conserve_volume_flow_mode conserve_volume_flow_mode] = "bulk_velocity". ||
    201201||[=#PA0158 PA0158]   ||no vertical boundary condition for variable "..."   || Routine {{{advec_s_bc}}} which calculates the advection term for scalar quantities using the Bott-Chlond scheme was called for a variable, which does not have a specific boundary condition implemented (Adding top and bottom boundaries according to the relevant boundary conditions is not possible). This should not happen. Please submit a [/newticket trouble ticket]. ||
    … …  
    252252||[=#PA0209 PA0209]   ||errors in file [../iofiles#TOPOGRAPHY_DATA TOPOGRAPHY_DATA]   ||Possible reasons for this error include:  \\ 1. File contains a header. Solution: The header of the ESRI Ascii Grid format (usually 6 lines) must be removed. \\ 2. File does not contain enough data. \\ a) The number of columns (`ncols`) is less than [../inipar#nx nx]+1. \\ b) The number of rows (`nrows`) is less than [../inipar#ny ny]+1. \\ Solution: Make sure that `ncols` matches `nx+1` and that `nrows` matches `ny+1`.   ||
    253253||[=#PA0210 PA0210]   ||nzb_local values are outside the model domain MINVAL( nzb_local ) = ... MAXVAL( nzb_local ) = ...   || This error occurs during grid consistency checks of the index arrays when using non-flat topography with regard to the vertical dimension. Please submit a [/newticket trouble ticket] if you have run into this error because this should not happen. ||
    254 ||[=#PA0211 PA0211]   ||   ||Message number is unused ||
     254||[=#PA0211 PA0211]   || The number of values for dz = ... has to be the same or one more than the number of values for dz_stretch_level_start = ...  || Self-explanatory. Please add/remove values for [../inipar#dz dz] or for [../inipar#dz_stretch_level_start dz_stretch_level_start] appropriately. ||
    255255||[=#PA0212 PA0212]   ||Overhanging topography do not work with particles    || When you have defined an overhanging structure in your topography data the simultaneous use of the Lagrangian particle model could be dangerous because reflection boundary conditions (as well as subgrid-scale velocities) are not realized for downward-facing walls so far.  ||
    256256||[=#PA0213 PA0213]   || max_number_of_particle_groups = ... number_of_particle_groups reset to reset to ... || If the [../parpar#number_of_particle_groups number_of_particle_groups] > 10 then is reset to the maximum number of particle groups (at maximum 10 are allowed) ||
    257257||[=#PA0214 PA0214]   ||version mismatch concerning data from prior run version on file = ... version in program = ...   || This error occurs when particle data from the [../iofiles#PARTICLE_RESTART_DATA_OUT restart file] is read and the precursor run was carried out with a different particle binary version than the main run. Repeat the precurser with the current version or carry out the main run with the same version as the precursor. You can check the particle binary version number which is required for the main run in {{{lpm_read_restart_file.f90}}}.  ||
    258258||[=#PA0215 PA0215]   ||particle group # ... has a density ratio /= 0 but radius = 0   || Particles with mass but without radius are not allowed. Please  appropriately correct [../parpar#radius radius] or [../parpar#density_ratio density_ratio] ||
    259 ||[=#PA0216 PA0216]   ||   ||Message number is unused. ||
     259||[=#PA0216 PA0216]   || The number of values for dz_stretch_level_start = ... has to be the same or one more than the number of values for dz_stretch_level_end = ...  || Self-explanatory. Please add/remove values for [../inipar#dz_stretch_level_start dz_stretch_level_start] or for [../inipar#dz_stretch_level_end dz_stretch_level_end] appropriately. ||
    260260||[=#PA0217 PA0217]   ||unknown boundary condition bc_par_b = "..."   || See parameter [../parpar#bc_par_b bc_par_b] for allowed values, and appropriately correct your parameter file.  ||
    261261||[=#PA0218 PA0218]   ||unknown boundary condition bc_par_t = "..."   || See parameter [../parpar#bc_par_t bc_par_t] for allowed values, and appropriately correct your parameter file.  ||
    … …  
    265265||[=#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.   ||
    266266||[=#PA0223 PA0223]   ||errors in \$nesting_parameters   ||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.  ||
    267 ||[=#PA0224 PA0224]   ||   || Message number is unused. ||
     267||[=#PA0224 PA0224]   || Eeach dz_stretch_level_end has to be ... than its corresponding value for dz_stretch_level_start ... 4*MAX(dz(n),dz(n+1)) to allow for smooth grid stretching  || To allow for a smooth stretching, the distance between [../inipar#dz_stretch_level_start dz_stretch_level_start] and [../inipar#dz_stretch_level_end dz_stretch_level_end] has to be large enough. Please increase the stretching region appropriately. ||
    268268||[=#PA0225 PA0225]   ||x-direction: gridpoint number (...) is not an integral divisor of the number of processors (...)   || The division of the number of grid points along the x-direction given by [../inipar#nx nx]+1 by the number of processors along the x-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 x-direction manually (see [../d3par#npex npex]) or by changing [../inipar#nx nx]. It might also be the case that you did not think about that [../inipar#nx nx]+1 is the total number of gridpoints along the x-direction instead of [../inipar#nx nx]. ||
    269 ||[=#PA0226 PA0226]   || || Message number is unused ||
     269||[=#PA0226 PA0226]   || Eeach dz_stretch_level_start has to be ... than ... || The stretching region has to be defined above the first two grid points (Prandtl-layer). In case of ocean = .T. the stretching region muss below the two highest grid points (surface). Please adjust [../inipar#dz_stretch_level_start dz_stretch_level_start] accordingly. ||
    270270||[=#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]. ||
    271 ||[=#PA0228 PA0228]   || || Message number is unused ||
     271||[=#PA0228 PA0228]   || Two adjacent values of dz must be different || It is necessary to specify different values for [../inipar#dz dz] if they are adjacent. ||
    272272||[=#PA0229 PA0229]   ||nesting-setup requires different number of 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. ||
    273273||[=#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].  ||
    … …  
    642642||[=#PA0418 PA0418]   ||illegal nesting datatransfer mode: ... ||Allowed values for [../nestpar#nesting_datatransfer_mode nesting_datatransfer_mode] are 'cascade', 'mixed' or 'overlap'. ||
    643643||[=#PA0419 PA0419]   ||mismatch between root model and child settings: \\ <parameter name>(root) = ... \\ <parameter name>(child) = ... \\ child value is set to root value ||The displayed parameter has been assigned different values for the root domain and a child domain (the id of the child domain is listed in the first line of the message) but it must have the same value for all domains. PALM automatically adjusts the child domain value to the one given for the root domain. In order to get rid of this warning message, adjust the parameter in the respective NAMELIST-parameter file of the child (or root) domain.||
    644 ||[=#PA0420 PA0420]   ||  || Message number is unused. ||
     644||[=#PA0420 PA0420]   || Using synthetic turbulence generator in combination with stretching is not allowed || Self-explanatory. Please try your simulation without stretching or try to use the turbulence recycling method for a turbulent inflow.  ||
    645645||[=#PA0421 PA0421]   ||recycling_yshift = .T. requires more than one processor in y direction|| The distance of the y-shift is calculated by INT( npey / 2 ). With only one processor in y direction, no y-shift is possible. ||
    646646||[=#PA0422 PA0422]   ||data_output_pr = ... is not available for cloud_scheme = saturation_adjust || If the output is not necessary, delete the variable from the namelist. If it is necessary, use [../inipar#cloud_scheme cloud_scheme] = kessler, seifert_beheng or morrison. ||
    … …  
    706706||[=#PA0482 PA0482]   ||  Version of binary SVF file "..." does not match the version of model "..." || This error occurs when radiation data from the file SVFIN is read and the precursor run was carried out with a different svf binary version than the main run. Repeat the precurser with the current version or carry out the main run with the same version as the precursor. You can check the svf binary version number which is required for the main run in [[source:palm/trunk/SOURCE/radiation_model_mod.f90| radiation_model_mod.f90]].  ||
    707707||[=#PA0483 PA0483]   ||  Wrong number of SVF or CSF || This error can happen if svf data is read from file SVFIN (e.g. during manual restarts). The local number of sky view factors and canopy sink factors for calculating surface reflection of radiation has to be the same between the precursor run and the main run. Be sure that you create the svf binary data with the same version as the version of the main run. ||
    708 ||[=#PA0484 PA0484]   ||  || Message number is unused. ||
     708||[=#PA0484 PA0484]   || The lowest level where vertical stretching is applied have to be greater than ... || The wind turbine model implemented in PALM does not consider a stretched grid. Therefore grid stretching should only be applied well above the region where the wind turbine model is active. Please adjust [../inipar#dz_stretch_level_start dz_stretch_level_start] accordingly. ||
    709709||[=#PA0485 PA0485]   ||  dissipation_1d = "as_in_3d_model" requires mixing_length_1d = "as_in_3d_model" || The [../inipar#dissipation_1d dissipation rate] in the TKE equation of the 1d-model can be calculated the same way as in the 3D model only if the [../inipar#mixing_length_1d mixing_length] is also calculated as in the 3D model. ||
    710710||[=#PA0486 PA0486]   ||  Usage of radiation module is only allowed if land-surface and/or urban-surface model is applied. || Either the namelist &land_surface_parameters has to be set in the _p3d file or &urban_surface_parameters (or both) to avoid this error. ||
    … …  
    718718||[=#PA0494 PA0494]   || ndsidir from SVF file does not match calculated ndsidir from radiation_presimulate_solar_pos || The number of apparent solar directions in SVFIN does not match the one which is calculated during model initialization. Be sure that you created the svf binary data with the same version as the version of the main run. Otherwise submit a [/newticket trouble ticket]. ||
    719719||[=#PA0495 PA0495]   || optimized multigrid method requires nz to be even || You are using the optimized multigrid method, which requires {{{nz}}} to have an even value. Change {{{nz}}} in your parameter file, or choose {{{psolver = 'multigrid_noopt'}}} (but be aware that with an uneven value of {{{nz}}} the multigrid solver can only use one grid level, so you will have no ''multi'' grid levels at all and hence convergence will be very low!). ||
     720||[=#PA0496 PA0496]   || The lowest level where vertical stretching is applied have to be greater than ... || The radiation model does not consider a stretched grid. The assumption of a uniform grid is necessary in parts below the top layer of urban surface (index height nzut). Please adjust [../inipar#dz_stretch_level_start dz_stretch_level_start] accordingly. ||
     721||[=#PA0497 PA0497]   || Stretching in the parent domain is only allowed above the nested domain || If pure vertical nesting is used the vertical stretching region has to be above the nested domain. Please adjust [../inipar#dz_stretch_level_start dz_stretch_level_start] or reduce the height of the nested domain accordingly.  ||
     722||[=#PA0498 PA0498]   || Stretching in the nested domain is not allowed || You are trying to use vertical grid stretching within the nested domain in combination with pure vertical nesting. This is not allowed due to the interpolation approach between parent and child. Please forgo the vertical stretching for the child. ||
    720723||[=#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'.   ||
    721724||[=#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' ||
                                                                                                                                                                                                                                                                                                                                                                               
  | Impressum | ©Leibniz Universität Hannover |