#1502 global/local of geometryInFather is buggy
Metadata
Property | Value |
---|---|
Reported by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
Reported at | Sep 29, 2014 14:26 |
Type | Bug Report |
Version | Git (pre2.4) [autotools] |
Operating System | Unspecified / All |
Last edited by | Dominic Kempf (dominic.r.kempf@gmail.com) |
Last edited at | Sep 29, 2014 16:46 |
Closed by | Dominic Kempf (dominic.r.kempf@gmail.com) |
Closed at | Sep 29, 2014 16:46 |
Closed in version | 2.4 |
Resolution | Not a bug |
Comment | test fixed in |
ef053414610f8a1d8aba8d4f6ea74520fbcb3365 |
Description
I added a test case to checkgeometryinfather. It is sufficient to run test-yaspgrid to verify the problem. The bug is not fatal, as we currently have no way to distinguish between non-nested (e.g. boundary-adapted) meshes and those where the relation must be fulfilled stricktly.
This bug is really nasty, as it can result in very wrong results, e.g. when employing geometric multigrid computations.