From: Wolfgang Bangerth Date: Wed, 29 Mar 2006 03:29:37 +0000 (+0000) Subject: Remove untrue assertion in documentation. X-Git-Tag: v8.0.0~11967 X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=78d7a8f27377718062ac0bd3f373baae8993c970;p=dealii.git Remove untrue assertion in documentation. git-svn-id: https://svn.dealii.org/trunk@12748 0785d39b-7218-0410-832d-ea1e28bc413d --- diff --git a/deal.II/deal.II/include/grid/tria_levels.h b/deal.II/deal.II/include/grid/tria_levels.h index f64b39a0e1..2fe525e7e0 100644 --- a/deal.II/deal.II/include/grid/tria_levels.h +++ b/deal.II/deal.II/include/grid/tria_levels.h @@ -47,19 +47,18 @@ namespace internal * Store all information which belongs to one level of the multilevel * hierarchy. * - * In TriaLevel<0> all data is stored which is not - * dependent on the dimension, e.g. a field to store the - * refinement flag for the cells (what a cell actually is - * is declared elsewhere), etc. Actually, it is only cell-based - * data, like neighborship info or refinement flags. There is another - * field, which may fit in here, namely the material data (for cells) - * or the boundary indicators (for faces), but since we need for a line - * or quad either boundary information or material data, we store them - * with the lines and quads rather than with the common data. We may, - * however lose some memory in three dimensions, when we need the - * material data for cell, boundary data for the quads, but nothing - * for the lines. Since we only store one byte per line, quad or hex, - * this is a minor loss and we can live with that. + * In TriaLevel<0> all data is stored which is not dependent on the + * dimension, e.g. a field to store the refinement flag for the cells + * (what a cell actually is is declared elsewhere), etc. Actually, it + * is only cell-based data, like neighborship info or refinement + * flags. There is another field, which may fit in here, namely the + * material data (for cells) or the boundary indicators (for faces), + * but since we need for a line or quad either boundary information or + * material data, we store them with the lines and quads rather than + * with the common data. Likewise, in 3d, we need boundary indicators + * for lines and quads (we need to know how to refine a line if the + * two adjacent faces have different boundary indicators), and + * material data for cells. * * @ingroup grid * @author Wolfgang Bangerth, 1998