Event capture
How many relevant reports landed inside the 25-mile neighborhood of any non-zero forecast area?
Forecast Grade v3 is built to separate those two truths. It rewards a broad low-probability outlook for finding the event, then asks more of a 15% or 30% core: was the activity actually where the stronger claim was drawn?
The old calculation called the March 10 package 37.7 / F. The revised instrument calls it 76.9 / C: comfortably passing, visibly imperfect, and specific about why.
The headline score is now an outcome measure with a spatial conscience. Low-risk coverage is allowed to be wide. High-risk cores are not allowed to be vague.
How many relevant reports landed inside the 25-mile neighborhood of any non-zero forecast area?
Below 15%, broad coverage earns bounded credit. At 15%+, softened area contingency measures the core.
Does a high-probability core produce the amount of activity its size and tier imply?
Significant reports are scored proportionally. One hit is evidence—not perfection.
This is the saved forecast geometry normalized into a small instrument panel. Colored outlines are real March 10 probability contours; pale points are a sample of the archived SPC reports used in the replay.
Geometry normalized from the saved 2026-03-10 package; report points sampled from the 608-report archived SPC replay. Visual comparison aid, not a geographic map.
The broad envelope found nearly every report. The stronger core was less spatially exact, and the significant contour had no significant verification.
Excellent event coverage, but the 15%+ placement and 30% yield claim both leave visible debt.
This is the important correction: the hail outlook saw the event, but its stronger areas did not line up tightly enough to deserve a 100.
These values remain useful as a technical readout. They are no longer allowed to define the entire human-facing grade.
Five saved packages, matched to their archived SPC report dates, plus synthetic edge cases. The real set is still small—but it already catches the two failure modes we were worried about: overgrading and overpenalizing.
| Date | Evidence | v3 result |
|---|---|---|
| 02 / 23 | no usable severe geometry | — |
| 03 / 02 | no reports / quiet day | — |
| 03 / 03 | 7 reports / missed hail | 20.6 |
| 03 / 09 | 65 reports / mixed placement | 74.0 |
| 03 / 10 | 608 reports / strong capture | 76.9 |
Read the spread: v3 does not pretend a quiet day can yield a meaningful single-case accuracy grade. It does, however, refuse to call a broad successful outlook perfect—and it still fails a genuine miss.
These are the guardrails that keep v3 from becoming either a compactness contest or a participation trophy.
Capture earns real credit. Placement is deliberately bounded below perfect because a broad envelope did not localize the threat.
The outlook can still pass when the event is found, but core placement and significant coverage pull the grade down.
High-risk area creates an expectation. When the observed activity cannot support it, event yield and placement fail together.
It is still possible. A forecast with near-total capture, well-placed 15%+ cores, activity that supports its high-risk claims, and proportionally successful significant placement can earn it. But a low-probability wide net cannot reach 100 merely because the storm happened somewhere inside.