Pyplis - Python Plume Imaging Software
Pyplis is a Python toolbox originally developed for the analysis of UV SO2 camera data. The software includes a comprehensive and flexible collection of algorithms for the analysis of atmospheric imaging data and is tested for all major operating systems and most recent python versions.
Useful links
Installation: Installation instructions
Getting Started: Getting Started guide
Main Features: Feature overview
Contributing: Contributing guide
Scientific background: Peer reviewed pyplis publication
Features
Comprehensive algorithms for all aspects of UV SO2 camera data analysis.
Flexible tools for atmospheric imaging data processing.
Cross-platform compatibility (Windows, Linux).
Tested with recent Python versions.
For more details on the features, please refer to the documentation.
Installation
To install Pyplis, simply run:
pip install pyplisIf you use conda, you can also install pyplis using conda-forge:
conda install -c conda-forge pyplisFor detailed installation instructions, please refer to the documentation.
Documentation
The pyplis documentation is hosted here. It contains all relevant information about the software, including installation instructions, a detailed API reference, and a gallery of examples. The documentation is continuously updated and improved.
Contributions are welcome!
The pyplis software is maintained during the author’s free time, and the author is no longer actively engaged in the field of volcano remote sensing. Contributions from users or developers with expertise in UV SO2 cameras are highly valued. Interested individuals are encouraged to reach out via email at jonasgliss@gmail.com, submit pull requests through a fork, or create issues on the repository (tagging @jgliss in issues and pull requests is recommended).
1 maintainer
Metadata
1 maintainer
Release files for pyplis 1.5.0
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 | Actions |
|---|---|---|---|---|
| pyplis-1.5.0.tar.gz | 28.7 MB | Without provenance | Details for pyplis-1.5.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyplis-1.5.0-py3-none-any.whl | Python 3 | none | any | Details for pyplis-1.5.0-py3-none-any.whl |
Total release size: 33.5 MB
Release files / pyplis-1.5.0.tar.gz
| Download URL | pyplis-1.5.0.tar.gz |
|---|---|
| Size | 28.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
630dc57acb05eb2cb6f5a92617814dafddcdeacf12ddfebd8d065db638f11d99
|
|
BLAKE2b-256 checksum How to use checksums |
f7b51a83b3c8cc17c38f9419dcd2a12c8b1ad80765e9bdd6f14988272fec74a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.10
|
Release files / pyplis-1.5.0-py3-none-any.whl
| Download URL | pyplis-1.5.0-py3-none-any.whl |
|---|---|
| Size | 4.8 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a933d6fd5bd50a146467132a246c71986b96f2b7c02c01f23cdb6423616e08fc
|
|
BLAKE2b-256 checksum How to use checksums |
af4bfb482bac314d3c2973152107ceff5e38e0dd169dba5a8a216876fd56368d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.10
|
Security for pyplis 1.5.0
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.
