Logging IDs#

Description: Add the settings to the namelist input file _p3d.

DCP0013#

LogLevel: ERROR

IDM0001#

LogLevel: ERROR

LogLevel: ERROR

LogLevel: ERROR

Message: ... exceeds 0.5 * surface-layer height at ... surface grid point (i,j) = (...,...)

Description: Monin-Obukhov similarity is assumed between the surface and the first computational grid point normal to the surface. Because of the staggered grid, the distance between these two points is half of the grid spacing in the respective direction, i.e. \(dz/2\) in vertical direction. The height \(z = dz/2\) defines the top of the (analytical) logarithmic layer \(z_{mo}\) (the surface layer height). Functions like \(ln(z_{mo}/z_0)\), where \(z_0\) is the roughness length, are used to calculate characteristic surface layer variables like \(u_*\) or \(\theta_*\). This mathematically requires that \(z_{mo} > z_0\), or in other words, that \(z_0 < dz/2\). In case you have run into this error, you either need to reduce the roughness length \(z_0\) (via namelist parameter roughness_length or in the static driver) or enlarge the grid spacing dz. Same holds for roughness length \(z_{0h}\) for temperature and \(z_{0q}\) for moisture.

Attention: This message is given only once (for the first grid point where the exceedance has been detected). Be aware that there might be more grid points where \(z_0\) exceeds the surface-layer height.

In case of water surfaces \(z_0\) is automatically calculated each time step via the Charnock relation and respectively checked. No information about grid point location(s) is given for that case. More than one location may have been detected.

Set allow_roughness_limitation = .TRUE. in order to allow for an automatical limitation of \(z_0\) to a maximum value of \(0.5 * z_{mo}\), which is equivalent to \(0.25 * dz\).

LSM0049#

LogLevel: INFO

Offline Nesting#

Description: Internally, PALM calls the netCDF function NF90_STRERROR which returns an error message string provided by netCDF. Hence, no exact assignment between PALM error number and netCDF error string can be given. Most of the netCDF errors should never appear if the default code is used. The following list gives errors which may be caused by wrong steering or errors due to problems in the user interface.

NCF0079#

LogLevel: ERROR

Message: string match to name in use

Description: A netCDF variable name has been used twice. Possible reasons: a variable in the parameter file has been listed twice (e.g. in data_output) or a variable name that has been defined in the user interface is already used by PALM.

NCF0253#

LogLevel: ERROR

LogLevel: INFO

Message: netCDF file for cross-sections "..." from previous run found. This file will be extended.

Description:

LogLevel: WARNING

Message: netCDF file for spectra from previous run found, but this file cannot be extended due to variable mismatch. New file is created instead.

Description: A netCDF file from a previous run exist which is tried to be opened for extension. However, its variables do not match the ones of the current run. Therefore a new file is created instead.

NCI0032#

LogLevel: WARNING

Message: netCDF file for spectra from previous run found, but this file cannot be extended due to mismatch in number of vertical levels. New file is created instead.

Description: A netCDF file from a previous run exist which is tried to be opened for extension. However, the number of vertical levels which shall be outputted do not match the ones of the current run. Therefore a new file is created instead.

NCI0033#

LogLevel: WARNING

Message: netCDF file for spectra from previous run found, but this file cannot be extended due to mismatch in heights of vertical levels. New file is created instead.

Description: A netCDF file from a previous run exist which is tried to be opened for extension. However, the specified vertical levels (heights) which shall be outputted do not match the ones of the current run. Therefore a new file is created instead.

NCI0034#

LogLevel: WARNING

Message: netCDF file for spectra from previous run found, but this file cannot be extended because the current output time is less or equal than the last output time on this file. New file is created instead.

NCI0035#

LogLevel: INFO

Message: netCDF file for spectra from previous run found. This file will be extended.

Description:

NCI0036#

LogLevel: ERROR

Description: netcdf_data_format > 2 has been set. This requires netCDF4 features, which have to be activated by setting the cpp-switch -D__netcdf4 in the configuration file (line starting with %cpp_options). It also requires a netCDF4 library and possibly to give include- and library paths via -I, -L and -l options in the configuration file (lines starting with %compiler_options and %linker_options).

Without the -D__netcdf4 switch, netcdf_data_format is internally reset to 2, the netCDF 64-bit offset format, where the variable-size is restricted (see netcdf_data_format).

PAC0146#

LogLevel: WARNING

With this combination, the subdomain on each PE has the size nx_s = 15, ny_s = 30, nz_s = 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 on the subdomain of an PE in each direction can be divided by 2 without rest at least one time. Therefore, vary the number of grid points for the direction which does not fit by changing nx, ny, or nz, or adjust the number of processors by modifying npex or npey in order to get other subdomain sizes.

For the example given above, the error can be avoided e.g. by setting nx = 64, which leads to a subdomain of nx_s = 16, ny_s = 30, nz_s = 60. All numbers are now divisible by 2 without rest, and the first coarser grid level on the subdomain then consists of (8, 15, 30) grid points along (x, y, z).

