Home


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

Changes between Version 538 and Version 539 of doc/app/errmsg


Ignore:
Timestamp:
May 24, 2018 3:55:27 PM (7 years ago)
Author:
Giersch
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • doc/app/errmsg

    v538 v539  
    107107||[=#PA0082 PA0082]   ||number of statistic_regions = ... is not allowed ||Adjust parameter [../inipar#statistic_regions statistic_regions] in your parameter file to a value >= ''0''.  ||
    108108||[=#PA0083 PA0083]   ||normalizing_region = ... must be >= 0 and <= ... (value of statistic_regions)  ||The region number given by [../d3par#normalizing_region normalizing_region] must be within the range [0, [../inipar#statistic_regions statistic_regions] ]. Adjust [../d3par#normalizing_region normalizing_region] appropriately in your parameter file. ||
    109 ||[=#PA0084 PA0084]   || ||message number is unused. ||
     109||[=#PA0084 PA0084]   || ||Message number is unused. ||
    110110||[=#PA0085 PA0085]   ||averaging_interval = ... must be <= dt_data_output_av = ... ||The [../d3par#averaging_interval averaging_interval] for averaged output data must be smaller or equal to the output interval given by [../d3par#dt_data_output dt_data_output] or [../d3par#dt_data_output_av dt_data_output_av]. Adjust settings of these variables appropriately in the parameter file. ||
    111111||[=#PA0086 PA0086]   ||averaging_interval_pr = ... must be <= dt_dopr = ... ||The [../d3par#averaging_interval_pr averaging_interval_pr] for profile output data must be smaller or equal to the output interval given by [../d3par#dt_dopr dt_dopr]. Adjust settings of these variables appropriately in the parameter file. ||
    … …  
    139139||[=#PA0114 PA0114]   ||illegal value for data_output or data_output_user = "..."   || No matching variable was found for the given identifier in the parameter file. Possible reasons are: (a) a typo in the parameter file, (b) a user-defined variable has not been defined in {{{user_check_data_output.f90}}}, (c) the string length of the user-defined variable exceeds the current limits (see [../userint/output here]). ||
    140140||[=#PA0115 PA0115]   ||illegal value for data_output = "..."   || No matching variable was found for the given identifier in the parameter file. This error is most likely related to a typo in the parameter file (a output variable was used that does not exist in PALM). For possible output quantities see [../d3par#data_output data_output]. ||
    141 ||[=#PA0116 PA0116]   ||  || message number is unused.  ||
     141||[=#PA0116 PA0116]   ||  || Message number is unused.  ||
    142142||[=#PA0117 PA0117]   ||pointer for array ".." can't be associated   ||This is an internal error message from the pmc (PALM model coupler) which is responsible for data exchange in nested runs. Please submit a trouble ticket if you are sure that you did not modify the source code of the model coupler ({{{pmc_interface_mod.f90}}}).  ||
    143143||[=#PA0118 PA0118]   ||using the beta function for the construction of the leaf area density profile requires both alpha_lad and beta_lad to be /= 9999999.9 ||If the lad (leaf area density) profile of a vegetation canopy is to be constructed using a beta distribution, parameters [/wiki/doc/app/canpar#alpha_lad alpha_lad], [/wiki/doc/app/canpar#beta_lad beta_lad] must be set and [/wiki/doc/app/canpar#lai_beta lai_beta] must be given a non-zero value. ||
    … …  
    190190||[=#PA0147 PA0147]   ||unknown splitting function = "..."   || See parameter [../parpar#splitting_function splitting_function] for allowed values, and appropriately correct your parameter file.  ||
    191191||[=#PA0148 PA0148]   ||particle too fast. n = ...   || Particle has moved further than the length of one PE subdomain within on timestep. This is not allowed, since particles can only be transferred from one subdomain to the neighboring subdomain. Please check if subdomains are too small or velocities are unrealistically high. ||
    192 ||[=#PA0149 PA0149]   || ||message number is unused.   ||
     192||[=#PA0149 PA0149]   || ||Message number is unused.   ||
    193193||[=#PA0150 PA0150]   ||Both dp_external and conserve_volume_flow are .TRUE., but one of them must be .FALSE.   || Simultaneous use of an external pressure gradient forcing ([../inipar#dp_external dp_external] = .TRUE.) and [../inipar#conserve_volume_flow conserve_volume_flow] is not allowed. Please correct your parameter file appropriately. ||
    194194||[=#PA0151 PA0151]   ||dp_level_b = ... is out of range [zu(nzb), zu(nzt)]  || [../inipar#dp_level_b dp_level_b] is outside of the vertical bounds of the model domain. Please check the prescribed value for [../inipar#dp_level_b dp_level_b] in your parameter file. ||
    … …  
    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]   ||   ||   Message number is unused. ||
    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]   ||   ||Message number is unused ||
    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]   ||   ||Message number is unused. ||
    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]   ||   || Message number is unused. ||
    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]   || || Message number is unused ||
    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]   || || Message number is unused ||
    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].  ||
    … …  
    334334||[=#PA0291 PA0291]   ||mismatch between actual data and data from prior run on PE ... \\nzb on file = ... \\nzb = ...   || 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. See documentation of [../examples/turbinf tubulent inflow] for detailed information on the use of restart data for precursor runs. ||
    335335||[=#PA0292 PA0292]   ||mismatch between actual data and data from prior run on PE ... \\nzt on file = ... \\nzt = ...   || The vertical extent of the model domain must be the same in precursor and main run. See documentation of [../examples/turbinf tubulent inflow] for detailed information on the use of restart data for precursor runs. ||
    336 ||[=#PA0293 PA0293]   || || message number is unused. ||
    337 ||[=#PA0294 PA0294]   || || message number is unused. ||
    338 ||[=#PA0295 PA0295]   || || message number is unused. ||
     336||[=#PA0293 PA0293]   || || Message number is unused. ||
     337||[=#PA0294 PA0294]   || || Message number is unused. ||
     338||[=#PA0295 PA0295]   || || Message number is unused. ||
    339339||[=#PA0296 PA0296]   ||version mismatch concerning binary_version_global: version on file = "..." version on program = "..."   || The precursor run was carried out with a different 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.  ||
    340340||[=#PA0297 PA0297]   ||numprocs not found in data from prior run on PE ...   || Number of processors are not written out or read in correctly during restarts. Please submit a  [/newticket trouble ticket]. ||
    … …  
    431431||[=#PA0351 PA0351]   ||heatflux must not be set for pure neutral flow ||Inipar parameter [../inipar#neutral neutral] = .TRUE. has been set, but non-zero values for parameters [../inipar#surface_heatflux surface_heatflux] and / or [../inipar#top_heatflux top_heatflux] are given at the same time. This is not allowed for simulating a flow with pure neutral stratification where the temperature equation is switched off. Check your parameter file. ||
    432432||[=#PA0352 PA0352]   ||pavement_type = 0 (user_defined) requires setting of z0_pavement /= 9999999.9 || In case of a user-defined pavement type, the roughness length must be given by the user ||
    433 ||[=#PA0353 PA0353]   ||pavement_type = 0 (user_defined) requires setting of z0h_pavement /= 9999999.9 || In case of a user-defined pavement type, the roughness length must be given by the user ||
    434 ||[=#PA0354 PA0354]   || It is not allowed to arrange more than 100 profiles with cross_profiles. Apart from that, all profiles are saved to the netCDF file. || All profiles are written to the netCDF file. Only the first 100 profiles will be plotted by palmplot pr with var=cross_profiles (default). To see all profiles, add the parameter var=all to palmplot pr. ||
     433||[=#PA0353 PA0353]   || || Message number is unused. ||
     434||[=#PA0354 PA0354]   || It is not allowed to arrange more than 100 profiles with cross_profiles. Apart from that, all profiles are saved to the netCDF file. || This is just an informative message. All profiles are written to the netCDF file. Only the first 100 profiles will be plotted by palmplot pr with var=cross_profiles (default). To see all profiles, add the parameter var=all to palmplot pr. ||
    435435||[=#PA0355 PA0355]   ||netcdf_deflate out of range \\ given value: ..., allowed range: 0-9  ||Set d3par-parameter [../d3par#netcdf_deflate netcdf_deflate] to a value within the allowed range ||
    436436||[=#PA0356 PA0356]   ||netcdf_deflate reset to 0  ||You have set [../d3par#netcdf_data_format netcdf_data_format] /= 3 and [../d3par#netcdf_deflate netcdf_deflate] > 0 in the d3par-NAMELIST. However, data compression only works for the NetCDF4/HDF5 non-parallel format ([../d3par#netcdf_data_format netcdf_data_format] = 3).  ||
    437 ||[=#PA0357 PA0357]   ||unknown cloud microphysics scheme cloud_scheme = "..."   || Unknown cloud microphysics scheme. Allowed [../inipar#cloud_scheme cloud] microphysics schemes are "saturation_adjust", "kessler" or "seifert_beheng". ||
    438 ||[=#PA0358 PA0358]   ||data_output_pr = '...' is not implemented for cloud_scheme /= seifert_beheng || Output of profiles of rain drop number concentration (nr) or rain water content (qr) is only allowed for [../inipar#cloud_scheme cloud_scheme] = "seifert_beheng". ||
    439 ||[=#PA0359 PA0359]   ||output of "..." requires cloud_scheme = seifert_beheng || Output of 3d-data or cross-sections of rain drop number concentration (nr) or rain water content (qr) is only allowed for [../inipar#cloud_scheme cloud_scheme] = "seifert_beheng". ||
     437||[=#PA0357 PA0357]   ||unknown cloud microphysics scheme cloud_scheme = "..."   || Unknown cloud microphysics scheme. Allowed [../inipar#cloud_scheme cloud] microphysics schemes are "saturation_adjust", "kessler", "seifert_beheng" or "morrison". ||
     438||[=#PA0358 PA0358]   ||data_output_pr = '...' is not implemented for cloud_scheme /= ... || Output of profiles of rain drop number density (nr) or rain water mixing ratio (qr) is only allowed for [../inipar#cloud_scheme cloud_scheme] = "seifert_beheng". Output of profiles of cloud drop number density (nc) is only allowed for [../inipar#cloud_scheme cloud_scheme] = "morrison". ||
     439||[=#PA0359 PA0359]   ||output of "..." requires cloud_scheme = seifert_beheng || Output of 3d-data, cross-sections or masked data of rain drop number concentration (nr) or rain water content (qr) is only allowed for [../inipar#cloud_scheme cloud_scheme] = "seifert_beheng". Output of cloud drop number density (nc) is only allowed for [../inipar#cloud_scheme cloud_scheme] = "morrison". ||
    440440||[=#PA0360 PA0360]   ||plant_canopy = .TRUE. requires cloud_scheme /= seifert_beheng || It is not allowed to use [../canpar plant_canopy] with the [../inipar#cloud_scheme cloud_scheme] = "seifert_beheng". ||
    441441||[=#PA0361 PA0361]   || output of ssws requires passive_scalar=.TRUE.   || Variables connected with passive_scalar, e.g. like the resolved-scale turbulent scalar flux w*s*, can only be output if [../inipar#passive_scalar passive_scalar] = '''.TRUE.'''   ||
                                                                                                                                                                                                                                                                                                                                                                               
  | Impressum | ©Leibniz Universität Hannover |