LAPACK ("Linear Algebra Package") is a standard software library for numerical linear algebra. It provides routines for solving systems of linear equations and linear least squares, eigenvalue problems, and singular value decomposition. It also includes routines to implement the associated matrix factorizations such as LU, QR, Cholesky and Schur decomposition.[2] LAPACK was originally written in FORTRAN 77, but moved to Fortran 90 in version 3.2 (2008).[3] The routines handle both real and complex matrices in both single and double precision. LAPACK relies on an underlying BLAS implementation to provide efficient and portable computational building blocks for its routines.[2]: "The BLAS as the Key to Portability"
Initial release | 1992 |
---|---|
Stable release | 3.12.0[1]
/ 24 November 2023 |
Repository |
|
Written in | Fortran 90 |
Type | Software library |
License | BSD-new |
Website | netlib |
LAPACK was designed as the successor to the linear equations and linear least-squares routines of LINPACK and the eigenvalue routines of EISPACK. LINPACK, written in the 1970s and 1980s, was designed to run on the then-modern vector computers with shared memory. LAPACK, in contrast, was designed to effectively exploit the caches on modern cache-based architectures and the instruction-level parallelism of modern superscalar processors,[2]: "Factors that Affect Performance" and thus can run orders of magnitude faster than LINPACK on such machines, given a well-tuned BLAS implementation.[2]: "The BLAS as the Key to Portability" LAPACK has also been extended to run on distributed memory systems in later packages such as ScaLAPACK and PLAPACK.[4]
Netlib LAPACK is licensed under a three-clause BSD style license, a permissive free software license with few restrictions.[5]
Subroutines in LAPACK have a naming convention which makes the identifiers very compact. This was necessary as the first Fortran standards only supported identifiers up to six characters long, so the names had to be shortened to fit into this limit.[2]: "Naming Scheme"
A LAPACK subroutine name is in the form pmmaaa
, where:
p
is a one-letter code denoting the type of numerical constants used. S
, D
stand for real floating-point arithmetic respectively in single and double precision, while C
and Z
stand for complex arithmetic with respectively single and double precision. The newer version, LAPACK95, uses generic subroutines in order to overcome the need to explicitly specify the data type.mm
is a two-letter code denoting the kind of matrix expected by the algorithm. The codes for the different kind of matrices are reported below; the actual data are stored in a different format depending on the specific kind; e.g., when the code DI
is given, the subroutine expects a vector of length n
containing the elements on the diagonal, while when the code GE
is given, the subroutine expects an n×n array containing the entries of the matrix.aaa
is a one- to three-letter code describing the actual algorithm implemented in the subroutine, e.g. SV
denotes a subroutine to solve linear system, while R
denotes a rank-1 update.For example, the subroutine to solve a linear system with a general (non-structured) matrix using real double-precision arithmetic is called DGESV
.[2]: "Linear Equations"
Many programming environments today support the use of libraries with C binding (LAPACKE, a standardised C interface,[6] has been part of LAPACK since version 3.4.0[7]), allowing LAPACK routines to be used directly so long as a few restrictions are observed. Additionally, many other software libraries and tools for scientific and numerical computing are built on top of LAPACK, such as R,[8] MATLAB,[9] and SciPy.[10]
Several alternative language bindings are also available:
As with BLAS, LAPACK is sometimes forked or rewritten to provide better performance on specific systems. Some of the implementations are:
Since LAPACK typically calls underlying BLAS routines to perform the bulk of its computations, simply linking to a better-tuned BLAS implementation can be enough to significantly improve performance. As a result, LAPACK is not reimplemented as often as BLAS is.
These projects provide a similar functionality to LAPACK, but with a main interface differing from that of LAPACK: