[MOAB-dev] Using Mesquite with MOAB

[Tim Tautges]

Jason Kraftcheck wrote:
>> I think we really need to be able to fire up an iMesh instance from an
>> existing MBInterface*, for cases where the iMesh API is more convenient;
>> I just ran across such a case last week, where I needed connectivities
>> as an array with offsets.  In what way does iMesh constrain the MOAB
>> data model, or is it more of an implementation issue that we could correct?
>>
> 
> The first example that comes to mind is the handling of the creation of
> lower-dimension entities (all the stuff with setAdjTable).
> 

That's pretty minor; are there other examples?  The main concern here would be to be able to access iMesh functions from 
MOAB-based applications, and to expose MOAB data to services implemented on iMesh.

- tim

> 
>> Having to construct a MOAB-specific API for Mesquite just because the
>> application isn't completely iMesh-based blows a big part of our
>> interoperability argument in ITAPS.
>>
> 
> Then we need to move the setAdjTable functionality (and any other such
> things) into MOAB core.
> 
> - jason
> 

-- 
================================================================
"You will keep in perfect peace him whose mind is
   steadfast, because he trusts in you."               Isaiah 26:3

              Tim Tautges            Argonne National Laboratory
          (tautges at mcs.anl.gov)      (telecommuting from UW-Madison)
          phone: (608) 263-8485      1500 Engineering Dr.
            fax: (608) 263-4499      Madison, WI 53706