</pre>
Here, <code>N</code> is the number of concurrent tests that should be
run, in the same way as you can say <code>make -jN</code>. The testsuite
- is huge and will need around 12h on current computers
+ is huge and will need around 12h on current computers
running single threaded.
</p>
<a href="http://www.nongnu.org/numdiff/">numdiff</a> tool that compares
stored and newly created output files based on floating point
tolerances. To use it, simply export where the <code>numdiff</code>
- executable can be found via the <code>PATH</code>
+ executable can be found via the <code>PATH</code>
environment variable so that it can be found during
<code>make setup_tests</code>.
</p>
<p>
To run the testsuite in this mode, essentially, you have to do three
- things:
+ things:
<ol>
<li>
build the library with appropriate profiling flags
<p>
<b>Note:</b> The tests in some subdirectories of <code>tests/</code> are
automatically run only if some feature is enabled. In this case a
- feature constraint encoded in the output file name is
+ feature constraint encoded in the output file name is
redundant and should be avoided. In particular, this holds for
- subdirectories
+ subdirectories
<code>distributed_grids</code>, <code>lapack</code>,
<code>metis</code>, <code>petsc</code>, <code>slepc</code>,
<code>trilinos</code>, <code>umfpack</code>, <code>gla</code>, and
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
- "http://www.w3.org/TR/html4/loose.dtd">
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+ "http://www.w3.org/TR/html4/loose.dtd">
-<html>
- <head>
+<html>
+ <head>
<title>The deal.II Readme on interfacing to ARPACK</title>
<link href="../screen.css" rel="StyleSheet">
<meta name="copyright" content="Copyright (C) 2010, 2013, 2015 by the deal.II authors">
- <meta name="keywords" content="deal.II">
- </head>
- <body>
+ <meta name="keywords" content="deal.II">
+ </head>
+ <body>
+
-
<h2>Installation of <acronym>ARPACK</acronym></h2>
<p>
- <a href="http://www.caam.rice.edu/software/ARPACK/">ARPACK</a>
+ <a href="http://www.caam.rice.edu/software/ARPACK/">ARPACK</a>
is a collection of Fortran77 subroutines designed to solve large
scale eigenvalue problems.
<a href="http://www.caam.rice.edu/software/ARPACK/" target="_top">ARPACK</a>
<li>edit <code>ARmake.inc</code></li>
<ul>
<li>change home to the correct directory</li>
- <li>choose which <acronym>BLAS</acronym> and
+ <li>choose which <acronym>BLAS</acronym> and
<acronym>LAPACK</acronym> you would like to use</li>
</ul>
<li>change the file second.f in the UTIL directory</li>
- <li>do <code>make lib</code> in the current directory
+ <li>do <code>make lib</code> in the current directory
to build the standard library <code>libarpack_$(PLAT).a</code>
</li>
</ul>
</p>
<p>
- Try to run one of the examples and compare the output.
- How the output should look like is stated in the README
+ Try to run one of the examples and compare the output.
+ How the output should look like is stated in the README
that can be found in the <code>EXAMPLES</code> directory.
- </p>
+ </p>
<p>
- If that output you produced looks like it should you can
- proceed to comile <acronym>deal.II</acronym> with
+ If that output you produced looks like it should you can
+ proceed to compile <acronym>deal.II</acronym> with
<acronym>ARPACK</acronym>.
</p>
projects / dealii.git / commitdiff