[MOAB-dev] r4673 - MOAB/branches/Version4.0
jvporter at wisc.edu
jvporter at wisc.edu
Mon Mar 28 21:21:41 CDT 2011
Author: jvporter
Date: 2011-03-28 21:21:41 -0500 (Mon, 28 Mar 2011)
New Revision: 4673
Added:
MOAB/branches/Version4.0/README.IMESH
Modified:
MOAB/branches/Version4.0/
Log:
Merge r4672 to 4.0 branch
Property changes on: MOAB/branches/Version4.0
___________________________________________________________________
Modified: svn:mergeinfo
- /MOAB/trunk:4610-4611,4628,4631,4640-4641,4646,4663,4670
+ /MOAB/trunk:4610-4611,4628,4631,4640-4641,4646,4663,4670,4672
Copied: MOAB/branches/Version4.0/README.IMESH (from rev 4672, MOAB/trunk/README.IMESH)
===================================================================
--- MOAB/branches/Version4.0/README.IMESH (rev 0)
+++ MOAB/branches/Version4.0/README.IMESH 2011-03-29 02:21:41 UTC (rev 4673)
@@ -0,0 +1,59 @@
+MOAB iMesh Interface Implementation, iMesh v1.2
+===============================================
+
+1. Non-compliant iMesh functionality:
+
+1.1 Iterators for list-type entity sets:
+
+The iMesh 1.2 specification requires that iterators over list-type entity sets be updated
+in response to membership changes in the set. Specifically, if entities are added to or
+removed from the set, the spec requires that added entities be iterated without needing to
+reset the iterator, and that removed entities not be iterated. MOAB will not support this
+capability in the iMesh 1.2 release. Future support will depend on whether this can be
+implemented efficiently, without degrading performance for static mesh applications.
+
+1.2 No support for septahedron entities:
+
+MOAB does not support septahedron entities at this time (though such entities could be
+represented as general polyhedra).
+
+2. MOAB capabilities not accessible through iMesh:
+
+2.1 Dense tags: MOAB supports two kinds of tag storage: dense tags, where tag values are
+stored in sequence for sequences of contiguous entity handles; and sparse tags, which are
+stored in (entity handle, tag value) tuples. iMesh does not support creation of a tag
+with a default value, nor does it have a mechanism for passing general options to the tag
+creation function. Therefore, MOAB's iMesh implementation creates sparse tags by
+default. Alternatives for specifying the tag creation type will be explored for future
+iMesh releases.
+
+2.2 Variable-length tags: MOAB supports a variable-length tag, where a tag value can have
+a different length for each entity to which it is assigned. This functionality is not
+supported in iMesh.
+
+2.3 Direct access to tag data (tag_iterate functionality): MOAB 4.0.1 introduced the
+ability for applications to get direct access to tag storage for dense-type tags (see the
+tag_iterate function in src/moab/Interface.hpp). This functionality is not supported in
+iMesh.
+
+2.4 Corner vs. all vertices in connectivity list: MOAB represents so-called "higher-order
More information about the moab-dev
mailing list