[MOAB-dev] Getting ent set data when tag_size > 1

[James Porter]

There are also places where interleaved storage seems to be preferred,
e.g. iMesh_createVtxArr:
<http://trac.mcs.anl.gov/projects/ITAPS/browser/MOAB/trunk/itaps/imesh/iMesh_MOAB.cpp#L1254>

Whether the internal memory structure is interleaved or not, the blocked
versions of every function I see are more complicated than the
interleaved versions. It seems like the "default" really is interleaved,
even if it's organized differently in memory.

- Jim

On Sun, 2010-04-18 at 10:51 -0500, Tim Tautges wrote:
> Well, it's something I've wondered about, actually.  In cases where you want to read in interleaved data directly, that 
> requires duplicating storage (or very fine-grained reads).  Conversely, if the storage is blocked, MOAB can read 
> coordinates directly into its native storage.  This can be significant for large meshes.
> 
> - tim
> 
> Jed Brown wrote:
> > On Sat, 17 Apr 2010 17:20:21 -0500, Tim Tautges <tautges at mcs.anl.gov> wrote:
> >> Actually, it's blocked; see VertexSequence constructor.
> > 
> > Goes to show what I know...
> > 
> > Jed
> > 
>