Home

Context Navigation

errmsg

Timestamp:: Feb 13, 2023 4:59:10 PM (2 years ago)
Author:: raasch
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

doc/app/errmsg

-                      v849
+                      v850
 ||[=#PA0185 PA0185]   || data_output_pr = s*2 is not implemented for passive_scalar = .FALSE.  ||The listed entry s*2 in the parameter file under  [../runtime_parameters#data_output_pr data_output_pr] is only available for [../initialization_parameters#passive_scalar passive_scalar]= .T.. ||
 ||[=#PA0186 PA0186]   || no spectra data available   || This message occurs if the {{{data_output_spectra}}} routine is called but no spectra data was calculated through the routine {{{calc_spectra}}}. Check your [../spectra_parameters#SpectraParameters spectra settings] in the parameter file. ||
 ||[=#PA0187 PA0187]   ||fft method "system-specific" currently does not work on NEC   ||Usage of system-specific fft has been switched on with parameter [../initialization_parameters#fft_method fft_method], but the relevant part of the PALM code where the NEC-fft-library calls (e.g. DZFFT or DZFFTM) are used contains bugs which still require to be solved. You may submit a [/newticket trouble ticket] and ask for help. ||
+||[=#PA0187 PA0187]   ||not in use   || ||
 ||[=#PA0188 PA0188]   ||no system-specific fft-call available  ||You have set [../initialization_parameters#fft_method fft_method] = ''system-specific''. In this case you additionally have to set the cpp-preprocessor switches {{{-D__ibm}}} or {{{-D__nec}}} to specify the fft-library that you like to use. Calls to IBM/NEC-libraries are the only one implemented so far in the PALM code. Probably you forgot to set such a switch. Set the switch and do not forget to recompile the code. ||
 ||[=#PA0189 PA0189]   ||fft method "..." not available   ||See [../initialization_parameters#fft_method fft_method] for the availabe methods that are implemented in PALM and modify the initialization-parameter {{{fft_method}}} in your NAMELIST file appropriately.||
 …
 ||[=#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.  ||
 ||[=#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. ||
 ||[=#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]. ||
+||[=#PA0225 PA0225]   ||multigrid-solver does not allow to use non-uniform subdomains || Please ensure that 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 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 havn't been aware that [../initialization_parameters#nx nx]+1 is the total number of gridpoints along the x-direction instead of [../initialization_parameters#nx nx]. The same condition  must be fulfilled to the ratio [../initialization_parameters#ny ny]+1 / [../runtime_parameters#npey npey]. ||
 ||[=#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 [../initialization_parameters#dz_stretch_level_start dz_stretch_level_start] accordingly. ||
 ||[=#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 [../initialization_parameters#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 [../runtime_parameters#npey npey]) or by changing [../initialization_parameters#ny ny]. It might also be the case that you did not think about that [../initialization_parameters#ny ny]+1 is the total number of gridpoints along the y-direction instead of [../initialization_parameters#ny ny]. ||
+||[=#PA0227 PA0227]   ||y_shift requires that subdomains are uniform along y-direction  || Please ensure that the division of the number of grid points along the y-direction (given by [../initialization_parameters#ny ny]+1) by the number of processors along the y-direction is without rest for example by setting the number of PEs in y-direction manually (see [../runtime_parameters#npey npey]) or by changing [../initialization_parameters#ny ny]. It might also be the case that you did havn't been aware that [../initialization_parameters#ny ny]+1 is the total number of gridpoints along the y-direction instead of [../initialization_parameters#ny ny]. ||
 ||[=#PA0228 PA0228]   || Two adjacent values of dz must be different || It is necessary to specify different values for [../initialization_parameters#dz dz] if they are adjacent. ||
 ||[=#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. ||
 ||[=#PA0230 PA0230]   ||transposition z --> x: nz=... is not an integral multiple of npex= ...   ||Due to restrictions in data transposition, the division of [../initialization_parameters#nz nz] by the number of processors in x-direction has to be without rest. Please ensure this by changing [../initialization_parameters#nz nz] or setting the number of gridpoints in x-direction (npex) manually by [../runtime_parameters#npex npex].  ||
 ||[=#PA0231 PA0231]   ||transposition x --> y: nx+1=... is not an integral multiple of npey= ...   || Due to restrictions in data transposition, the division of [../initialization_parameters#nx nx]+1 by the number of processors in y-direction has to be without rest. Please ensure this by changing [../initialization_parameters#nx nx] or setting the number of gridpoints in y-direction (npey) manually by [../runtime_parameters#npey npex]. ||
 ||[=#PA0232 PA0232]   ||transposition y --> z: ny+1=... is not an integral multiple of npex=...    ||Due to restrictions in data transposition, the division of [../initialization_parameters#ny ny]+1 by the number of processors in x-direction has to be without rest. Please ensure this by changing [../initialization_parameters#ny ny] or setting the number of gridpoints in x-direction (npex) manually by [../runtime_parameters#npex npex].  ||
 ||[=#PA0233 PA0233]   ||transposition x --> y: ny+1=... is not an integral multiple of npex=...   ||Due to restrictions in data transposition, the division of [../initialization_parameters#ny ny]+1 by the number of processors in x-direction has to be without rest. Please ensure this by changing [../initialization_parameters#ny ny] or setting the number of gridpoints in x-direction (npex) manually by [../runtime_parameters#npex npex].  ||
 ||[=#PA0234 PA0234]   ||direct transposition z --> y (needed for spectra): nz=... is not an integral multiple of npey=...   || Due to restrictions in data transposition, the division of [../initialization_parameters#nz nz] by the number of processors in y-direction has to be without rest. Please ensure this by changing [../initialization_parameters#nz nz] or setting the number of gridpoints in y-direction (npey) manually by [../runtime_parameters#npey npey]. ||
+||[=#PA0230 PA0230]   ||not in use  || ||
+||[=#PA0231 PA0231]   ||not in use  || ||
+||[=#PA0232 PA0232]   ||not in use  || ||
+||[=#PA0233 PA0233]   ||not in use  || ||
+||[=#PA0234 PA0234]   ||not in use  || ||
 ||[=#PA0235 PA0235]   ||mg_switch_to_pe0_level out of range and reset to 0  || mg_switch_to_pe0_level was manually set out of range. It was reset to 0, so that the gathering level is determined automatically and displayed in file RUN_CONTROL. See [../initialization_parameters#mg_switch_to_pe0_level mg_switch_to_pe0_level] for details. ||
 ||[=#PA0236 PA0236]   ||grid coarsening on subdomain level cannot be performed  || The multigrid pressure solver halfs the number of grid points in each direction to get coarser grid levels. This is done for the subdomains on each PE until one of the directions cannot be divided by 2 without rest. If this is the case, the coarsest grid level of each subdomain are gathered on each PE for further coarsening. Before gathering, the coarsening must be done for the subdomain at least one time. You get this error messages for example with the following combination: \\ [../initialization_parameters#nx  nx ] = 60, [../initialization_parameters#ny  ny ] = 60, [../initialization_parameters#nz  nz ] = 60, \\ [../runtime_parameters#npex  npex ] = 4, [../runtime_parameters#npey  npey ] = 2. \\ With this combination, the subdomain on each PE has the size: \\ nx = 15, ny = 30, nz = 60. \\ The number of grid points in the x-direction of the subdomain cannot be divided by 2 and no coarsening is possible for the subdomains in this example. \\\\ To avoid this error ensure that the number of grid points in each direction can be divided by 2 without rest on the subdomain of an PE at least one time. Therefor vary the number of grid points for the direction which does not fit by changing [../initialization_parameters#nx  nx ], [../initialization_parameters#ny  ny ] or [../initialization_parameters#nz  nz ] or adjust the number of processors by modifying the parameters [../runtime_parameters#npex  npex ] or [../runtime_parameters#npey  npey ] in order to get other subdomain sizes. \\ In the example given above, you can avoid the error by changing nx or npex. For example setting [../initialization_parameters#nx  nx ] = 64 leads to a subdomain of \\ nx = 16, ny = 30, nz = 60. \\ All numbers are now divisible by 2 without rest and the first coarser grid on the subdomain is then: \\ nx = 8, ny = 15, nz = 30. ||