Jason, It is a strong function of how one would support the mesh in parallel. I do know how I would do partitioning and dynamic re-partitioning (to account for contact evolution) for efficient parallel simulation using iMeshP's FMDB implementation and the issue of where the mesh instance is defined creates no problem at all. Mark Jason Kraftcheck wrote:
Mark,
I think that having one iMesh instance per Part would be problematic for "contact"-type problems. If I understand the nature of the problem correctly, there are two partitioning of the mesh: one that distributes volume elements and one that distributes 2D elements on interfaces. If there were multiple (for simplicity lets say two) iMesh instances for a single process where one contains the volume elements and one contains the 2D elements then there would be no way to obtain information about the relation between the 2D elements and the volume elements.
- jason