Changes between Version 29 and Version 30 of doc/tec/bugs

Timestamp:

Jul 3, 2017 2:16:07 PM (8 years ago)

Author:

suehring

Comment:

--

doc/tec/bugs

@@ -3 +3 @@
 ||='''Date'''  =||='''Reported by'''  =||='''Description'''  =||
 |----------------------
-||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).
+||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'''. ||
 |----------------------
 ||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).
@@ -11 +11 @@
 ||28/04/17 || MS || Spectra: wavenumber do not match theoretical value (Pi/dx) at grid cut-off length 
 |----------------------
-||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
+||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.'''
 |----------------------
-||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'''.
+||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'''.
 |----------------------
-||18/10/16 || MS || Output of initial profile of passive scalar quantity #s is not correct. ||
+||18/10/16 || MS || ~~Output of initial profile of passive scalar quantity #s is not correct.~~ ||
 |----------------------
-||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.  ||
+||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.''' ||
 |----------------------
-||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. ||
+||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.  ||
 |----------------------
 ||13/06/16 || MS || Less divergence reduction with [../../app/inipar#masking_method masking_method] = .T. compared to [../../app/inipar#masking_method masking_method] = .F. . Please see [#remark2 remarks] below. ||
@@ -27 +27 @@
 ||09/05/16 || MS || In case of [../../app/inipar#topography 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 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. ||
+||~~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.''' ||
 
 \\\\