ctapipe 
Low-level data processing pipeline software for the CTAO (Cherenkov Telescope Array Observatory).
This code is a prototype data processing framework and is under rapid development. It is not recommended for production use unless you are an expert or developer!
Slack: Contact Karl Kosack for invite
Citing this software
If you use this software for a publication, please cite the Zenodo Record for the specific version you are using and our latest publication.
You can find all ctapipe Zenodo records here: List of ctapipe Records on Zenodo.
There is also a Zenodo DOI always pointing to the latest version:
At this point, the latest publication is our contribution in the 2023 ICRC proceedings, which you can cite using this bibtex entry:
@inproceedings{ctapipe-icrc-2023,
author = {Linhoff, Maximilian and Beiske, Lukas and Biederbeck, Noah and Fröse, Stefan and Kosack, Karl and Nickel, Lukas},
title = {ctapipe -- Prototype Open Event Reconstruction Pipeline for the Cherenkov Telescope Array},
usera = {for the CTA Consortium and Observatory},
doi = {10.22323/1.444.0703},
booktitle = {Proceedings, 38th International Cosmic Ray Conference},
year=2023,
volume={444},
number={703},
location={Nagoya, Japan},
}Installation for Users
ctapipe and its dependencies may be installed using the Anaconda or Miniconda package system. We recommend creating a conda virtual environment first, to isolate the installed version and dependencies from your main environment (this is optional).
The latest version of ctapipe can be installed via:
mamba install -c conda-forge ctapipe
or via:
pip install ctapipe
Note: to install a specific version of ctapipe take a look at the documentation here.
Note: mamba is a C++ reimplementation of conda and can be found here.
Note that this is pre-alpha software and is not yet stable enough for end-users (expect large API changes until the first stable 1.0 release).
Developers should follow the development install instructions found in the documentation.
3 maintainers
Metadata
3 maintainers
Release files for ctapipe 0.32.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 | |
|---|---|---|---|
| ctapipe-0.32.0.tar.gz | 6.3 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ctapipe-0.32.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.5 MB
Release files / ctapipe-0.32.0.tar.gz
| Download URL | ctapipe-0.32.0.tar.gz |
|---|---|
| Size | 6.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
081b7476e815c49860ba079d5185350f19d2056069df0c4d27d54ad11cd520d1
|
|
BLAKE2b-256 checksum How to use checksums |
050e3e214a86e47832b8d803c10152d643a29b04e3ffef40afa40ab3297a3afe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / ctapipe-0.32.0-py3-none-any.whl
| Download URL | ctapipe-0.32.0-py3-none-any.whl |
|---|---|
| Size | 2.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
be541ba91038452a965965f60657f424e7c5ff6425cd6f43d524a0d6f8f4cb30
|
|
BLAKE2b-256 checksum How to use checksums |
1a93285cf81f084d60777e0bf4c3e92f40394464833a056522eee6226acc396d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency log
