itaps-parallel Notes from today's meeting

[Mark Beall]

Jason,

Assuming that the two partitions are not 100% correlated (the  
interface elements are not on the same processors as their associated  
volume elements), I think you have the same problem with the current  
design. The interface elements will be copies on different processors  
in the second partition. If someone has a way to avoid this, feel free  
to point it out since it's the basis of my entire argument here.

If the two partitions are 100% correlated, then it's the same as if  
you were doing it in serial and in that case I don't see that you  
would want to use a partition to represent the interface elements,  
you'd just use a mesh entity set.

mark

On Apr 13, 2010, at 10:24 AM, 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