Changes between Version 673 and Version 674 of doc/app/errmsg
- Timestamp:
- Jan 27, 2020 3:14:04 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
doc/app/errmsg
v673 v674 244 244 ||[=#PA0201 PA0201] ||dz=... <= 0.0 || The value given for [../inipar#dz dz] must be greater than 0.0. || 245 245 ||[=#PA0202 PA0202] ||grid anisotropy exceeds threshold given by only local horizontal reduction of near_wall mixing length l_wall starting from height level k = ... . ||The grid-dependent mixing length {{{l_grid}}} ( ''= '''Δ''' = (Δx Δy Δz)^1/3^'' ) becomes larger than 2.7 * dx or 2.7 * dy starting from the reported height level {{{k}}}. Although PALM will not abort due to this warning, the chosen grid setup might lead to untrustworthy results. The reason for this is an unfavourable choise of grid anisotropy. To avoid this, make sure that the values of [../inipar#dx dx], [../inipar#dy dy], and [../inipar#dz dz] do not differ too much from each other. In case of grid stretching, the settings of [../inipar#dz_stretch_level dz_stretch_level] and/or [../inipar#dz_stretch_factor dz_stretch_factor] should be changed to ensure a smaller difference between {{{dz(k)}}} and {{{dx}}} and {{{dy}}} at the reported height level. || 246 ||[=#PA0203 PA0203] ||inconsistent building parameters: bxl=... bxr=... bys=... byn=... nx=... ny=... || The setup of the single building ([../inipar#topography topography] = '' 'single_building' '') yields a too narrow building or the building walls are positioned outside of the model domain. Please check the [../inipar#topo building parameters] in your parameter file. ||246 ||[=#PA0203 PA0203] ||inconsistent building parameters: index_left_bwall=... index_right_bwall=... =... byn=... nx=... ny=... || The setup of the single building ([../inipar#topography topography] = '' 'single_building' '') yields a too narrow building or the building walls are positioned outside of the model domain. Please check the [../inipar#topo building parameters] in your parameter file. || 247 247 ||[=#PA0204 PA0204] ||no street canyon width given || If [../inipar#topography topography] = '' 'single_street_canyon' '' is given, also a canyon width must be given by either specifying [../inipar#canyon_width_x canyon_width_x] or [../inipar#canyon_width_y canyon_width_y] in the parameter file. || 248 ||[=#PA0205 PA0205] ||inconsistent canyon parameters: cxl=... cxr=... cwx=... ch=... nx=... ny=... || Due to [../inipar#canyon_width_x canyon_width_x] the setup of the single street canyon ([../inipar#topography topography] = '' 'single_street_canyon' '') yields a too narrow canyon or the canyon walls are outside of the model domain. Please check the [../inipar#topo canyon parameters] in your parameter file. ||248 ||[=#PA0205 PA0205] ||inconsistent canyon parameters: index_left_cwall=... index_right_cwall=... ngp_cx=... ch=... nx=... ny=... || Due to [../inipar#canyon_width_x canyon_width_x] the setup of the single street canyon ([../inipar#topography topography] = '' 'single_street_canyon' '') yields a too narrow canyon or the canyon walls are outside of the model domain. Please check the [../inipar#topo canyon parameters] in your parameter file. || 249 249 ||[=#PA0206 PA0206] ||inconsistent canyon parameters:... cys=... cyn=... cwy=... ch=... nx=... ny=... || Due to [../inipar#canyon_width_y canyon_width_y] the setup of the single street canyon ([../inipar#topography topography] = '' 'single_street_canyon' '') yields a too narrow canyon or the canyon walls are outside of the model domain. Please check the [../inipar#topo canyon parameters] in your parameter file. || 250 250 ||[=#PA0207 PA0207] ||inconsistent canyon parameters: street canyon can only be oriented either in x- or in y-direction || Please do not specify [../inipar#canyon_width_x canyon_width_x] and [../inipar#canyon_width_y canyon_width_y] in the parameter file at the same time. || … … 252 252 ||[=#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`. || 253 253 ||[=#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] || 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. ||254 ||[=#PA0211 PA0211] || The number of values for dz = ... has to be the same as 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. || 255 255 ||[=#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. || 256 256 ||[=#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) || … … 265 265 ||[=#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. || 266 266 ||[=#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] || E each 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. ||267 ||[=#PA0224 PA0224] || Each 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. || 268 268 ||[=#PA0225 PA0225] ||x-direction: gridpoint number (...) is not an integral multiple 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 multiple 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] || E each 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 mode the stretching region muss below the two highest grid points (surface). Please adjust [../inipar#dz_stretch_level_start dz_stretch_level_start] accordingly. ||269 ||[=#PA0226 PA0226] || Each 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 mode the stretching region muss below the two highest grid points (surface). Please adjust [../inipar#dz_stretch_level_start dz_stretch_level_start] accordingly. || 270 270 ||[=#PA0227 PA0227] ||y-direction: gridpoint number (...) is not an integral multiple 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 multiple 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 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. ||
