Interpolation to/from sub-meshes causes parallel deadlock about dolfinx HOT 3 CLOSED

Issue is that since we do not associate any relationships between meshes in the objects, it gets problematic to distinguish between non-matching meshes and a sub-mesh parent mesh relation when one has no cells on a process for:

1. Have parent cells, no submesh cells

2. No parent cells, no submesh cells (no cells for either nonmatching grid).

3. Is easy to fix, 2, however, is challenging to fix without adding a flag to interpolate stating if we want to call non-matching interpolation (as this uses mpi communication).

from dolfinx.

Issue is that since we do not associate any relationships between meshes in the objects, it gets problematic to distinguish between non-matching meshes and a sub-mesh parent mesh relation when one has no cells on a process for:

1. Have parent cells, no submesh cells
2. No parent cells, no submesh cells (no cells for either nonmatching grid).
3. Is easy to fix, 2, however, is challenging to fix without adding a flag to interpolate stating if we want to call non-matching interpolation (as this uses mpi communication).

The first problem seems to be that the code conflates None and len(foo) == 0, which breaks when a sub-mesh has no cells on a rank. This is a failure in logic.

The second is a design failure - one function doing too many different things. And it's not clear from the argument descriptions what is going on.

Unless there is an easy and good fix, the change should probably be wound back until it can done properly.

from dolfinx.

Working on a fix where a user that wants non-matching interpolation has to pass in an enum indicating this. Should not affect usage of normal interpolation

from dolfinx.