Ripser
Ripser.py is a renovated Python implementation of the Ripser package. We provide a slim interface for computing persistence cohomology of sparse and dense data sets, visualizing persistence diagrams, computing lowerstar filtrations on images, and computing representative cochains.
To aid your use of the package, we've put together a large set of notebooks that demonstrate many of the features available. Complete documentation about the package can be found at ripser.scikit-tda.org.
Through extensive testing and continuous integration, Ripser.py is easy to install on Mac, Linux, and Windows platforms.
If you're looking for the original C++ library, you can find it at Ripser/ripser.
Setup
Installation requires Cython, but other than that, it is available on all platforms (if you are having trouble installing, please let us know!)
pip install Cython
pip install Ripser
Usage
The interface is as simple as can be:
import numpy as np
from ripser import ripser, plot_dgms
data = np.random.random((100,2))
diagrams = ripser(data)['dgms']
plot_dgms(diagrams)
We also supply a Scikit-learn transformer style object if you would prefer to use that:
import numpy as np
from ripser import Rips
rips = Rips()
data = np.random.random((100,2))
diagrams = rips.fit_transform(data)['dgms']
rips.plot(diagrams)
License
Ripser.py is available under an MIT license!
Contributions
We welcome all kinds of contributions! There are lots of opportunities for potential projects, so please get in touch if you would like to help out. Everything from code to notebooks to examples and documentation are all equally valuable so please don't feel you can't contribute. To contribute please fork the project make your changes and submit a pull request. We will do our best to work through any issues with you and get your code merged into the main branch.
3 maintainers
Metadata
3 maintainers
Release files for ripser 0.2.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ripser-0.2.6.tar.gz | 70.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ripser-0.2.6-cp36-cp36m-macosx_10_12_x86_64.whl | CPython 3.6 | CPython 3.6 pymalloc | macOS 10.12+ x86-64 | Details |
Total release size: 133.8 kB
Release files / ripser-0.2.6.tar.gz
| Download URL | ripser-0.2.6.tar.gz |
|---|---|
| Size | 70.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4ce71e3b3adba87ecbd986141249e088ac238e83b91c2dc5b8a06599c12bf3cd
|
|
BLAKE2b-256 checksum How to use checksums |
41958ebea463cfa3c734b0058e1a709f28f5958e84dbc5c3f3bda9dd1b6f2eb1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.0.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.6.4
|
Release files / ripser-0.2.6-cp36-cp36m-macosx_10_12_x86_64.whl
| Download URL | ripser-0.2.6-cp36-cp36m-macosx_10_12_x86_64.whl |
|---|---|
| Size | 63.4 kB |
| Tags | CPython 3.6 CPython 3.6 pymalloc macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
88600a47008ec12a34fffabb29ee23a4cb0302b805e4ea46e74042c50be1cbe6
|
|
BLAKE2b-256 checksum How to use checksums |
59caca947b5ace04a2255ba371635b588caa6b290f8ee7f6391631fc18fd69fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.0.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.6.4
|
Security for ripser 0.2.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
