#747 BoundarySegmentIndex does not work for parallel YaspGrid
Metadata
Property | Value |
---|---|
Reported by | Martin Nolte (nolte@mathematik.uni-freiburg.de) |
Reported at | Mar 1, 2010 17:14 |
Type | Bug Report |
Version | Git (pre2.4) [autotools] |
Operating System | Unspecified / All |
Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
Last edited at | Mar 22, 2010 17:30 |
Closed by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
Closed at | Mar 22, 2010 17:30 |
Closed in version | 2.0 |
Resolution | Fixed |
Comment | and merged |
Description
When running the gridcheck for YaspGrid in parallel (e.g., with 2 processes), the boundary segment index is reported to not be a unique, zero-based, consecutive index on the macro level.
This is reproduced by running (in dune-grid/dune/grid/test) mpiexec -np 2 ./test-yaspgrid