#449 arbitrary reference elements
Metadata
| Property | Value |
|---|---|
| Reported by | Andreas Dedner (A.S.Dedner@warwick.ac.uk) |
| Reported at | Oct 28, 2008 17:24 |
| Type | Feature Request |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Last edited at | Jan 20, 2010 21:52 |
| Closed by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Closed at | Jan 20, 2010 21:52 |
| Closed in version | 2.0 |
| Resolution | Fixed |
| Comment | Implemented |
Description
There is some interest for support of
- arbitrarily formed grid elements
- subdivision of these elements into parts with reference elements (for quadrature over these parts). This is required both for entities as well as for intersections.
A suggestion for both points:
Add two new reference element types: NONE: there exists no reference element and there is nothing to be done about it. SUBDIVIDED: there is no reference element but there exists an iterator which provides a set of geometries which all (must) have reference elements and which cover the whole entity/intersection. In both cases the geometry returned directly from the entity/intersection is the identity mapping (the element itself is its reference element). In the first case only operator[] and volume are really meaningful. In the second case a iterator is provided (from the geometry for example) which iterates over a sequence of dune geometries having real reference elements.
The implementation for existing codes is almost zero since they all have reference elements and the subdivision iterator either has begin()==end() or return a single item which is identical to the already implemented geometry.