Changes between Version 34 and Version 35 of doc/tec/bugs


Ignore:
Timestamp:
Nov 22, 2018 8:46:21 AM (6 years ago)
Author:
suehring
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/tec/bugs

    v34 v35  
    11== Known bugs ==
    22
    3 ||='''Date'''  =||='''Reported by'''  =||='''Description'''  =||
    4 |----------------------
    5 ||06/09/17 || MS || ~~Particle advection using SGS-velocities does not work properly since -r 1359, more precisely, time loop for sub-timesteps is only carried out once. As a consequence, particles accumulate near horizontal and vertical walls.~~ '''Fixed in -r2417.'''
    6 |----------------------
    7 ||14/07/17 || TG || ~~{{{palmplot}}} does not work with NCL 6.3.0. Reading of variable names is incorrect: instead of reading {{{u}}} it reads {{{/u}}} from file. If you use {{{palmplot pr ... var="/u"}}} it does not find the vertical dimension because it searches for {{{z/u}}} but the dimension name is read as {{{/zu}}}.~~ '''won't fix: error occurs with deprecated version of NCL. Solution: update NCL version.''' ||
    8 |----------------------
    9 ||30/06/17 || TG || ~~If 3D topography is used (lod=2), topography and air volume are switched. I.e., prognostic equations are only calculated ''within'' the topography (observed using r2292).~~ '''Fixed in -r2302'''. ||
    10 |----------------------
    11 ||30/06/17 || TG || ~~New surface implementation does not work with a density not equal to one if a non-flat surface is used (since r2252).~~ '''Fixed in revision r2329'''
    12 |----------------------
    13 ||08/05/17 || MS || Domain-averaged velocity variances over surface roughness heterogeneities look strange 
    14 |----------------------
    15 ||28/04/17 || MS || Spectra: wavenumber do not match theoretical value (Pi/dx) at grid cut-off length
    16 |----------------------
    17 ||22/02/17 || MS || ~~Segmentation Fault in netcdf_interface_mod in case of land surface model - Subscript 1 of the array SECTION has value 101 which is greater than the upper bound of 100.~~ '''Fixed in -r2239.'''
    18 |----------------------
    19 ||05/01/17 || MS || ~~Within revision r2092 (and former) there is still a bug in the LPM, particle speeds are getting too large so that particle exchange between cores does not work properly, possibly leading to segmentation faults.~~ '''Remark: Fixed in revision r2100'''.
    20 |----------------------
    21 ||18/10/16 || MS || ~~Output of initial profile of passive scalar quantity #s is not correct.~~ ||
    22 |----------------------
    23 ||12/08/16 || MS || ~~Only a 'latent' bug, however, in case of {{{topography = .T. }}} initialization of the PALM grid does not scale with the number of processors, as two global arrays required only (!) for NetCDF output are necessary (zu_s_inner, zw_w_inner). If you are short on internal memory, it is possible that the required memory exceeds the available memory in case of very large grids.~~  '''Fixed in -r2231.''' ||
     3||='''Date'''  =||='''Reported by'''  =||='''Description'''  =|| ||
    244|----------------------
    255||13/06/16 || MS || '''Only if [../../app/inipar#masking_method masking_method] = .T.:''' Over-determination of Neumann boundary condition of perturbation pressure in poismg_noopt.f90 if a grid point within topography adjoins to two or more 'flow' grid points. This case, Neumann boundary conditions are not correctly set for the 'flow' grid points as the perturbation pressure inside topography is an average over all the adjoining 'flow' grid points. At this point it should be noted that is '''is not''' the reason for the velocity blow-up in case of complex topography.  ||
     
    288|----------------------
    299||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 [../../app/inipar#psolver psolver] = 'multigrid_noopt' and [../../app/inipar#masking_method masking_method] = .F. can lead to a blow up of wind velocity. Please see [#remark1 remarks] below. ||
    30 |----------------------
    31 ||09/05/16 || MS || In case of [../../app/inipar#topography topography] = .T., different processor topologies do not yield identical results. ||
    32 |----------------------
    33 ||~~18/04/12~~ || ~~MS~~ || ~~The use of the cache-optimized and the vector-optimized Palm versions do not yield identical results with topography.~~ ~~'''Reason:''' Different treatment of array rif_wall in cache and vector version in wall_fluxes. In vector version rif_wall is update after each component in prognostic equations, whereas in cache version old and updated values are mixed, leading to slightly different results in wall_fluxes_e.~~ '''Fixed in -r2231.''' ||
    3410
    3511\\\\