wrong boundary Segment Indices in 2d
The 2d grid uses the boundary segment indices from its underlying 3d grid. Unfortunately, the numbers of the fake faces are not the last ones, so that the boundary segment index becomes non-consecutive. Attached is a small example triggering the bug.
Example output looks as follows:
Reading 2d Gmsh grid...
version 2.2 Gmsh file detected
file contains 4 nodes
file contains 5 elements
number of real vertices = 4
number of boundary elements = 4
number of elements = 1
WARNING (ignored): Could not open file 'alugrid.cfg', using default values 0 < [balance] < 1.2, partitioning method 'ALUGRID_SpaceFillingCurve(9)'.
You are using DUNE-ALUGrid, please don't forget to cite the paper:
Alkaemper, Dedner, Kloefkorn, Nolte. The DUNE-ALUGrid Module, 2016.
Created parallel ALUGrid<2,2,cube,nonconforming> from input stream.
Number of boundary segments: 4
Boundary Segment Index : 2 Factory Insertion Index : 3
Boundary Segment Index : 3 Factory Insertion Index : 1
Boundary Segment Index : 0 Factory Insertion Index : 0
Boundary Segment Index : 5 Factory Insertion Index : 2
You are using DUNE-ALUGrid, please don't forget to cite the paper:
Alkaemper, Dedner, Kloefkorn, Nolte. The DUNE-ALUGrid Module, 2016.
An additional output in the constructor of HBnd4Top reveals the folloing indices:
constructed hbnd4 with vertices = [ vx ( 0 : 0 1 0 ) vx ( 1 : 0 1 1 ) vx ( 3 : 0 0 1 ) vx ( 2 : 0 0 0 ) ], index = 0
constructed hbnd4 with vertices = [ vx ( 0 : 0 1 0 ) vx ( 2 : 0 0 0 ) vx ( 4 : 1 0 0 ) vx ( 6 : 1 1 0 ) ], index = 1
constructed hbnd4 with vertices = [ vx ( 0 : 0 1 0 ) vx ( 1 : 0 1 1 ) vx ( 7 : 1 1 1 ) vx ( 6 : 1 1 0 ) ], index = 2
constructed hbnd4 with vertices = [ vx ( 2 : 0 0 0 ) vx ( 3 : 0 0 1 ) vx ( 5 : 1 0 1 ) vx ( 4 : 1 0 0 ) ], index = 3
constructed hbnd4 with vertices = [ vx ( 1 : 0 1 1 ) vx ( 3 : 0 0 1 ) vx ( 5 : 1 0 1 ) vx ( 7 : 1 1 1 ) ], index = 4
constructed hbnd4 with vertices = [ vx ( 4 : 1 0 0 ) vx ( 5 : 1 0 1 ) vx ( 7 : 1 1 1 ) vx ( 6 : 1 1 0 ) ], index = 5