From: Timo Heister Date: Fri, 17 Aug 2018 19:51:04 +0000 (-0400) Subject: address comment X-Git-Tag: v9.1.0-rc1~739^2 X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0a0a2417ef93d2aae2a703aa60133fa295f189c2;p=dealii.git address comment --- diff --git a/examples/step-16/doc/results.dox b/examples/step-16/doc/results.dox index 31836288ad..004d6d512a 100644 --- a/examples/step-16/doc/results.dox +++ b/examples/step-16/doc/results.dox @@ -61,7 +61,7 @@ it shows the power of multigrid methods. We encourage you to generate timings for the solve() call and compare to -step 6. You will see that the multigrid method has quite an overhead +step-6. You will see that the multigrid method has quite an overhead on coarse meshes, but that it always beats other methods on fine meshes because of its optimal complexity. diff --git a/examples/step-16b/doc/intro.dox b/examples/step-16b/doc/intro.dox index 5e4375c42a..9bddddddc6 100644 --- a/examples/step-16b/doc/intro.dox +++ b/examples/step-16b/doc/intro.dox @@ -7,6 +7,9 @@ This is a variant of step-16 with the only change that we are using the MeshWorker framework with the pre-made LocalIntegrator helper classes instead of manually assembling the matrices. +The details of this framework on how it is used in practice will be explained +as part of this tutorial program. +

The testcase

The problem we solve here is the same as the one in step-16.