What is published right now
Three dispatches are currently filed. Each one describes a single piece of work we have shipped to a partner observatory or operations centre, the metric we are willing to defend on it, and the failure modes we know about. The numbers in each are reproducible from the validation notebook that ships with the corresponding model release on the Data page.
M-class flare TSS 0.71 at 30 min
How a spatiotemporal CNN on SDO/AIA EUV imagery plus HMI magnetograms reached TSS 0.71 at the 30-minute horizon for M-class flares, including the calibration step that made the score usable for an operations desk and the failure modes (limb events, multi-flare days).
Open the dispatch →Restoration when the data is a histogram
EMCCD electron-multiplication imaging produces data that is, in the regime that matters, a Poisson histogram rather than an image plus Gaussian noise. The dispatch walks through why classical denoisers fail and what a photon-count-aware variational network buys you (1.7× effective gain over BM3D at g = 200).
Open the dispatch →A real-bogus classifier you can put in front of a broker
97.4% recall at 0.5% bogus contamination on the ZTF 2024-January replay set, plus a cosmic-ray segmenter at F1 0.962 replacing LACosmic. The dispatch is honest about the LSST-era volume considerations that will reset the benchmark.
Open the dispatch →Why the cadence is irregular
The engineering desk has a single rule about dispatches: a piece is filed when an internal hostile reviewer cannot kill it, and not before. The rule produces about three dispatches a year. We are aware that this is not how content marketing is meant to work; we are also aware that observatory partners read these pieces carefully before integrating our models into a real pipeline, and we would rather they read three honest dispatches than twelve marketing ones.
Each dispatch carries the filing date, the engineering author byline, and a numeric reference to the validation notebook used to produce the headline figure. Errata, when we find them, are appended to the end of the original dispatch with the date and the correction; we do not silently re-edit numbers.
What about the older work
Work that pre-dates the current dispatch format lives in the engineering notebooks shared directly with partner observatories. Where a finding has held up under continued use, it is rewritten into a current-format dispatch; where it has not, it is archived without ceremony. We do not maintain a public archive of the older pieces because they were written for a specific operational audience and would mislead a general reader.
The full citation pattern for referencing a dispatch in an academic paper is given on the Data page along with each model release.
If a dispatch is relevant to your pipeline
Each dispatch ends with a transit notice for that specific piece of work. The generic path — academic collaboration, operations integration, or instrument-scientist support — is on the Access page; the fastest reply route is the contact form below.
Open contact →