bts6 models. Nothing was screenshotted and no BOOM classifier
score is invented.Tiles follow the widget's own rule: filled block, three-bucket colour at 0.7 and 0.4, integer per cent. BOOM's own classifiers are blank here because this page was rendered offline from the FLARE models alone.
| measured out of fold, SN Ia n = 7159 | 90.6% ± 0.3% |
| credibility max p — matches any class at all | 0.143 |
| confidence 1 − second p | 0.875 |
| p-value floor 1/(ncal+1) | 0.003 |
| likelihood ratio prior-free | 13.7× |
| novelty p-value 1 in 315 known-class objects is this extreme | 0.0032 |
| sep [arcsec] | 2.13 |
| rKronMag | 17.88 |
| iKronMag | 18.80 |
| g-r | nan |
| sep [arcsec] | 6.10 |
| W1 | 12.76 |
| W1-W2 | -0.55 |
What the current UI could and could not show. The six class scores drop
straight into the existing “ML Scores” card — but only after
mapAlertClassifications in ClassificationsV2.tsx stops
being a hard-coded whitelist (acai_*, btsbot,
drb, reliability, sgscore1,
LSPSC), which silently drops every other key. The prediction set, the
error it admits and the anomaly energy have no home in the widget at all: it draws
one number per classifier with a three-bucket colour and no threshold lines, so the
FLARE card above is a new component.
Pipeline fit. BOOM already runs its models as ONNX in enrichment workers
(ORT_DYLIB_PATH, results written back to MongoDB) and crossmatches
static catalogues per alert, which is exactly what FLARE consumes: PS1 host and
pre-outburst counterpart, Legacy Surveys photo-z, Gaia, AllWISE. The classifier is
LightGBM and converts to ONNX; the anomaly layer reads its own narrower
181-column space.