itaps-parallel Mesh Instances

[Mark Miller]

Hi Carl,

So, 'merging' means to have both meshes managed by a single instance
with perhaps different entity sets being used to keep them distinct? And,
'co-existence' is both meshes existing as separate instances but behind
a 'multiplexor' that keeps the two instances distinct? I like this terminology.

However, and not to de-rail the discussion of what a 'mesh' is in the ITAPS
context but I didn't see how Jason's solution permitted 'co-existance'. I
thought with a single iMesh isntance, you could have it be an A implementation
or a B implementation but that a single instance held by
the application could NOT be hold both an A and a B implementation simultaneously.
Was I wrong in that understanding? If it could, I didn't see any way for the
application to give the API a handle to that single instances and then say it
wants to act on the A one or the B one. Am I missing something here?

Mark



Carl Ollivier-Gooch wrote:

> (except possibly by multiplexing, although
> Jason's earlier solution for that, as I recall, was aimed at
> co-existence of two instances, not merging of two instances).
>

--
Mark C. Miller, Lawrence Livermore National Laboratory
email: mailto:miller86 at llnl.gov
(M/T/W) (925)-423-5901 (!!LLNL BUSINESS ONLY!!)
(Th/F)  (530)-753-8511 (!!LLNL BUSINESS ONLY!!)