#170 UGGrid has inconsistent subIndex<1> on incomplete levels
Metadata
| Property | Value |
|---|---|
| Reported by | Oliver Sander (oliver.sander@tu-dresden.de) |
| Reported at | Aug 9, 2006 10:06 |
| Type | Bug Report |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Last edited at | Oct 18, 2006 08:27 |
| Closed by | Oliver Sander (oliver.sander@tu-dresden.de) |
| Closed at | Nov 7, 2006 09:47 |
| Closed in version | 1.0 |
| Resolution | Fixed |
| Comment | This is a UG bug. A workaround has been committed in dune-grid patch 3246. Actually fixing this in UG will take more time. |
Description
The test for consistent numbering of faces
assert(indexSet.template subIndex<1>(*eIt, numberInSelf) == indexSet.template subIndex<1>(*outside, numberInNeighbor));
(checkintersectionit.cc:41
when seen from the two neighboring elements fails for the level index of 3d UGGrid on levels which cover the domain only partially.
UGGrid stores the index for faces in a SideVector object, which is supposedly attached to faces in the grid. However, there appear cases where two elements which are clearly adjacent (they share 3 nodes) do not share any SideVectors. Hence the numbering algorithm goes wrong.
This will need more researching. Until then, expect your higher-order methods to go wrong on UGGrid.