[MOAB-dev] commit/MOAB: iulian07: remove PARTITION_PART from documentation; Its role is now taken by PARALLEL_PARTITION

commits-noreply at bitbucket.org commits-noreply at bitbucket.org
Thu Aug 29 13:21:35 CDT 2013


1 new commit in MOAB:

https://bitbucket.org/fathomteam/moab/commits/5dbd712d0277/
Changeset:   5dbd712d0277
Branch:      master
User:        iulian07
Date:        2013-08-29 20:14:49
Summary:     remove PARTITION_PART from documentation; Its role is now take=
n by PARALLEL_PARTITION
The former role of PARALLEL_PARTITION is now taken by PARALLEL_PARTITIONING=
_TAG_NAME (it is the tag for
the parent set that has children sets corresponding to parts in the partiti=
on)

 correct spelling error in the name of the tag
PARALLEL_PARTITIONING_TAG_NAME

Affected #:  3 files

diff --git a/doc/MetaData/metadata.h b/doc/MetaData/metadata.h
index 3e822b9..84aaf87 100644
--- a/doc/MetaData/metadata.h
+++ b/doc/MetaData/metadata.h
@@ -129,13 +129,13 @@ Data: Entity sets; Tag(s): DIRICHLET_SET/I, NEUMANN_S=
ET/I)
 Boundary conditions are often specified in terms of geometric model entiti=
es, similar to material types.  MOAB uses entity sets to store this informa=
tion as well.  The DIRICHLET_SET and NEUMANN_SET tags are used to represent=
 Dirichlet- and Neumann-type boundary condition sets, resp.  By convention,=
 Neumann sets usually contain (indirectly) intermediate-dimension entities =
like edges in a 2D mesh or faces in a 3D mesh, while Dirichlet sets usually=
 contain vertices.  In addition, Neumann sets are represented as sets of fa=
ces, rather than as sides of elements.  Faces can be ordered =E2=80=9Cforwa=
rd=E2=80=9D or =E2=80=9Creverse=E2=80=9D with respect to one of the boundin=
g elements, depending on whether the right-hand normal points into or out o=
f the element.  Forward-sense faces are added to the Neumann set.  Reverse-=
sense faces are put into a separate set; that set is tagged with the NEUSET=
_SENSE tag, with value =3D -1; and that reverse set is added to the Neumman=
n set.
=20
 <H3> Parallel Mesh Constructs </H3>
-(Data: Entity sets, entities; Tag(s): PARALLEL_PART/I, PARALLEL_PARTITION/=
I, PSTATUS/C*1, PARALLEL_SHARED_PROC/I, PARALLEL/SHARED_HANDLE/H, PARALLEL_=
SHARED_PROCS/I*NP, PARALLEL_SHARED_HANDLES/H*NP)
+(Data: Entity sets, entities; Tag(s): PARALLEL_PARTITION/I, PSTATUS/C*1, P=
ARALLEL_SHARED_PROC/I, PARALLEL/SHARED_HANDLE/H, PARALLEL_SHARED_PROCS/I*NP=
, PARALLEL_SHARED_HANDLES/H*NP)
=20
 On a parallel computer, MOAB can represent the mesh on each processor as w=
ell as information about entities shared with neighboring processors.  Some=
 of this information is also relevant even when the mesh is represented on =
a serial machine.  MOAB uses several tag and set conventions to describe th=
e parallel nature of a mesh.  This information is summarized here; for a mo=
re complete description of MOAB=E2=80=99s parallel mesh representation and =
functionality, see [ref-moabpar].
=20
 - <B> Parallel partition, parts </B>
=20
-Most parallel mesh applications use a domain decomposition approach, where=
 each processor solves for a subset of the domain.  The set of entities sol=
ved by a given processor is referred to as a part, and the collection of pa=
rts together is called the partition.  MOAB stores each part in an entity s=
et, marked with the PARALLEL_PART tag, whose value is the rank of the proce=
ssor assigned that part; an entity set which contains all part sets is give=
n the PARALLEL_PARTITION tag, whose value is currently meaningless.  The MB=
Zoltan tool included as a tool in MOAB can partition a mesh for parallel so=
lution, and writes the partition to the mesh in the form of parts and parti=
tions.  Both these types of sets can be accessed in a serial mesh, e.g. for=
 visualization.
+Most parallel mesh applications use a domain decomposition approach, where=
 each processor solves for a subset of the domain.  The set of entities sol=
ved by a given processor is referred to as a part, and the collection of pa=
rts together is called the partition.  MOAB stores each part in an entity s=
et, marked with the PARALLEL_PARTITION tag, whose value is the rank of the =
processor assigned that part; an entity set which contains all part sets is=
 given the PARALLEL_PARTITIONING_TAG_NAME tag, whose value is currently mea=
