SLEPc Release Version 3.22
The following downloads correspond to the latest available release. Note that slepc4py source (without documentation) is already included in the SLEPc tarball.
| Description | File | MD5 checksum |
|---|---|---|
| SLEPc distribution file (source code only) | slepc-3.22.2.tar.gz | 649601827246366224d512f7b25d972b |
| SLEPc distribution file (source code with documentation) | slepc-with-docs-3.22.2.tar.gz | d99176f13b60f922714b239d83db2230 |
| slepc4py distribution file (enables separate install) | slepc4py-3.22.2.tar.gz | 37fe519252c319bfccb237bfaaa673c2 |
There are no separate patch files, the current fixes are included in the tar file. Patches are documented at: slepc-3.22 change log
Previous Versions
Distribution files: [3.0.0] [3.1] [3.2] [3.3] [3.4] [3.5] [3.6] [3.7] [3.8] [3.9] [3.10] [3.11] [3.12] [3.13] [3.14] [3.15] [3.16] [3.17] [3.18] [3.19] [3.20] [3.21]
Note: Users of previous versions are strongly recommended to upgrade to the latest one.
Note: Even older releases can be found here.
Development Version
The development repository is hosted at gitlab.com and uses the git version control system. Note that using the development version requires also a development version of PETSc.
The development process follows the methodology used by PETSc, with two integration branches (main and release), together with various feature branches. One can expect SLEPc's main branch to be synchronized with PETSc's main branch.
In order to get the development version of SLEPc, you need to clone the repository:
$ git clone https://gitlab.com/slepc/slepc
At a later time, the repository can be refreshed simply by:
$ git pull
You can also use the repository to work with the release version, instead of downloading the tarball file. The release branch tracks the latest release version, including all the patches. It is also possible to check out a specific version with the tag name, for instance:
$ git checkout v3.22.0
The source code in the repository can be browsed at gitlab.com. Some statistics related to source code development can be found at openhub.net.
Additional information can be found at PETSc Developer’s Documentation.
Users of the development version may also want to check the nightly tests for various builds of SLEPc's main branch with PETSc's main branch, as well as the source coverage of these tests (for real or complex). The development copy of the documentation is also available, also for the python interface (slepc4py docs).