itaps-parallel Mesh Instances

[Carl Ollivier-Gooch]

Devine, Karen D. wrote:
> Hi, Mark.
> 
> Thanks for your email contributing to this discussion.  (Thanks to Carl,
> too!)
> 
> It is funny how differently people can read the same email.  I saw Carl's
> response as an additional use-case, adding, as he said, complexity but not
> providing an answer to my questions about mesh instances.  I agree that for
> Carl's example, it is natural to store many submeshes in a single database.
> But I keep coming back to the example of a loosely-coupled physics
> simulation on multiple distinct meshes, where I think having multiple mesh
> instances is more natural.

I agree with you on this last point, Karen, especially since it's 
entirely possible that the mesh instances for the fluids mesh and the 
solids mesh in a fluid-structure problem could be provided by the fluids 
app and the solids app as minimal iMesh implementations.  Those are 
going to be mutually incompatible with each other in terms of stuffing 
them into the same backend (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).

On the other hand, each of those instances individually might be a 
"simple mesh" or something way more complex....

Carl

-- 
------------------------------------------------------------------------
Dr. Carl Ollivier-Gooch, P.Eng.                   Voice: +1-604-822-1854
Associate Professor                                 Fax: +1-604-822-2403
Department of Mechanical Engineering             email: cfog at mech.ubc.ca
University of British Columbia              http://www.mech.ubc.ca/~cfog
Vancouver, BC  V6T 1Z4                  http://tetra.mech.ubc.ca/ANSLab/
------------------------------------------------------------------------