ningless.  The MBZoltan tool included as a tool in MOAB can partition a mes=
h for parallel solution, and writes the partition to the mesh in the form o=
f parts and partitions.  Both these types of sets can be accessed in a seri=
al mesh, e.g. for visualization.
=20
 - <B> Part interfaces </B>
=20
@@ -273,7 +273,7 @@ GEOM_SENSE_N_SENSES/I*N</td><tr><td>Parallel mesh const=
ructs</td><td>E, S</td>
-<td>PARALLEL_PART/I, PARALLEL_PARTITION/I, PSTATUS/C*1, PARALLEL_SHARED_PR=
OC/I, PARALLEL/SHARED_HANDLE/H, PARALLEL_SHARED_PROCS/I*NP, PARALLEL_SHARED=
_HANDLES/H*NP</td>
+<td>PARALLEL_MESH_PARTITIONING/I, PARALLEL_PARTITION/I, PSTATUS/C*1, PARAL=
LEL_SHARED_PROC/I, PARALLEL/SHARED_HANDLE/H, PARALLEL_SHARED_PROCS/I*NP, PA=
RALLEL_SHARED_HANDLES/H*NP</td><td> Data which describes parallel mesh</td>=
</tr><tr>
@@ -380,19 +380,19 @@ GEOM_SENSE_N_SENSES/I*N</td><td>Entities or sets with=
 common boundary condition </td></tr><tr>
-<td>PARALLEL_PART </td>
+<td>PARALLEL_PARTITION </td><td>I</td><td>S</td><td>Represent a part in a =
partition</td></tr><tr>
-<td>PARALLEL_PARTITION</td>
+<td>PARALLEL_MESH_PARTITIONING</td><td>I</td><td>S</td><td>Represents a pa=
rtition of the mesh for parallel solution, which is a collection of parts</=
td></tr><tr>
-<td>__PARALLEL_SHARED_HANDLEd</td>
+<td>__PARALLEL_SHARED_HANDLE</td><td>H</td><td>E, S</td><td> Handle of thi=
s entity/set on sharing processor</td>

diff --git a/itaps/imesh/iMeshP_MOAB.cpp b/itaps/imesh/iMeshP_MOAB.cpp
index ab45811..e554fba 100644
--- a/itaps/imesh/iMeshP_MOAB.cpp
+++ b/itaps/imesh/iMeshP_MOAB.cpp
@@ -350,7 +350,7 @@ void iMeshP_createPartitionAll( iMesh_Instance instance,
   *partition_handle =3D 0;
=20
   Tag prtn_tag;
-  ErrorCode rval =3D MOABI->tag_get_handle( PARALLEL_PARITIONING_TAG_NAME,
+  ErrorCode rval =3D MOABI->tag_get_handle( PARALLEL_PARTITIONING_TAG_NAME,
                                           1, MB_TYPE_INTEGER,
                                           prtn_tag,
                                           MB_TAG_SPARSE|MB_TAG_CREAT );

diff --git a/src/parallel/MBParallelConventions.h b/src/parallel/MBParallel=
Conventions.h
index abda367..255eb9a 100644
--- a/src/parallel/MBParallelConventions.h
+++ b/src/parallel/MBParallelConventions.h
@@ -17,7 +17,7 @@
 /** \brief Tag on a meshset representing a parallel partition.
  *
  * When the mesh is partitioned for use in a parallel environment,
- * the each CPUs partiiton of the mesh is stored in a meshset with
+ * the each CPUs partition of the mesh is stored in a meshset with
  * this tag.  The value of the tag is an integer "part identifier".
  */
 #define PARALLEL_PARTITION_TAG_NAME "PARALLEL_PARTITION"
@@ -29,13 +29,13 @@
  * This tag labels an entity set for which the child sets are part(ition)s
  * that together are a single partitioning of the mesh.  I.e. There should
  * be no mesh entity that is contained in more than one child part(ition)
- * set, and typically every mesh entity of the dimenion used to partition
+ * set, and typically every mesh entity of the dimension used to partition
  * the mesh is contained in exactly one of the child sets.
  *
  * The data for this tag is a single integer value.  The value of
  * the tag is undefined.
  */
-#define PARALLEL_PARITIONING_TAG_NAME "PARALLEL_MESH_PARITIONING"
+#define PARALLEL_PARTITIONING_TAG_NAME "PARALLEL_MESH_PARTITIONING"
=20
 /** \brief Tag storing which other processor a given entity is shared with
  *

Repository URL: https://bitbucket.org/fathomteam/moab/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.


More information about the moab-dev mailing list