itaps-parallel copy information stored in iMesh

[Mark Miller]

Hi All,

 

On page 16 of Karen's talk made at the ITAPS bootcamp on monday,

we all agreed on the 'Duplicated information for copies' which was

- owner of an entity knows part-/entity-handles of all its copies

- all copies know remote part-/entity-handle of the owned entity

- all boundary entities know part-/entity-handles of all its copies

 

While I can understand that portions of this information are useful

for various applications that may need to modify the mesh, none

of it is useful for read-only applications, like a viz. tool. So,

I'd like to make a pitch to allow applications to indicate to iMesh

if some or all of this information is needed. In other words, will

the application even engage in the operations for which we determined

this information is essential? If not, then why are we going to the

trouble of storing it? Yes, viz-tools need ghost entities. And, viz-tools

need the ability to create ghost entities (as well as tag or field

data defined on those entities). But, viz-tools don't need a concept

of 'owner' for an entity nor do they need to know where all

the copies of entities are. Its extra information they don't need.

Even though its only going to happen on the 'boundaries', its still

worth NOT storing it if we don't need it.

 

Mark

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/itaps-parallel/attachments/20080312/529de78e/attachment.htm>