ILLUSTRATIVE · NASA / SVS · NOT ADITYA-L1 DATA
Orientation · research journey
The investigation, not just the answer
Nine stages, in the order they happened — including the two where the result was not what this project expected, and the point at which a less careful version of it would have published.
What is this?
A chronological account of how the flare-detection question was asked, tested, and answered — with the hypothesis that failed left in.
Why should I trust it?
Every figure in this account is interpolated at build time from the same committed artifacts the evidence pages render from, so the story cannot keep repeating a number the benchmark no longer contains.
Where can I verify it?
- The evidence for each stageCurves, calibration, error analysis
- Trace any claim hereClaim → artifact → commit
- Every model that was triedEight cards
- What the data cannot supportL-1 … L-10
The shape
Nine stages
03
The account
What happened, in order
01
Research question
Aditya-L1 publishes soft X-ray measurements from two payloads at one-minute cadence. Can a model trained on that archive detect solar flares better than the simplest rule an operator would write by hand?
The question was fixed before the data was touched, along with the metrics that would answer it. That ordering is what makes the eventual negative result publishable rather than a story assembled after the fact.
02
Initial hypothesis
Expected · Machine learning would beat the threshold, and spectral features would be why.
The reasoning was ordinary and, at the time, sound. A single count-rate threshold uses one number per minute and discards everything else — the shape of the rise, the recent variance, the spectral distribution. A learner with fourteen features and access to the spectrum should have had a great deal to work with.
Neither half of the hypothesis survived contact with the evaluation.
03
Dataset
Two years of archive products were parsed onto a canonical one-minute grid: 1,985 Parquet files across seven tables, frozen at a single digest and never modified since. Missing minutes were left missing.
The limitations were written down before modelling, not after. Two of them decided the shape of everything that followed: the effective sample size is events rather than minutes, and no instrument response exists, so physical severity targets are unconstructible from this archive.
04
Baseline
Expected · A threshold would be a floor to clear.
A single threshold on the SoLEXS count rate detected 76 of 82 M/X events (event recall 0.927) while raising 15 false alarm runs.
The baseline was not a floor. It was, and remained, the best operational detector in the study. Everything after this point is an attempt to displace it.
05
Machine learning
Expected · Gradient boosting would win.
Logistic regression, a random forest and LightGBM were fitted on the same fourteen features under a protocol frozen in advance — seed 20260718, chronological split, no shuffling. LightGBM ranked minutes best of anything evaluated: PR-AUC 0.707 against the threshold's 0.486.
On the ranking metric, the hypothesis looked confirmed. This is the point at which a less careful project would have published.
06
Unexpected results
Expected · Better ranking would mean better detection.
It did not. LightGBM detected 81 of 82 events against the threshold's 76 — no more flares — and the confidence intervals on ROC-AUC overlapped the baseline's, so no model was statistically distinguishable from it.
Ranking and detection came apart. At a base rate near one percent, being better at ordering minutes does not translate into catching more events, because the events were already at the top of both orderings.
07
False alarm analysis
Alarms were then counted as runs — contiguous blocks of predicted-positive minutes — because that is what an operator responds to. LightGBM raised 79 false runs against the threshold's 15: about 5 times as many, for no additional events detected.
This settled the question. The comparison is decided on the metric that matters operationally, and on that metric the learned models lose decisively.
08
Calibration
The remaining defence of a learned model is that its probabilities are useful even if its alarms are not. LightGBM's reliability diagram and Brier score (0.0155) are published so that argument can be evaluated rather than asserted.
The threshold detector emits a physical rate, not a probability, so it has no reliability diagram at all. Where a comparison is impossible, no comparison is drawn.
09
Final scientific conclusion
A one-line detector on the SoLEXS count rate remains the operational recommendation. Machine learning ranks individual minutes better, detects no more flares, and raises roughly 5× the false alarms. Added spectral resolution changed ROC-AUC by 0.0033 — a confirmed null.
The negative result is published at full weight, and the model that lost has the most detailed card on the site. A platform whose central claim is that its evidence is checkable earns that claim by publishing the finding a positive-result incentive would bury.
One more thing
What this account leaves in
The hypothesis in stage 2 was wrong, and it is left in the record rather than rewritten to match the outcome. So is stage 5, where the ranking metric made the hypothesis look confirmed — that is a real moment in the investigation, and removing it would make the eventual conclusion look more obvious than it was.
The same discipline applies elsewhere on this platform. Six times the implementation contradicted the written specification; all six adjudications are published, including the amendment that was declined and the one that remains open. A digest mismatch in the environment record was traced rather than silenced, and the trace is published as a case study.
None of that is decoration. A platform that only ever shows its successes gives a reader no way to calibrate how much to believe it.