PAC0246#

LogLevel: ERROR

Message: more than 10 multigrid levels

Description: The computational grid (given by nx+1, ny+1, nz) allows for more than 10 coarsening levels for the selected multigrid Poisson-solver (psolver = 'multigrid'), which cannot be handled. This may happen for very large grids, where the grid point numbers along x, y, z are given by 2ⁿ with n > 10. The smallest grid which may cause this error would have 2048³ points. However, depending on the chosen domain decomposition, much larger grids might be possible. To circumvent this problem, change the subdomain size by reducing the total number of grid points or increase the number of cores for this run. Setting mg_switch_to_pe0_level = -1 may also solve the problem.

PAC0247#

LogLevel: ERROR

LogLevel: ERROR

PAC0289#

LogLevel: ERROR

Message: problem with index bound nxr on restart file "..." nxr = ... but it should be = ... from the index bound information array

PAC0290#

LogLevel: ERROR

Message: problem with index bound nys on restart file "..." nys = ... but it should be = ... from the index bound information array

PAC0291#

LogLevel: ERROR

Message: problem with index bound nyn on restart file "..." nyn = ... but it should be = ... from the index bound information array

PAC0292#

LogLevel: ERROR

Message: mismatch between actual data and data from prior run on PE ... nzb on file = ... nzb = ...

Description: The vertical extent of the model domain must be the same in precursor and main run. In this case, there is a mismatch in the respective topography of both runs. See documentation of turbulent inflow for detailed information on the use of restart data for precursor runs.

LogLevel: ERROR

Message: surface_coupler_buffer_handling: illegal action ...

Description: Internal error. Please contact the PALM developers, e.g. via the trouble-ticket system.

PAC0316#

LogLevel: ERROR

Message: inconsistent surface element classification at grid point (i,j,k) = (...,...,...) LSM = .., USM = .., terrain = .., building = ..

Description: Static driver input data is not defined consistently. If surface points are classified as building (e.g. by setting driver variable buildings_2d to a non _FillValue), the urban surface model (USM) must be switched on. If surface points are classified as terrain (e.g. by setting driver variable soil_type to a non _FillValue), the land surface model (LSM) must be switched on. The respective settings in the run are listed in the message. terrain and building are values for the indicated grid point, LSM and USM are global settings. LSM and terrain must both be .T. or .F., also USM and building must both be .T. or .F..

If a respective namelist is missing, add it to the namelist input file (_p3d). Another error reason might be that driver variables for the indicated grid point(s) are all set to _FillValue, so that the surface at that point can not be classified. Respectively check the static driver and remove the inconsistencies.

PAC0317#

LogLevel: ERROR

Message: number of gridpoints along x or/and y contain illegal factors only factors 2, 3, 5 are allowed

Description: In case of fft_method = 'temperton-algorithm', the number of horizontal grid points (nx+1, ny+1) must be composed of prime factors 2,3 and 5. Higher prime factors such as 7 are not allowed. Please ensure that these restrictions are fulfilled or set fft_method = 'fftw' or 'singleton-algorithm'.

PAC0318#

LogLevel: WARNING

Message: Time step has reached minimum limit. dt = ... s Simulation is terminated. old_dt = ... s dt_u = ... s dt_v = ... s dt_w = ... s dt_diff = ... s u_max = ... m/s k=... j=... i=... v_max = ... m/s k=... j=... i=... w_max = ... m/s k=... j=... i=...

Description: The time step is determined according to the CFL criterion to assure a stable numerical solution. This message means that the required minimum time step, determined from the three velocity components, is several orders of magnitude smaller than dt_max, or, in other words, that at least one of the velocity components got too large.

Important: Due to the large number of complex reasons it should be noted that the following list is not complete, but it is intended to give general hints how to proceed in case of this error message. There are various reasons for this message to appear. In general, it just means that the simulation became unstable.

First, check for an unrealistic value of dt_max in the namelist file. Setups with very small grid spacings may require to reduce dt_max. The error message may also indicate unrealistic settings of e.g. boundary conditions or other namelist parameters. Please also check if this error appears if you run without user interface code. In case the land surface model or the urban surface model is employed, surface temperatures may have become unstable during the time-integration. One known issue is e.g. the presence of metal surfaces pavement_type = 7, where the integration of surface tempertures can become unstable, producing unrealistically high or low surface sensible heat fluxes. Please check for possibly mis-represented settings in your static input file.

PAC0319#

LogLevel: ERROR

Message: wrong setting topography = "..."

Description: If topography information is provided via netCDF or ASCII input file, topography = 'read_from_file' is required.

PAC0320#

LogLevel: ERROR

Message: inconsistent building parameters: index_left_bwall=... index_right_bwall=... index_south_bwall=... index_north_bwall=... nx=... ny=...'

Description: The single building setup (topography = 'single_building') yields a too narrow building, or the building walls are positioned outside of the model domain. Please check the setting of the building parameters (e.g. building_wall_left, building_length_x, etc.).

