From c0ddcc6ab0b8e27d238d433e2b20e06fefd5c835 Mon Sep 17 00:00:00 2001 From: David Wells Date: Sat, 3 Jun 2017 14:18:57 -0400 Subject: [PATCH] Make some documentation links relative. The other tutorial programs use relative links in these cases. --- examples/step-1/doc/intro.dox | 4 ++-- examples/step-17/doc/intro.dox | 2 +- examples/step-36/doc/results.dox | 12 ++++++------ 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/examples/step-1/doc/intro.dox b/examples/step-1/doc/intro.dox index fee4a5d507..b87312bda3 100644 --- a/examples/step-1/doc/intro.dox +++ b/examples/step-1/doc/intro.dox @@ -86,8 +86,8 @@ tutorial is that you're interested in) and type The first command sets up the files that describe which include files this tutorial program depends on, how to compile it and how to run it. This command should find the installed deal.II libraries as well that were generated when -you compiled and installed everything as described in the deal.II ReadMe file. +you compiled and installed everything as described in the +README file. If this command should fail to find the deal.II library, then you need to provide the path to the installation using the command @code diff --git a/examples/step-17/doc/intro.dox b/examples/step-17/doc/intro.dox index 32c0b04a59..f6f146aee5 100644 --- a/examples/step-17/doc/intro.dox +++ b/examples/step-17/doc/intro.dox @@ -19,7 +19,7 @@ you want to run in %parallel on a cluster, you also need METIS to partition meshes. The installation of deal.II together with these two additional libraries is described in the README file. +href="../../readme.html" target="body">README file. Now, for the details: as mentioned, the program does not compute anything new, so the use of finite element classes, etc., is exactly the same as before. The diff --git a/examples/step-36/doc/results.dox b/examples/step-36/doc/results.dox index 5643013888..90cf29f0d6 100644 --- a/examples/step-36/doc/results.dox +++ b/examples/step-36/doc/results.dox @@ -170,12 +170,12 @@ procedure. A sketch of how this can be done can be found in @ref step_17 "step-17".
  • Finally, there are alternatives to using the SLEPc eigenvalue -solvers. deal.II has interfaces to one of them, ARPACK (see -http://www.dealii.org/developer/external-libs/arpack.html), implemented in the -ArpackSolver class. Here is a short and quick overview of what one would need -to change to use it, provided you have a working installation of ARPACK and -deal.II has been configured properly for it (see the deal.II ReadMe file -at http://www.dealii.org/readme.html): +solvers. deal.II has interfaces to one of them, ARPACK (see the ARPACK configuration page for +setup instructions), implemented in the ArpackSolver class. Here is a short and +quick overview of what one would need to change to use it, provided you have a +working installation of ARPACK and deal.II has been configured properly for it +(see the deal.II README file): First, in order to use the ARPACK interfaces, we can go back to using standard deal.II matrices and vectors, so we start by replacing the PETSc and SLEPc -- 2.39.5