Andrea Franceschini

I created a simpler version that should just duplicate the nodes alone a fracture of an unstructured mesh. Because the `surfaceGenerator` function call `TwoPointFluxApproximation` that requires the `pressure` field to...

To be more precise, I prepared [this test case](https://github.com/GEOSX/GEOSX/files/4361040/crack_flow.txt), that defines the `pressure` field, in such a way that the simulation can reach the end. Running with the configuration `mpirun...

I really don't know what can be the cause, but ... can it be something similar to #663?

I realized that the issue is **not** related with `Surface Generator`. The problem can be reproduced even without the `SurfaceGenerator` step. Running `mpirun -np 3 geosx -i file` this pair...

Working with [this mesh](https://github.com/GEOSX/GEOSX/files/4410371/crack02.txt) and 2 processes, I realized that the fracture nodes are properly split only on one process (rank 0), while it seems that rank 1 sees the...

Yes, that's the [file](https://github.com/GEOSX/GEOSX/files/4411312/crack_flow2.txt). It's a simple flow simulation that, with `develop` branch, and `mpirun -np 2` produces: ``` Rank 0: 0 3 37 465 81 1639 1676 1711 1654...

> I realized that the issue is **not** related with `Surface Generator`. The problem can be reproduced even without the `SurfaceGenerator` step. Running `mpirun -np 3 geosx -i file` this...

For unstructured grids, the parallel surface generator still has problems, such as the inconsistency across ranks of the splitting.

> The fracture is propagating along a partition boundary Can it be related to #1000?

For the contact relation I'm using I don't need any table of this sort, so I'm fine with the second solution, i.e., enforcing the usual way to access the tables.