-
Notifications
You must be signed in to change notification settings - Fork 50
Description
Project URL
https://pypi.org/project/snid-sage/
Does this project already exist?
- Yes
New Limit
300
Update issue title
- I have updated the title.
Which indexes
PyPI, TestPyPI
About the project
snid-sage is a research software for template crossmatching of supernova spectra. Users compare their observed spectra against a curated, versioned library of reference templates to obtain classifications and quality metrics. The project has been active since summer 2025 and is used in daily transient follow-up workflows where observers collect spectroscopy after discovery and need a quick, reliable type estimate.
To keep installs lean, we’ve:
- Included only essential files in the wheel (no tests, build caches).
- Stored reference templates as compressed, curated HDF5 bundles with deduplication.
- Trimmed example data to the minimum needed for sanity checks.
- Avoided vendoring other packages; third-party code is installed via normal dependencies.
We do bundle reference template data (optical and NIR) because this is core to the tool’s operation and reproducibility.
Reasons for the request
Many users run snid-sage on HPC/cluster or offline environments, so the package must work out of the box without post-install downloads. Shipping the vetted template set with the code ensures:
- Reproducibility: exact code+data pairing for published results and audits.
- Correct defaults: immediate, complete functionality (including NIR coverage), which matters when classifying higher-redshift supernovae (really far away supernovae)
- Operational reliability: observers who discover supernovae and take spectra need a fast, dependable classifier during follow-up.
We’ve evaluated alternatives:
- On-first-run downloads are unreliable behind firewalls and break deterministic installs.
- Splitting templates into optional pieces increases the chance of incomplete environments and inconsistent results.
Current artifact sizes: the wheel is ~220 MB, exceeding the default 100 MB per-file cap.
We’re requesting a 300 MB per-file limit (PyPI and TestPyPI) to provide a self-contained, reproducible install. We don’t expect frequent releases, and we’ll keep pruning non-essential assets; any future growth would be modest (e.g., carefully curated template updates) and well within this headroom.
Code of Conduct
- I agree to follow the PSF Code of Conduct