From e2a70b5ff4ddfe69d4a26141fe40343a1eaf2436 Mon Sep 17 00:00:00 2001 From: Timo Heister Date: Fri, 14 Feb 2020 23:38:04 -0500 Subject: [PATCH] do not use

tag in tutorials I am not quite sure why, but they don't show up in the table of contents. We have been avoiding them, but a few tutorials seem to violate this now. --- examples/step-14/doc/results.dox | 10 +++++----- examples/step-17/doc/intro.dox | 6 +++--- examples/step-36/doc/results.dox | 2 +- examples/step-39/doc/results.dox | 4 ++-- examples/step-47/doc/intro.dox | 6 +++--- examples/step-47/doc/results.dox | 2 +- examples/step-53/doc/intro.dox | 6 +++--- examples/step-60/doc/results.dox | 4 ++-- 8 files changed, 20 insertions(+), 20 deletions(-) diff --git a/examples/step-14/doc/results.dox b/examples/step-14/doc/results.dox index df4df7eea1..8c6802717a 100644 --- a/examples/step-14/doc/results.dox +++ b/examples/step-14/doc/results.dox @@ -1,6 +1,6 @@

Results

-

Point values

+

Point values

This program offers a lot of possibilities to play around. We can thus @@ -136,7 +136,7 @@ value: -

Comparing refinement criteria

+

Comparing refinement criteria

Since we have accepted quite some effort when using the mesh @@ -172,7 +172,7 @@ smaller errors. -

Evaluation of point stresses

+

Evaluation of point stresses

Besides evaluating the values of the solution at a certain point, the @@ -290,7 +290,7 @@ computed value of $J(u_h)$. -

Step-13 revisited

+

Step-13 revisited

If instead of the Exercise_2_3 data set, we choose @@ -357,7 +357,7 @@ would remain. -

Conclusions and outlook

+

Conclusions and outlook

The results here are not too clearly indicating the superiority of the diff --git a/examples/step-17/doc/intro.dox b/examples/step-17/doc/intro.dox index 79b432bf6a..342fb5b222 100644 --- a/examples/step-17/doc/intro.dox +++ b/examples/step-17/doc/intro.dox @@ -1,7 +1,7 @@

Introduction

-

Overview

+

Overview

This program does not introduce any new mathematical ideas; in fact, all it does is to do the exact same computations that step-8 @@ -50,7 +50,7 @@ time, PETSc also provides dummy MPI stubs, so you can run this program on a single machine if PETSc was configured without MPI. -

Parallelizing software with MPI

+

Parallelizing software with MPI

Developing software to run in %parallel via MPI requires a bit of a change in mindset because one typically has to split up all data structures so that @@ -172,7 +172,7 @@ function calls. That said, you do have to understand the general philosophy behind MPI as outlined above. -

What this program does

+

What this program does

The techniques this program then demonstrates are: - How to use the PETSc wrapper classes; this will already be visible in the diff --git a/examples/step-36/doc/results.dox b/examples/step-36/doc/results.dox index f913ce46df..4e883ca09d 100644 --- a/examples/step-36/doc/results.dox +++ b/examples/step-36/doc/results.dox @@ -1,6 +1,6 @@

Results

-

Running the problem

+

Running the problem

The problem's input is parameterized by an input file \step-36.prm which could, for example, contain the following text: diff --git a/examples/step-39/doc/results.dox b/examples/step-39/doc/results.dox index c9263a17c7..c3531d9d4b 100644 --- a/examples/step-39/doc/results.dox +++ b/examples/step-39/doc/results.dox @@ -1,6 +1,6 @@

Results

-

Logfile output

+

Logfile output

First, the program produces the usual logfile here stored in deallog. It reads (with omission of intermediate steps) @code @@ -82,7 +82,7 @@ DEAL:: This log for instance shows that the number of conjugate gradient iteration steps is constant at approximately 15. -

Postprocessing of the logfile

+

Postprocessing of the logfile

Using the perl script postprocess.pl, we extract relevant diff --git a/examples/step-47/doc/intro.dox b/examples/step-47/doc/intro.dox index 34ebe19c52..9991a52c10 100644 --- a/examples/step-47/doc/intro.dox +++ b/examples/step-47/doc/intro.dox @@ -58,7 +58,7 @@ conditions on one part of the boundary, and the other on the remainder. -

What's the issue?

+

What's the issue?

The fundamental issue with the equation is that it takes four derivatives of the solution. In the case of the Laplace equation @@ -122,7 +122,7 @@ consequence, they have largely fallen out of favor and deal.II currently does not contain implementations of these shape functions. -

What to do instead?

+

What to do instead?

So how does one approach solving such problems then? That depends a bit on the boundary conditions. If one has the first set of boundary @@ -482,7 +482,7 @@ $\mathcal{A}(\cdot,\cdot)$ and $\mathcal{F}(\cdot)$ described in the book chapter @cite Brenner2011 . -

The testcase

+

The testcase

The last step that remains to describe is what this program solves for. As always, a trigonometric function is both a good and a bad diff --git a/examples/step-47/doc/results.dox b/examples/step-47/doc/results.dox index 6a7fc558aa..d646e17318 100644 --- a/examples/step-47/doc/results.dox +++ b/examples/step-47/doc/results.dox @@ -191,7 +191,7 @@ is that $\gamma=p(p+1)$ yields the expected results. It is, consequently, what t uses as currently written. -

Possibilities for extensions

+

Possibilities for extensions

There are a number of obvious extensions to this program that would make sense: diff --git a/examples/step-53/doc/intro.dox b/examples/step-53/doc/intro.dox index 35f52a320e..c630d2f755 100644 --- a/examples/step-53/doc/intro.dox +++ b/examples/step-53/doc/intro.dox @@ -51,7 +51,7 @@ deal.II Frequently Asked Questions page referenced from http://www.dealii.org/ provides resources to mesh generators. -

Where geometry and meshes intersect

+

Where geometry and meshes intersect

Let us assume that you have a complex domain and that you already have a coarse mesh that somehow represents the general features of the domain. Then @@ -108,7 +108,7 @@ means providing a class derived from ChartManifold, and this is precisely what we will do in this program. -

The example case

+

The example case

To illustrate how one describes geometries using charts in deal.II, we will consider a case that originates in an application of the Implementation +

Implementation

There are a number of issues we need to address in the program. At the largest scale, we need to write a class that implements the interface of ChartManifold. This involves diff --git a/examples/step-60/doc/results.dox b/examples/step-60/doc/results.dox index 59627a376d..ae9c27c51c 100644 --- a/examples/step-60/doc/results.dox +++ b/examples/step-60/doc/results.dox @@ -202,7 +202,7 @@ end and you would obtain exactly the same results as in test case 1 below. -

Test case 1:

+

Test case 1:

For the default problem the value of $u$ on $\Gamma$ is set to the constant $1$: this is like imposing a constant Dirichlet boundary condition on $\Gamma$, seen @@ -283,7 +283,7 @@ representatio of your domain (a much cheaper and easier mesh to produce). To play around a little bit, we are going to complicate a little the fictitious domain as well as the boundary conditions we impose on it. -

Test case 2 and 3:

+

Test case 2 and 3:

If we use the following parameter file: @code -- 2.39.5