[MOAB-dev] commit/MOAB: 2 new changesets
commits-noreply at bitbucket.org
commits-noreply at bitbucket.org
Sat Aug 3 13:01:15 CDT 2013
2 new commits in MOAB:
https://bitbucket.org/fathomteam/moab/commits/7134355f2c22/
Changeset: 7134355f2c22
Branch: None
User: iulian07
Date: 2013-08-03 19:26:00
Summary: doxygenize comments in fortran
also include *.F90 to file patters
fortran example now shows up in the list
still don't know why the example is not referenced in iMesh
Affected #: 2 files
diff --git a/doc/user.dox.in b/doc/user.dox.in
index 07f707f..4e1c773 100644
--- a/doc/user.dox.in
+++ b/doc/user.dox.in
@@ -321,7 +321,7 @@ INPUT = @top_srcdir@/src @top_srcdir@/src/moab \
# and *.h) to filter out the source-files in the directories. If left
# blank all files are included.
-FILE_PATTERNS = *.cpp *.hpp *.h *.dox
+FILE_PATTERNS = *.cpp *.hpp *.h *.dox *.F90
#FILE_PATTERNS = *.dox
# The RECURSIVE tag can be used to turn specify whether or not subdirectories
diff --git a/examples/DirectAccessNoHolesF90.F90 b/examples/DirectAccessNoHolesF90.F90
index 3cf5fa7..c3cceeb 100644
--- a/examples/DirectAccessNoHolesF90.F90
+++ b/examples/DirectAccessNoHolesF90.F90
@@ -1,42 +1,41 @@
-! @example DirectAccessNoHolesF90.F90 \n
-! \brief Use direct access to MOAB data to avoid calling through API, in Fortran90 \n
-!
-! This example creates a 1d row of quad elements, such that all quad and vertex handles
-! are contiguous in the handle space and in the database. Then it shows how to get access
-! to pointers to MOAB-native data for vertex coordinates, quad connectivity, and tag storage
-! (vertex to quad adjacency lists aren't accessible from Fortran because they are std::vector's).
-! This allows applications to access this data directly
-! without going through MOAB's API. In cases where the mesh is not changing (or only mesh
-! vertices are moving), this can save significant execution time in applications.
-!
-! Using direct access (or MOAB in general) from Fortran is complicated in two specific ways:
-! 1) There is no way to use arrays with specified dimension starting/ending values with ISO_C_BINDING;
-! therefore, all arrays passed back from MOAB/iMesh must use 1-based indices; this makes it a bit
-! more difficult to traverse the direct arrays. In this example, I explicitly use indices that
-! look like my_array(1+v_ind...) to remind users of this.
-! 2) Arithmetic on handles is complicated by the fact that Fortran has no unsigned integer type. I get
-! around this by assigning to a C-typed variable first, before the handle arithmetic. This seems to
-! work fine. C-typed variables are part of the Fortran95 standard.
-!
-! ----------------------
-! | | | |
-! | | | | ...
-! | | | |
-! ----------------------
-!
-! -# Initialize MOAB \n
-! -# Create a quad mesh, as depicted above
-! -# Create 2 dense tags (tag1, tag2) for avg position to assign to quads, and # verts per quad (tag3)
-! -# Get connectivity, coordinate, tag1 iterators
-! -# Iterate through quads, computing midpoint based on vertex positions, set on quad-based tag1
-! -# Iterate through vertices, summing positions into tag2 on connected quads and incrementing vertex count
-! -# Iterate through quads, normalizing tag2 by vertex count and comparing values of tag1 and tag2
-!
-! <b>To compile</b>: \n
-! make DirectAccessNoHolesF90 MOAB_DIR=<installdir> \n
-! <b>To run</b>: ./DirectAccessNoHolesF90 [-nquads <# quads>]\n
-!
-!
+!> @example DirectAccessNoHolesF90.F90
+!! \brief Use direct access to MOAB data to avoid calling through API, in Fortran90 \n
+!!
+!! This example creates a 1d row of quad elements, such that all quad and vertex handles
+!! are contiguous in the handle space and in the database. Then it shows how to get access
+!! to pointers to MOAB-native data for vertex coordinates, quad connectivity, and tag storage
+!! (vertex to quad adjacency lists aren't accessible from Fortran because they are std::vector's).
+!! This allows applications to access this data directly
+!! without going through MOAB's API. In cases where the mesh is not changing (or only mesh
+!! vertices are moving), this can save significant execution time in applications.
+!!
+!! Using direct access (or MOAB in general) from Fortran is complicated in two specific ways:
+!! 1) There is no way to use arrays with specified dimension starting/ending values with ISO_C_BINDING;
+!! therefore, all arrays passed back from MOAB/iMesh must use 1-based indices; this makes it a bit
+!! more difficult to traverse the direct arrays. In this example, I explicitly use indices that
+!! look like my_array(1+v_ind...) to remind users of this.
+!! 2) Arithmetic on handles is complicated by the fact that Fortran has no unsigned integer type. I get
+!! around this by assigning to a C-typed variable first, before the handle arithmetic. This seems to
+!! work fine. C-typed variables are part of the Fortran95 standard.
+!!
+!! ----------------------
+!! | | | |
+!! | | | | ...
+!! | | | |
+!! ----------------------
+!!
+!! -# Initialize MOAB \n
+!! -# Create a quad mesh, as depicted above
+!! -# Create 2 dense tags (tag1, tag2) for avg position to assign to quads, and # verts per quad (tag3)
+!! -# Get connectivity, coordinate, tag1 iterators
+!! -# Iterate through quads, computing midpoint based on vertex positions, set on quad-based tag1
+!! -# Iterate through vertices, summing positions into tag2 on connected quads and incrementing vertex count
+!! -# Iterate through quads, normalizing tag2 by vertex count and comparing values of tag1 and tag2
+!!
+!! <b>To compile</b>: \n
+!! make DirectAccessNoHolesF90 MOAB_DIR=<installdir> \n
+!! <b>To run</b>: ./DirectAccessNoHolesF90 [-nquads <# quads>]\n
+!!
#define CHECK(a) \
if (a .ne. iBase_SUCCESS) call exit(a)
https://bitbucket.org/fathomteam/moab/commits/c39f3e9e60dc/
Changeset: c39f3e9e60dc
Branch: master
User: iulian07
Date: 2013-08-03 20:00:22
Summary: add references to the user guide and and dev guide to the main page
Affected #: 2 files
diff --git a/doc/UG/moabUG.h b/doc/UG/moabUG.h
index c5231fa..a6a6f4a 100644
--- a/doc/UG/moabUG.h
+++ b/doc/UG/moabUG.h
@@ -18,7 +18,7 @@
- Timothy J. Tautges (Argonne National Lab, Univ Wisconsin-Madison)
- Iulian Grindeanu (Argonne National Lab)
- Rajeev Jain (Argonne National Lab)
- - Xiabing Xu (Argonne National Lab)
+ - Danqing Wu (Argonne National Lab)
<h2>Emeritus members:</h2>
@@ -27,6 +27,7 @@
- Brandon M. Smith
- Hong-Jun Kim
- Jim Porter
+ - Xiabing Xu
\page contents Table of Contents
diff --git a/src/moab/Interface.hpp b/src/moab/Interface.hpp
index d7ad8aa..1decd7a 100644
--- a/src/moab/Interface.hpp
+++ b/src/moab/Interface.hpp
@@ -22,9 +22,12 @@
* together to describe geometric topology, boundary condition, and inter-processor interface
* groupings in a mesh.
*
- * MOAB's API is documented in the moab::Interface class. The User's Guide and Developer's Guide are located in
- * <a href="pages.html">related pages</a>. Questions and comments should be sent to moab-dev
+ * MOAB's API is documented in the moab::Interface class. Questions and comments should be sent to moab-dev
* _at_ mcs.anl.gov.
+ *
+ * \ref userguide "User's Guide (MOAB 4.6)"
+ *
+ * \ref developerguide "Developer's Guide (MOAB 4.6)"
*/
#ifndef MOAB_INTERFACE_HPP
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