Astronomy · The Sun, heliosphere and space weather
Solar measurements and space-weather forecasting
Distinguish measurement, physical inference and a defined forecast, then evaluate invented timing and forecast cases using transparent uncertainty and scoring conventions.
Continue in the approved chapter order. Necessary vocabulary, quantities and assumptions are explained in the lesson.
Back to the chapterAfter reading, you can
- Compare solar and in-situ measurements by quantity, response, time and location.
- State a forecast target and distinguish a conditional transit estimate from usable lead time.
- Calculate and interpret categorical and probability scores with an explicit reference forecast.
Name the measured quantity before interpreting it
An image, a spectrum, a magnetogram and an in-situ particle record do not measure the same quantity. A comparison needs the instrument response, units, location, observation time, sampling and processing. Display colour alone cannot make these products physically interchangeable.
Calibration relates instrument indications to reference values under stated conditions and with uncertainty. A physical inference adds a model connecting those measured signals to unobserved properties. For example, the earlier two-component response case showed that one calibrated channel can still admit different plasma mixtures.
A forward model predicts signals from assumed physical inputs; an inverse analysis infers inputs from signals under a chosen model. A forecast adds a time-directed question about an outcome not yet observed when the forecast is issued. These roles should be stated explicitly when data and models are combined.
A useful record retains its provenance and uncertainty throughout those steps. Precise units and repeatable processing support interpretation, while neither eliminates sampling limits, response uncertainty or physical model discrepancy.
A transit estimate is one conditional model component
Specify a forecast’s event or quantity, location or region, issue time, valid interval, threshold if used, and observation-matching rule. “Activity later” is too vague to evaluate. Lead time concerns the interval between issuing a forecast and the defined target time; data transfer and processing can consume part of the available interval.
Construct an original upstream example with prescribed projected distance d = 1500000 km and constant propagation speed v = 400 km s⁻¹. The model t = d/v gives 3750 s = 62.5 minutes. These are supplied quantities, not an actual spacecraft geometry, measured front or operational lead-time claim.
For an optional first-order uncertainty calculation, stipulate small independent standard uncertainties u_d = 15000 km and u_v = 20 km s⁻¹. Then u_t ≈ t√[(u_d/d)² + (u_v/v)²] ≈ 191.213 s, or 3.18689 minutes. Independence is an explicit assumption; correlated inputs require their covariance term.
The result is a standard uncertainty for the declared approximate model. It is not a confidence interval or a guaranteed warning. Acceleration, changing direction, front geometry, sampling and model discrepancy can add information or uncertainty beyond this distance-and-speed calculation.
Count outcomes using one fixed definition
A binary categorical forecast says whether a defined event will occur. A hit means an event forecast matched an observed event; a false alarm means it did not. A miss is an event observed after a no-event forecast, while a correct negative is a matching no-event pair.
Create one hundred invented evaluation cases for a single fixed target region, threshold, time window and matching rule. Stipulate six hits, four false alarms, two misses and eighty-eight correct negatives. There are eight observed events and ninety-two observed non-events.
The table is a calculation exercise, not an assessment of any named forecasting service. It contains no missing cases and makes no claim of statistical independence or representative sampling for a real population.
A real evaluation must retain the target definition, sample selection, missing observations, dependence and any changes in observing or forecasting practice. Repeatedly tuning a model on the same evaluation set can also weaken the independence of a reported result.
| Forecast | Event observed | No event observed | Row total |
|---|---|---|---|
| Event | 6 hits | 4 false alarms | 10 |
| No event | 2 misses | 88 correct negatives | 90 |
| Column total | 8 | 92 | 100 |
High accuracy can conceal a rare-event problem
Overall accuracy is (hits + correct negatives)/all cases = 94/100 = 0.94. An always-no-event forecast would already be correct in 92/100 cases here. The apparent 94% accuracy is two percentage points above that simple reference, rather than a complete account of usefulness.
Probability of detection asks what fraction of observed events were forecast: 6/(6 + 2) = 0.75. The false-alarm ratio asks what fraction of event forecasts were false: 4/(6 + 4) = 0.4. Despite its name, the first quantity here is an evaluated count fraction, rather than an individual event’s forecast probability.
The false-alarm rate, also called probability of false detection in this binary setting, uses the observed non-events as its denominator: 4/(4 + 88) = 4/92 ≈ 0.0434783. The critical success index is 6/(6 + 4 + 2) = 0.5. These quantities answer different questions and should not be interchanged.
Choice of metric depends on the target and purpose. Event frequency, reference forecast and uncertainty in the evaluation matter. One favourable score does not establish calibration, general skill or the correct prediction of a particular local consequence.
| Metric | Calculation | Value |
|---|---|---|
| Accuracy | 94/100 | 0.94 |
| Always-no accuracy | 92/100 | 0.92 |
| Detection fraction | 6/8 | 0.75 |
| False-alarm ratio | 4/10 | 0.4 |
| False-alarm rate | 4/92 | 0.0434783 |
| Critical success index | 6/12 | 0.5 |
Declare the probability-score convention
A probability forecast gives p between zero and one for a defined event. Write its observed outcome as y = 1 when the event occurs and y = 0 otherwise. Define the binary Brier score here as the mean of (p − y)²; its range is zero to one, with smaller values better.
For four separate invented cases, use p = (0.8,0.6,0.2,0.1) and y = (1,0,1,0). Their squared errors are 0.04, 0.36, 0.64 and 0.01. The mean is 0.2625. A reference that assigns p = 0.5 to every one of these cases has score 0.25.
With skill defined as 1 − BS/BS_reference, this example gives 1 − 0.2625/0.25 = −0.05. The four supplied forecasts score worse than that declared reference under this measure. If instead both yes and no category errors are summed, the score doubles to 0.525 and the reference to 0.5; the normalization changes but the consistently formed skill does not.
Four invented cases establish neither reliability nor population performance. Reliability concerns whether stated probabilities correspond to observed frequencies across suitable sets of cases, with sampling uncertainty retained. Useful solar forecasting joins physical evidence with such independent evaluation, rather than treating a precise-looking probability or transit time as certainty.
| Case | Forecast p | Observed y | (p − y)² |
|---|---|---|---|
| 1 | 0.8 | 1 | 0.04 |
| 2 | 0.6 | 0 | 0.36 |
| 3 | 0.2 | 1 | 0.64 |
| 4 | 0.1 | 0 | 0.01 |
Worked examples
Keep a conditional clock and its uncertainty separate
What do the prescribed 1500000-km separation and 400-km s⁻¹ speed imply?
- Compute t = d/v = 3750 s = 62.5 minutes.
- Under the stipulated small independent uncertainties, use relative standard uncertainty √(0.01² + 0.05²).
- Multiplying by 3750 s gives u_t ≈ 191.213 s = 3.18689 minutes.
A conditional 62.5-minute transit with the stated first-order standard uncertainty, without a guaranteed lead time or confidence interval.
Identify the population in the denominator
Why are false-alarm ratio 0.4 and false-alarm rate about 0.0434783 different in the same table?
- The ratio divides four false alarms by ten event forecasts: 4/10.
- The rate divides those four by ninety-two observed non-events: 4/92.
- The counts are the same but the conditioning populations differ.
They answer different questions: how many event forecasts were false, versus how many observed non-events were forecast as events.
Try the reasoning
Is a calibrated image already a verified forecast of a later event?
Show the answer and reasoning
No.
Calibration, physical inference and future-event prediction play different roles. Verification needs a defined forecast and matching later observations.
What accuracy would always forecasting no event achieve in the invented 100-case set?
Show the answer and reasoning
0.92, or 92%.
There are ninety-two observed non-events. This baseline helps interpret the candidate’s 94% accuracy.
What is the binary Brier score of the four supplied probability cases?
Show the answer and reasoning
0.2625.
The squared errors sum to 1.05, and 1.05/4 = 0.2625. Summing both category errors would use a different normalization.
What does skill −0.05 mean relative to the declared 0.5-probability reference here?
Show the answer and reasoning
The supplied forecasts have a worse Brier score than that reference on these four cases.
It is the result of 1 − 0.2625/0.25. The small invented set does not establish general performance or calibration.
What to carry forward
- Measured signals, model-based inferences and forecasts have different evidence requirements.
- A forecast needs a defined target, clock, region and evaluation rule.
- Transparent denominators, score conventions, uncertainty and reference forecasts make verification interpretable.
References
Teaching resources and research supporting this lesson’s explanations and examples.
- Differential Emission Measures from the Regularized Inversion of Hinode and SDO data, author manuscriptv2I.G. Hannah and E.P. Kontar / University of GlasgowReference guide
- Forecast Verification GlossaryNOAA Space Weather Prediction Center / retained verification teaching glossaryReference guide · PDF