From: Jean-Paul Pelteret Date: Mon, 30 Jan 2017 21:50:09 +0000 (+0100) Subject: Match all
and
elements in glossary X-Git-Tag: v8.5.0-rc1~186^2 X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F3873%2Fhead;p=dealii.git Match all
and
elements in glossary --- diff --git a/doc/doxygen/headers/glossary.h b/doc/doxygen/headers/glossary.h index 5b75cecdd7..7353a9f1e9 100644 --- a/doc/doxygen/headers/glossary.h +++ b/doc/doxygen/headers/glossary.h @@ -29,7 +29,8 @@ *
A cell, face or edge is defined as active if it is not * refined any further, i.e., if it does not have children. Unless * working with a multigrid algorithm, active cells are the only - * ones carrying degrees of freedom.
+ * ones carrying degrees of freedom. + * * * * @@ -52,7 +53,8 @@ * * The concept of artificial cells has no meaning for triangulations * that store the entire mesh on each processor, i.e. the - * dealii::Triangulation class. + * dealii::Triangulation class. + * * * *
@anchor GlossBlockLA Block (linear algebra)
@@ -301,7 +303,8 @@ * * In either case, the length of the vector equals the determinant of * the transformation of reference face to the face of the current - * cell. + * cell. + * * * *
@anchor GlossBoundaryIndicator %Boundary indicator
@@ -687,7 +690,6 @@ * @image html distorted_2d.png "A well-formed, a pinched, and a twisted cell in 2d." * * @image html distorted_3d.png "A well-formed, a pinched, and a twisted cell in 3d." - * * * Distorted cells can appear in two different ways: The original * coarse mesh can already contain such cells, or they can be created @@ -777,6 +779,7 @@ * Triangulation object to test for distortion of cells, you need to * specify this upon creation of the object by passing the appropriate * flag. + * * * *
@anchor distributed_paper @@ -852,6 +855,7 @@ * face_flip and face_rotation. Some documentation for these * exists in the GeometryInfo class. An example of their use in user * code is given in the DoFTools::make_periodicity_constraints function. + * * * *
@anchor GlossGeneralizedSupport Generalized support points
@@ -936,7 +940,8 @@ * * The concept of ghost cells has no meaning for triangulations that * store the entire mesh on each processor, i.e. the - * dealii::Triangulation class. + * dealii::Triangulation class. + * * * *
@anchor GlossGhostedVector Ghosted vectors
@@ -1050,11 +1055,13 @@ * "node functionals" Ni for the given function * f and store the result as entry i in the coefficient * vector. + * * * *
@anchor GlossLagrange Lagrange elements
*
Finite elements based on Lagrangian interpolation at - * @ref GlossSupport "support points".
+ * @ref GlossSupport "support points". + * * * *
@anchor GlossLocallyOwnedCell Locally owned cell
@@ -1080,7 +1087,8 @@ * of freedom. * * Locally owned DoFs are a subset of the - * @ref GlossLocallyActiveDof "locally active DoFs". + * @ref GlossLocallyActiveDof "locally active DoFs". + * * * *
@anchor GlossLocallyActiveDof Locally active degrees of freedom
@@ -1266,7 +1274,7 @@ year= {2011}, publisher={SIAM}} * @endcode - * See + * See * DOI:10.1137/090778523 * for the paper and deal.II publications for more details. * @@ -1308,6 +1316,7 @@ * Qk+1,k x Qk,k+1 * Gauss points on edges(faces) and anisotropic Gauss points in the interior * + * * * *
@anchor GlossParallelScaling Parallel scaling
@@ -1478,9 +1487,10 @@ * using parallel::distributed::Triangulation::add_periodicity() * -# Gather the periodic faces using GridTools::collect_periodic_faces() (DoFHandler) * -# Add periodicity constraints using DoFTools::make_periodicity_constraints() - * - * An example for this can be found in step-45. - * + * + * An example for this can be found in step-45. + * + * * *
@anchor GlossPrimitive Primitive finite * elements
@@ -1494,13 +1504,15 @@ * step-29, step-22 and several others. On the other hand, * the FE_RaviartThomas class used in step-20 and step-21, or the FE_Nedelec * class provide non-primitive finite elements because there, each - * vector-value shape function may have several non-zero components. + * vector-value shape function may have several non-zero components. + * * * *
@anchor GlossReferenceCell Reference cell
*
The hypercube [0,1]dim, on which all parametric finite * element shape functions are defined. Many properties of the reference - * cell are described by the GeometryInfo class.
+ * cell are described by the GeometryInfo class. + * * * *
@anchor GlossSerialization Serialization
@@ -1519,12 +1531,14 @@ * interfaces for the BOOST serialization library. See there for examples on - * how to save and restore objects. + * how to save and restore objects. + * * * *
@anchor GlossShape Shape functions
*
The restriction of the finite element basis functions to a single - * grid cell.
+ * grid cell. + * * * *
@anchor GlossSubdomainId Subdomain id
@@ -1578,10 +1592,10 @@ * * * - *
@anchor GlossSupport Support points
Support points are - * by definition those points $p_i$, such that for the shape functions - * $v_j$ holds $v_j(p_i) = \delta_{ij}$. Therefore, a finite element - * interpolation can be defined uniquely by the values in the support + *
@anchor GlossSupport Support points
+ *
Support points are by definition those points $p_i$, such that for the + * shape functions $v_j$ holds $v_j(p_i) = \delta_{ij}$. Therefore, a finite + * element interpolation can be defined uniquely by the values in the support * points. * * Lagrangian elements fill the vector accessed by @@ -1599,15 +1613,18 @@ *
* * - *
@anchor GlossTargetComponent Target component
When - * vectors and matrices are grouped into blocks by component, it is + *
@anchor GlossTargetComponent Target component
+ *
+ * When vectors and matrices are grouped into blocks by component, it is * often desirable to collect several of the original components into * a single one. This could be for instance, grouping the velocities - * of a Stokes system into a single block.
+ * of a Stokes system into a single block. + * * * *
@anchor GlossUnitCell Unit cell
- *
See @ref GlossReferenceCell "Reference cell".
+ *
See @ref GlossReferenceCell "Reference cell". + *
* * *
@anchor GlossUnitSupport Unit support points
@@ -1720,6 +1737,7 @@ * @note The usual warning about the missing type safety of @p void pointers are * obviously in place here; responsibility for correctness of types etc * lies entirely with the user of the pointer. + * * * *
@anchor workstream_paper %WorkStream paper