PAC0321#

LogLevel: ERROR

Message: no street canyon width given

Description: In case of topography = 'single_street_canyon', a canyon width must be set, too, by either specifying canyon_width_x or canyon_width_y.

PAC0322#

LogLevel: ERROR

Message: inconsistent canyon parameters: index_left_cwall=... index_right_cwall=... ngp_cx=... ch=... nx=... ny=...

Description: The street canyon setup (topography = 'single_street_canyon') yields a too narrow canyon, or the canyon walls are positioned outside the model domain. Please check the setting of the canyon parameters canyon_wall_left and canyon_width_x.

LogLevel: WARNING

PMC0001#

LogLevel: ERROR

LogLevel: ERROR

Message: dt_3d = ... exceeds dt_coupling = ...

Description: In a coupled atmosphere-ocean run, the time step of either the atmosphere or the ocean model has become larger than the coupling interval given via runtime parameter dt_coupling. Under such condition, the coupled simulation may hang at the end of the run. Try to increase the coupling interval. Because of the large inertia of the ocean, intervals of a few minutes should work very well.

Radiation Model#

RAD0001#

LogLevel: ERROR

Message: output of "..." requires radiation = .TRUE.

Description: #The requested output quantity is only available when the radiation module is switched on.

RAD0002#

LogLevel: ERROR

Message: output of ... requires radiation = .TRUE. and radiation_scheme = "rrtmg"

Description: The requested output quantity is only available with radiation scheme = 'rrtmg'.

RAD0003#

LogLevel: ERROR

Message: output of ... requires radiation = .TRUE. and radiation_scheme = "rrtmg" or radiation_scheme = "tenstream"

Description: The requested output quantity is only available with radiation scheme = 'rrtmg' or 'tenstream'.

SAL0045#

LogLevel: ERROR

Message: missing "emission_category_name" in ...

Description:

SAL0046#

LogLevel: ERROR

Message: none of the emission categories in ... match with the ones in the model

Description: Emission categories in <run_identifier>_salsa do not match with ones applied in the model ('traffic exhaust', 'road dust', 'wood combustion', 'other').

SAL0047#

LogLevel: ERROR

Message: emission_time_factors should be given for each nhoursyear OR nmonthdayhour

Description: Emission time factors for aerosol emissions (LOD=1) are not given or they are not correctly named in <run_identifier>_salsa.

SAL0048#

LogLevel: ERROR

LogLevel: WARNING

Message: boundary layer depth exceeds the model top

Description: The boundary-layer depth is computed from the mesoscale model input. If this warning is given, the model domain top is below or in the range of the computed boundary-layer depth. In some cases, this can lead to blow-ups of the imposed velocity perturbations. To avoid this, it is recommended to increase the vertical model extent.

Turbulence Closure#

TCM0001#

LogLevel: ERROR

Message: unknown turbulence closure: "..."

Description: See turbulence_closure for allowd values.

TCM0002#

LogLevel: ERROR

Message: turbulent inflow/outflow is not yet implemented for RANS mode

Description: A turbulent inflow or turbulent_outflow = .T. is not allowed in RANS mode (see turbulence_closure how to switch between LES/RANS mode).

TCM0003#

LogLevel: ERROR

Set allow_roughness_limitation = .T. in order to allow for an automatic limitation of \(z_0\) to a maximum value of \(0.5 * z_{mo}\), which is equivalent to \(0.25 * dz\).

USM0013#

LogLevel: INFO

Message: ... exceeds 0.5 * surface-layer height at ... surface(s) and is limited to that height

Description: See USM0012 for detailed explanation.

USM0014#

LogLevel: ERROR

Message: building_type is out of the range of possible values

Description: Only values between 1 and 7 are allowed. Please check if the given namelist variable building_type and/or the corresponding static input variable is set to a valid value.

USM0015#

LogLevel: ERROR

Message: building_pars from the static input file is deprecated

Description: Input of building_pars from the static input file is deprecated and will be removed in future releases. Please take the chance to switch to the newly available input variables building_hcap, building_hcond, building_general, building_fracs, building_rad, etc. (see static driver description).

USM0016#

LogLevel: ERROR

LogLevel: ERROR

LogLevel: ERROR

Message: error while writing output: "..."

Description: Internal error, occuring while trying to write the respective variable to the output file. In case a user-interface is not used, contact the PALM developers, e.g. via the trouble-ticket system.

WTM0009#

LogLevel: ERROR

Message: wind turbine ... outside domain bounds position (x,y) = (...,...) domain bounds: 0.0 / ... along x 0.0 / ... along y

Description: Modify hub_x and/or hub_y appropriately. Note that in child domains coordinates have to be given with respect to the origin of the child coordinate system, which is (x,y) = (0.0,0.0) at the left/south corner.

Keys	Action
`?`	Open this help
`n`	Next page
`p`	Previous page
`s`	Search