As mentioned in the Preface, the ScaLAPACK library discussed in this Users' Guide is only one facet of the ScaLAPACK project. A variety of other software is also available in the scalapack directory on netlib.
/scalapack/index.html
P_ARPACK (Parallel ARPACK) is an extension of the ARPACK software package used for solving large-scale eigenvalue problems on distributed-memory parallel architectures. The message-passing layers currently supported are BLACS and MPI. Serial ARPACK must be retrieved and installed prior to installing P_ARPACK. All core ARPACK routines are available in single-precision real, double-precision real, single-precision complex, and double-precision complex. An extensive set of driver routines is available for ARPACK, and a subset of these is available for parallel computation with P_ARPACK. These may be used as templates that are easily modified to construct a problem specific parallel interface to P_ARPACK.
CAPSS is a fully parallel package to solve a sparse linear system of the form Ax=b on a message passing multiprocessor; the matrix A is assumed to be symmetric positive definite and associated with a mesh in two or three dimensions. This version has been tested on the Intel Paragon and makes possible efficient parallel solution for several right-hand-side vectors.
ParPre is a package of parallel preconditioners for general sparse matrices. It includes classical point/block relaxation methods, generalized block SSOR preconditioners (this includes ILU), and domain decomposition methods (additive and multiplicative Schwarz, Schur complement). The communication protocol is MPI, and low-level routines from the PETSc [109] library are used, but installing the complete PETSc library is not necessary.
Prototype codes are provided for out-of-core solvers [55] for LU, Cholesky, and QR, the matrix sign function for eigenproblems [14, 13, 12] , an HPF interface to a subset of ScaLAPACK routines, and SuperLU [96, 39, 41] .
/scalapack/prototype/These software contributions are classified as prototype codes because they are still under development and their calling sequences may change. They have been tested only on a limited number of architectures and have not been rigorously tested on all of the architectures to which the ScaLAPACK library is portable.
Refer to Appendix C.2 for a brief description of the HPF interface to ScaLAPACK, as well as an example program.