== Known bugs ==

||='''Date'''  =||='''Reported by'''  =||='''Description'''  =||
|----------------------
||09/05/16 || MS || For very complex topography, e.g. very narrow street canyons or corners that are resolved by only one or two grid points, the use of psolver = 'multigrid_noopt' and masking_method = .F. can lead to a blow up of wind velocity. Please see remarks below. ||
|----------------------
||09/05/16 || MS || In case of topography = .T., different processor topologies do not yield identical results. ||
|----------------------
||18/04/12 || MS || The use of the cache-optimized and the vector-optimized Palm versions do not yield identical results. ||

\\\\
'''Remarks with respect to usage of psolver = 'multigrid_noopt'''' \\

In case of very complex topography, including narrow street canyons or complex shapes resolved by only a few grid points, the use of [../../app/inipar#psolver psolver] = 'multigrid_noopt' in combination with [../../app/inipar#masking_method masking_method] = .F. can lead to a blow up of wind velocity. So far, this never happened if masking_method = .T. or [../../app/inipar#psolver psolver] = 'multigrid' (where topography is always masked). 
A possible workaround to prevent such velocity blow-up is to preprocess the topography by filling holes and removing complex shapes on the small scale before running the LES. (This approach should have no significant effect on the flow field, as in LES the flow in such regions is poorly resolved and do not yield to reliable physical information.)
The reason for this velocity blow-up is unclear so far.