Changes between Version 424 and Version 425 of doc/app/errmsg


Ignore:
Timestamp:
Jun 9, 2017 8:22:54 AM (8 years ago)
Author:
schwenkel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/errmsg

    v424 v425  
    255255||[=#PA0215 PA0215]   ||particle group !# ... has a density ratio /= 0 but radius = 0   ||[[span(style=color: #FF0000, Johannes)]]  ||
    256256||[=#PA0216 PA0216]   ||number of initial particles (...) exceeds maximum_number_of_particles (...) on PE ...   || More particles are initialized than allowed by [../parpar#maximum_number_of_particles maximum_number_of_particles]. Adjust [../parpar#pdx pdx], [../parpar#pdy pdy], and [../parpar#pdz pdz] to reduce the number of particles. '''Not available from release 4.0 on.''' ||
    257 ||[=#PA0217 PA0217]   ||unknown boundary condition bc_par_b = "..."   || ||
    258 ||[=#PA0218 PA0218]   ||unknown boundary condition bc_par_t = "..."   || ||
    259 ||[=#PA0219 PA0219]   ||unknown boundary condition bc_par_lr = "..."   || ||
    260 ||[=#PA0220 PA0220]   ||unknown boundary condition bc_par_ns = "..."   ||  ||
     257||[=#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. ||
     258||[=#PA0218 PA0218]   ||unknown boundary condition bc_par_t = "..."   || See parameter [../parpar#bc_par_t bc_par_t] or allowed values, and appropriately correct your parameter file. ||
     259||[=#PA0219 PA0219]   ||unknown boundary condition bc_par_lr = "..."   || See parameter [../parpar#bc_par_lr bc_par_lr] for allowed values, and appropriately correct your parameter file. ||
     260||[=#PA0220 PA0220]   ||unknown boundary condition bc_par_ns = "..."   || See parameter [../parpar#bc_par_ns bc_par_ns] for allowed values, and appropriately correct your parameter file.  ||
    261261||[=#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 [../d3par#npex npex] and [../d3par#npey npey], the product npey*npex has to match exactly the total number of processors which is assigned by the '''mrun'''-option -X. ||
    262262||[=#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 &d3par-Namelist], the remaining, so far not assigned, number of processors has to be set, too.   ||