The MeshView.cell_map() and vertex_map() methods have a value of 0 when there is no connection - however 0 could be the index of a cell or vertex that is connected - so we need to check for this. Also, there is a message that pops up when a connection can't be found (which is very often when a surface mesh is a superset of the boundary of a volume mesh), this leads to thousands of messages which fill the screen and make it difficult to see what stubs is doing.
BoundingBoxTree() MPI bug (#38)
These will be fixed in the forked repository:
https://github.com/justinlaughlin/dolfinstubs/issues/new
The MeshView.cell_map() and vertex_map() methods have a value of 0 when there is no connection - however 0 could be the index of a cell or vertex that is connected - so we need to check for this. Also, there is a message that pops up when a connection can't be found (which is very often when a surface mesh is a superset of the boundary of a volume mesh), this leads to thousands of messages which fill the screen and make it difficult to see what stubs is doing.
BoundingBoxTree() MPI bug (#38)
These will be fixed in the forked repository:
https://github.com/justinlaughlin/dolfinstubs/issues/new