Welcome to specsuite!
For help with getting specsuite running on your own data, please check out the documentation page!
Introduction
Although other spectroscopic reduction tools exist, they are often designed for a small subset of instruments, have hard-to-read documentation, or are difficult to debug. specsuite was designed to address all three of these concerns, providing a set of robust, generalized, and user-friendly reduction tools! As of writing, this reduction pipeline has been tested this reduction pipeline against data from...
- Gemini North (GMOS-N)
- Apache Point Observatory (KOSMOS)
- Sommers-Bausch Observatory (SBO)
...but we are constantly testing on data from other telescopes!
Another advantage of specsuite is its modularity. All functions were designed to be easy to slot into an existing reduction pipeline (assuming the data is formatted correctly). If there are features you would like to see added to specsuite, please feel free to add an issue on this repository for our developers to address!
Installation
To install the most recent version of specsuite, run the following command from your terminal...
pip install specsuite
OR if you would like to install a version from this repository, the run...
git clone https://github.com/Autumn10677/specsuite.git
cd specsuite
pip install .
How can I test specsuite runs on my computer?
We have provided a handful of files and scripts that should help you get started on processing your data.
specsuite_env.yml~ A working Conda environment for the current version of the package.workflow.smk~ This is a "snakemake workflow" set to run on some sample data taken from APO's long-slit spectrograph.
Note that using the 'specsuite_env.yml' requires you to have Conda already installed on your computer. Instructions on installing Conda for Windows, macOS, and Linux can be found here! To run this workflow on your own computer, first clone the repository using...
git clone https://github.com/Autumn10677/specsuite.git
cd specsuite
Then run...
conda env create -f environment.yml
conda activate specsuite_env
snakemake --cores 1
This should deposit a set of files in an 'output/' folder that you can use to check out how the pipeline works at various steps in the analysis. These outputs include both images and '.npy' files used for storing exposure data between steps of the pipeline. If you see...
Finished jobid: 0 (Rule: all)
4 of 4 steps (100%) done
...then the pipeline ran successfully!
Metadata
Release files for specsuite 1.2.1
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 |
|---|---|---|---|---|
| specsuite-1.2.1.tar.gz | 22.5 MB | With provenance | Details for specsuite-1.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| specsuite-1.2.1-py3-none-any.whl | Python 3 | none | any | Details for specsuite-1.2.1-py3-none-any.whl |
Total release size: 45.1 MB
Release files / specsuite-1.2.1.tar.gz
| Download URL | specsuite-1.2.1.tar.gz |
|---|---|
| Size | 22.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ff028e204d14568f2bde73d6890f68c8cf745e89d4f1ce603537de3dbf33371
|
|
BLAKE2b-256 checksum How to use checksums |
0d82b8a571a71cd4464d8fc41116016d82bfa2b8f56b520c7ebe9d5af1d9372e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 11, 2026.
Transparency logRelease files / specsuite-1.2.1-py3-none-any.whl
| Download URL | specsuite-1.2.1-py3-none-any.whl |
|---|---|
| Size | 22.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0c3c9f79823ce307a7a89695c98eca39b3848732ff7d9bb82428188becaa10b2
|
|
BLAKE2b-256 checksum How to use checksums |
1b09f5ce8e83f2bec5bfd7f11db4afb3f613b6c6b7b7c9839c3923286297887a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 11, 2026.
Transparency logSecurity for specsuite 1.2.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for specsuite-1.2.1.tar.gz
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 Aug 11, 2026.
Transparency logA 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.