From: Timo Heister Date: Wed, 15 May 2019 17:31:32 +0000 (-0600) Subject: doxygen: two broken lists X-Git-Tag: v9.2.0-rc1~1491^2 X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=346c628c09f7ef30e83465688b4cb6d539190987;p=dealii.git doxygen: two broken lists --- diff --git a/doc/doxygen/headers/glossary.h b/doc/doxygen/headers/glossary.h index 7fee4e3731..fec754932b 100644 --- a/doc/doxygen/headers/glossary.h +++ b/doc/doxygen/headers/glossary.h @@ -428,9 +428,10 @@ *
  • Most of the functions in the GridGenerator namespace take an optional * argument colorize. This argument controls whether or not the * different parts of the boundary will be assigned different - * @ref GlossBoundaryIndicator "boundary indicators". Some functions also assign - * different - * @ref GlossMaterialId "material indicators" as well.
  • + * @ref GlossBoundaryIndicator "boundary indicators". + * Some functions also assign different + * @ref GlossMaterialId "material indicators" + * as well. *
  • The function GraphColoring::make_graph_coloring() computes a * decomposition of a Triangulation (more exactly, a range of iterators). No * two adjacent cells are given the same color.
  • @@ -650,8 +651,7 @@ * *
    @anchor GlossDimension Dimensions @p dim and @p spacedim
    * - *
    - * Many classes and functions in deal.II have two template parameters, + *
    Many classes and functions in deal.II have two template parameters, * @p dim and @p spacedim. An example is the basic Triangulation class: * @code * template @@ -659,19 +659,24 @@ * @endcode * In all of these contexts where you see @p dim and @p spacedim referenced, * these arguments have the following meaning: - * - @p dim denotes the dimensionality of the mesh. For example, a mesh that - * consists of line segments is one-dimensional and consequently corresponds - * to `dim==1`. A mesh consisting of quadrilaterals then has `dim==2` and a - * mesh of hexahedra has `dim==3`. - * - @p spacedim denotes the dimensionality of the space in which such a mesh - * lives. Generally, one-dimensional meshes live in a one-dimensional space, - * and similarly for two-dimensional and three-dimensional meshes that - * subdivide two- and three-dimensional domains. Consequently, the - * @p spacedim template argument has a default equal to @p dim. But this need + * + *
      + *
    • @p dim denotes the dimensionality of the mesh. For example, a mesh + * that consists of line segments is one-dimensional and consequently + * corresponds to `dim==1`. A mesh consisting of quadrilaterals then has + * `dim==2` and a mesh of hexahedra has `dim==3`.
    • + * + *
    • @p spacedim denotes the dimensionality of the space in which such a + * mesh lives. Generally, one-dimensional meshes live in a one-dimensional + * space, and similarly for two-dimensional and three-dimensional meshes + * that subdivide two- and three-dimensional domains. Consequently, the @p + * spacedim template argument has a default equal to @p dim. But this need * not be the case: For example, we may want to solve an equation for * sediment transport on the surface of the Earth. In this case, the domain * is the two-dimensional surface of the Earth (`dim==2`) that lives in a - * three-dimensional coordinate system (`spacedim==3`). + * three-dimensional coordinate system (`spacedim==3`).
    • + *
    + * * More generally, deal.II can be used to solve partial differential * equations on manifolds * that are embedded in higher dimensional space. In other words, diff --git a/include/deal.II/differentiation/sd/symengine_scalar_operations.h b/include/deal.II/differentiation/sd/symengine_scalar_operations.h index 1ed5f2b00d..e7fb3fbfbe 100644 --- a/include/deal.II/differentiation/sd/symengine_scalar_operations.h +++ b/include/deal.II/differentiation/sd/symengine_scalar_operations.h @@ -1279,17 +1279,20 @@ namespace Differentiation * the map using the resolve_explicit_dependencies() function. * * Examples: - * 1. If map["a"] == 1 and map["b"] == "a" + 2, - * then the function $f(a,b(a)) := a+b$ will be evaluated and the result - * $f\vert_{a=1,b=a+2} = 3+a$ is returned. This return is because the - * symbol "a" is substituted throughout the function first, and only - * then is the symbol "b(a)" substituted, by which time its explicit - * dependency on "a" cannot be resolved. - * 2. If map["a"] == "b"+2 and map["b"] == 1, - * then the function $f(a(b),b): = a+b$ will be evaluated and the result - * $f\vert_{a=b+2, b} = [b+2+b]_{b=1} = 4$ is returned. This is because - * the explicitly dependent symbol "a(b)" is substituted first followed - * by the symbol "b". + *
      + *
    1. If map["a"] == 1 and map["b"] == "a" + 2, then + * the function $f(a,b(a)) := a+b$ will be evaluated and the result + * $f\vert_{a=1,b=a+2} = 3+a$ is returned. This return is because the + * symbol "a" is substituted throughout the function first, and only + * then is the symbol "b(a)" substituted, by which time its explicit + * dependency on "a" cannot be resolved.
    2. + * + *
    3. If map["a"] == "b"+2 and map["b"] == 1, then + * the function $f(a(b),b): = a+b$ will be evaluated and the result + * $f\vert_{a=b+2, b} = [b+2+b]_{b=1} = 4$ is returned. This is because + * the explicitly dependent symbol "a(b)" is substituted first followed + * by the symbol "b".
    4. + *
    */ Expression substitute(const Expression & expression,