Papers › DASH: Deep Learning for the Automated Spectral Classification of Supernovae and their Hosts
DASH: Deep Learning for the Automated Spectral Classification of Supernovae and their Hosts
Daniel Muthukrishna, David Parkinson, Brad Tucker
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
We present DASH (Deep Automated Supernova and Host classifier), a novel software package that automates the classification of the type, age, redshift, and host galaxy of supernova spectra. DASH makes use of a new approach that does not rely on iterative template matching techniques like all previous software, but instead classifies based on the learned features of each supernova's type and age. It has achieved this by employing a deep convolutional neural network to train a matching algorithm. This approach has enabled DASH to be orders of magnitude faster than previous tools, being able to accurately classify hundreds or thousands of objects within seconds. We have tested its performance on four years of data from the Australian Dark Energy Survey (OzDES). The deep learning models were developed using TensorFlow, and were trained using over 4000 supernova spectra taken from the CfA Supernova Program and the Berkeley SN Ia Program as used in SNID (Supernova Identification software, Blondin & Tonry 2007). Unlike template matching methods, the trained models are independent of the number of spectra in the training data, which allows for DASH's unprecedented speed. We have developed both a graphical interface for easy visual classification and analysis of supernovae, and a Python library for the autonomous and quick classification of several supernova spectra. The speed, accuracy, user-friendliness, and versatility of DASH presents an advancement to existing spectral classification tools. We have made the code publicly available on GitHub and PyPI (pip install astrodash) to allow for further contributions and development. The package documentation is available at https://astrodash.readthedocs.io.
In Syntology View this paper on Syntology: its repositories, every harvested function with whether it ran, its licence and the call to fetch it.
Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="1903.02557")
Code
Syntology Ran 8 of 10 code samples harvested from 1 repository linked to this paper; 2 have no recorded run. Of those that ran: 8 ran with no contract checked.
By repository: community (archive-listed): 10 samples from 1 repository, 8 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
10 samples harvested; 8 ran; 0 honoured the contract we drafted; 2 have no recorded run. Read from Syntology's graph 2026-09-25; that is when this build read the record, not when the samples ran.
Licence: 0 of the 10 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.
Harvested from wdavison909/stag. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.
Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (how to connect); click an identity to copy that call.
Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples from a repository marked official are listed first. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of four reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.
75ab25a92e6de18e · report
79fc4760b9826052 · report
ed3abb4984b3d5f5 · report
9338f023f9a48b44 · report
39f6de0a499c8d91 · report
41fc4070fa34143d · report
a9c5c56d42edd920 · report
46596ae7e36d937f · report
fe967c479a1f9262 · report
d5652292d1ba1ab2 · report
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections