From: bangerth Date: Fri, 25 Apr 2014 13:18:15 +0000 (+0000) Subject: Augment the documentation in a couple of places. X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=295da7df8617abe1e345cb6eaee5e8e6146e3aa1;p=dealii-svn.git Augment the documentation in a couple of places. git-svn-id: https://svn.dealii.org/trunk@32827 0785d39b-7218-0410-832d-ea1e28bc413d --- diff --git a/deal.II/doc/doxygen/headers/glossary.h b/deal.II/doc/doxygen/headers/glossary.h index 5c10bf22dc..719467946e 100644 --- a/deal.II/doc/doxygen/headers/glossary.h +++ b/deal.II/doc/doxygen/headers/glossary.h @@ -944,6 +944,11 @@ Article{BK07, * distributed meshes, see the @ref distributed module. In such meshes, each * cell is owned by exactly one processor. The locally owned ones are those * owned by the current processor. + * + * Each processor in a parallel computation has a triangulation covering + * the entire domain that consists of cells that are locally owned, of + * @ref GlossGhostCell "ghost cells" and of + * @ref GlossArtificialCell "artificial cells". * * * diff --git a/deal.II/include/deal.II/grid/tria_accessor.h b/deal.II/include/deal.II/grid/tria_accessor.h index 17e78fd2b7..5a0e829713 100644 --- a/deal.II/include/deal.II/grid/tria_accessor.h +++ b/deal.II/include/deal.II/grid/tria_accessor.h @@ -782,7 +782,7 @@ public: * thereby moving the vertex of a cell within the triangulation. Of * course, doing so requires that you ensure that the new location * of the vertex remains useful -- for example, avoiding inverted - * or otherwise distorted (see also @ref GlossDistorted). + * or otherwise distorted (see also @ref GlossDistorted "this glossary entry"). * * @note When a cell is refined, its children inherit the position * of the vertex positions of those vertices they share with the mother @@ -798,10 +798,11 @@ public: * placed again at the same position as the first time around -- i.e., * not at the location you had previously moved it to. * - * @note The behavior described in the previous note is relevant if + * @note The behavior described above is relevant if * you have a parallel::distributed::Triangulation object. There, * refining a mesh always involves a re-partitioning. In other words, - * vertices of locally owned cells (see @ref GlossLocallyOwnedCell) + * vertices of locally owned cells (see + * @ref GlossLocallyOwnedCell "this glossary entry") * that you may have moved to a different location on one processor * may be moved to a different processor upon mesh refinement (even * if these particular cells were not refined) which will re-create