#834 Edge orientation in reference element/cell
Metadata
| Property | Value |
|---|---|
| Reported by | Sebastian Goetschel (goetschel@zib.de) |
| Reported at | Oct 29, 2010 09:06 |
| Type | Bug Report |
| Version | 2.0 |
| Operating System | Unspecified / All |
| Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Last edited at | Nov 2, 2010 17:33 |
| Closed by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Closed at | Nov 2, 2010 17:33 |
| Closed in version | Unknown |
| Resolution | Not a bug |
| Comment |
Description
When accessing the faces of a triangle in 2d, and getting global coordinates for a given local coordinate, the result for a certain edge is different when using the reference element. The orientation of one of the edges is different than the orientation of the edge in the reference element. That is, geometryInInside().global(local) and referenceElement.global<1>(local,indexInInside(),1) give different results for the same local coordinate on that edge.
The attached example program yields the following output:
[...] geoInInside.type = (simplex, 1) with corners (0 1), (0 0) corners in reference element (0 0), (0 1) loc = 0.11 glob = (0 0.89) in refElem = (0 0.11)
All other edges are oriented as in the element.
When an intersection covers the whole codim 1 subentity, should its geometry in the cell not be the same as specified in the reference element?