Changes between Version 726 and Version 727 of doc/app/errmsg
- Timestamp:
- Feb 26, 2021 3:55:25 PM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
doc/app/errmsg
v726 v727 264 264 ||[=#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 [../runtime_parameters#npex npex] and [../runtime_parameters#npey npey], the product npey*npex has to match exactly the total number of processors which is assigned by the '''palmrun'''-option -X. || 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 [../runtime_parameters#npex npex] or [../runtime_parameters#npey npey] is set in the [../runtime_parameters#pgrid &runtime_parameters-Namelist], the remaining, so far not assigned, number of processors has to be set, too. || 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/nest parNesting]-section of the model steering parameters. ||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/nesting_parameters Nesting]-section of the model steering parameters. || 267 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 [../initialization_parameters#dz_stretch_level_start dz_stretch_level_start] and [../initialization_parameters#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 [../initialization_parameters#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 [../runtime_parameters#npex npex]) or by changing [../initialization_parameters#nx nx]. It might also be the case that you did not think about that [../initialization_parameters#nx nx]+1 is the total number of gridpoints along the x-direction instead of [../initialization_parameters#nx nx]. || … … 639 639 ||[=#PA0415 PA0415] ||water_type = 0 (user_defined) requires setting of z0_water /= 9999999.9' ||If the [../land_surface_parameters#water_type water_type] is set to be user-specific, it is essential to prescribe a roughness length for momentum (in m) for water surface types. || 640 640 ||[=#PA0416 PA0416] ||nesting grid-spacing ratio ( parent dx / child dx [or dy or dz, respectively] ) must have an integer value [for each z-level] || Parent / child grid spacing ratios in each coordinate direction must be integer valued. This also implies that vertical grid stretching is not allowed in nested runs except in the root domain above the top level of the highest nest-domain || 641 ||[=#PA0417 PA0417] ||illegal nesting mode: ... ||Allowed values for [../nest par#nesting_mode nesting_mode] are 'one-way', 'two-way' or 'vertical'. ||642 ||[=#PA0418 PA0418] ||illegal nesting datatransfer mode: ... ||Allowed values for [../nest par#nesting_datatransfer_mode nesting_datatransfer_mode] are 'cascade', 'mixed' or 'overlap'. ||641 ||[=#PA0417 PA0417] ||illegal nesting mode: ... ||Allowed values for [../nesting_parameters#nesting_mode nesting_mode] are 'one-way', 'two-way' or 'vertical'. || 642 ||[=#PA0418 PA0418] ||illegal nesting datatransfer mode: ... ||Allowed values for [../nesting_parameters#nesting_datatransfer_mode nesting_datatransfer_mode] are 'cascade', 'mixed' or 'overlap'. || 643 643 ||[=#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 644 ||[=#PA0420 PA0420] ||Number of agents exceeds agent dimension. \\ Starting at time_since_reference_point = <time_since_reference_point> s, \\ data may be missing. \\ Number of agents: <out_noa> \\ Agent dimension size: <dim_size_agtnum> ||This is a result of the user manually setting either [../agent_parameters#dim_size_agtnum_manual dim_size_agtnum_manual] or [../agent_parameters#dim_size_factor_agtnum dim_size_factor_agtnum] or both, resulting in the agent-number dimension of [../iofiles#DATA_AGT_NETCDF DATA_AGT_NETCDF] becoming smaller than the number of agents the MAS tries to ouput. Please adjust the parameters accordingly. || … … 866 866 ||[=#PA0650 PA0650] || Invalid input value: pc_sa || Number concentration of gaseous sulphuric acid given to the subroutine for ternary nucleation ({{{ternucl}}}) is not within the allowed range of 1e4-1e9 cm^-3^. || 867 867 ||[=#PA0651 PA0651] || Invalid input value: pc_nh3 || Mixing ratio of gaseous ammonia given to the subroutine for ternary nucleation ({{{ternucl}}}) is not within the allowed range of 0.1-100 ppt. || 868 ||[=#PA0652 PA0652] || Child domain too narrow [or shallow] for anterpolation in x- [or y- or z-]direction || In case of [../nest par#nesting_mode nesting_mode] = 'two-way', the child domain must cover a sufficient number of parent-grid cells in all directions. Otherwise anterpolation is not possible. The absolute minimum number of parent-grid cells covered in x- and y-directions is 3 + 2*[../nestpar#anterpolation_buffer_width anterpolation_buffer_width], and 2 + [../nestpar#anterpolation_buffer_width anterpolation_buffer_width] in z-direction. However, it is recommended that child domains cover much larger number of parent-grid cells. This error message is only given if [../nestpar#nesting_mode nesting_mode] = 'two-way'. ||869 ||[=#PA0653 PA0653] || Anterpolation_buffer_width value too high, reset to 0 || In case of a marginally small child domain (see PA0652 above), the user is warned and [../nest par#anterpolation_buffer_width anterpolation_buffer_width] is set to 0 (the default value is 2) so that the minimum criteria (see PA0652 above) for the child domain size in terms of the number of parent-grid cells covered are satisfied. However, it is recommended that child domains cover much larger number of parent-grid cells. This warning is only given if [../nestpar#nesting_mode nesting_mode] = 'two-way'. ||870 ||[=#PA0654 PA0654] || Anterpolation_buffer_width value too high, reset to the default value 2 || In case of too wide anterpolation buffer, the user is informed and [../nest par#anterpolation_buffer_width anterpolation_buffer_width] is reset to its default value 2 so that the minimum criteria (see PA0652 above) for the child domain size in terms of the number of parent-grid cells covered are satisfied. However, it is recommended that child domains cover much larger number of parent-grid cells. This informative message is only given if [../nestpar#nesting_mode nesting_mode] = 'two-way'. ||868 ||[=#PA0652 PA0652] || Child domain too narrow [or shallow] for anterpolation in x- [or y- or z-]direction || In case of [../nesting_parameters#nesting_mode nesting_mode] = 'two-way', the child domain must cover a sufficient number of parent-grid cells in all directions. Otherwise anterpolation is not possible. The absolute minimum number of parent-grid cells covered in x- and y-directions is 3 + 2*[../nesting_parameters#anterpolation_buffer_width anterpolation_buffer_width], and 2 + [../nesting_parameters#anterpolation_buffer_width anterpolation_buffer_width] in z-direction. However, it is recommended that child domains cover much larger number of parent-grid cells. This error message is only given if [../nesting_parameters#nesting_mode nesting_mode] = 'two-way'. || 869 ||[=#PA0653 PA0653] || Anterpolation_buffer_width value too high, reset to 0 || In case of a marginally small child domain (see PA0652 above), the user is warned and [../nesting_parameters#anterpolation_buffer_width anterpolation_buffer_width] is set to 0 (the default value is 2) so that the minimum criteria (see PA0652 above) for the child domain size in terms of the number of parent-grid cells covered are satisfied. However, it is recommended that child domains cover much larger number of parent-grid cells. This warning is only given if [../nesting_parameters#nesting_mode nesting_mode] = 'two-way'. || 870 ||[=#PA0654 PA0654] || Anterpolation_buffer_width value too high, reset to the default value 2 || In case of too wide anterpolation buffer, the user is informed and [../nesting_parameters#anterpolation_buffer_width anterpolation_buffer_width] is reset to its default value 2 so that the minimum criteria (see PA0652 above) for the child domain size in terms of the number of parent-grid cells covered are satisfied. However, it is recommended that child domains cover much larger number of parent-grid cells. This informative message is only given if [../nesting_parameters#nesting_mode nesting_mode] = 'two-way'. || 871 871 ||[=#PA0655 PA0655] || Multiple calls to palm_date_time_set detected. date and time must be set only once. || Routine palm_date_time_set was called multiple times. Please remove any additional calls to this routine from your user code. || 872 872 ||[=#PA0656 PA0656] || Date and time are not set yet. Reset not possible. || palm_date_time_reset was called before palm_date_time_set which is not allowed. ||
