#1341 Prune the BasicGeometry code
Metadata
Property | Value |
---|---|
Reported by | Oliver Sander (oliver.sander@tu-dresden.de) |
Reported at | Aug 27, 2013 10:13 |
Type | Bug Report |
Version | Git (pre2.4) [autotools] |
Operating System | Unspecified / All |
Last edited by | Christoph Grüninger (gruenich@iws.uni-stuttgart.de) |
Last edited at | Jun 21, 2014 16:43 |
Closed by | Christoph Grüninger (gruenich@iws.uni-stuttgart.de) |
Closed at | Jun 21, 2014 16:43 |
Closed in version | Unknown |
Resolution | Fixed |
Comment |
Description
The BasicGeometry implementation provides a lot of functionality:
- Geometry implementations both for static and run-time element types
- Taking boundary traces of elements
- An implementation of reference elements taking a static topology id to identify the element type.
- Probably even more stuff, which I don't know about
Point 1) has been largely superseded by MultilinearGeometry and friends. Therefore, it looks like a considerable part of the BasicGeometry code is obsolete and may be a candidate for removal. Easiest would be to delete the whole thing, but before doing that I'd like some information about 2) and 3). Does anybody use the trace feature at all?
If the static reference elements are used (they do sound like a good idea), shouldn't they be in a file staticreferencelements.hh, on par with referenceelements.hh?
These issues may need a discussion at the next meeting.