#427 generic reference elements
Metadata
Property | Value |
---|---|
Reported by | Andreas Dedner (A.S.Dedner@warwick.ac.uk) |
Reported at | Sep 10, 2008 13:40 |
Type | Feature Request |
Version | Git (pre2.4) [autotools] |
Operating System | Unspecified / All |
Last edited by | Martin Nolte (nolte@mathematik.uni-freiburg.de) |
Last edited at | May 7, 2009 11:06 |
Closed by | Martin Nolte (nolte@mathematik.uni-freiburg.de) |
Closed at | May 7, 2009 11:06 |
Closed in version | Unknown |
Resolution | Implemented |
Comment |
Description
We have implemented generic geometries for all existing reference elements and also for simplex elements for dimension > 3 (as decided in Berlin). The implementation and an incomplete docu also describing the numbering convention is in grid/genericgeometry
But we were not able to generically reproduce the same numbering of all subentities used in the dune reference elements.
Q: should we switch to new reference elements?
Remarks to the different geometry types: (*,1): no change (simplex,2): no change except codim 1 subentites are numbered 2-i (cube,2): no change (simplex,3): changes only for codim 1: numbered 3-i 2: complex change but renumbering available (cube,3): changes only for codim 2: as for simplex (pyramid,3): changes for all codims: the numbering in dune is not very consistent for example in the bottom face with the 2d cube... (prisma,3): changes in codims 1 and 2. (cube,n): changes for all codim except 0,1,dim but no renumbering yet available. Note: the sub-sub-entity numbering is inconsistent in most cases.
Suggestion:
- we would like to change the pyramids and the prisma in 3d and introduce new simplex reference elements for dim>3.
- it would be nicely consistent to change the (simplex,2) and (simplex,3) numbering.
- We need to implement the renumbering for the dune cubes (Peter could you give us a description for the dune reference cubes?)