AceCAST 5: what's new
AceCAST 5 is available now. Here is what changed: WRF 4.8, four physics updates and four new model outputs.
A forecast you have not scored is a forecast you cannot price, tune or trust. The common scores in plain language, the pitfalls, and one published example of honest reporting.

Forecast verification is the practice of scoring forecasts against what actually happened. It is how a forecast-team lead learns whether a new model setup is an improvement, how a buyer learns what a vendor's forecast is worth, and how an operations lead decides how far to trust tomorrow's number. This guide covers what to compare against, the common scores in plain language, the pitfalls that produce flattering results, and one published example of a result reported with its limits attached.
No reference is perfect truth. Each has strengths and blind spots.
Whatever the reference, score a baseline too: persistence (no change from now), climatology, or a public forecast such as HRRR, NOAA's hourly US forecast model. A forecast earns its cost only by beating what you could have had without it.
Take five wind forecasts that missed by +2, −1, +3, −2 and +3 m/s (forecast minus observed). The numbers are made up to show the arithmetic.
For events, such as a storm at a site or wind above a turbine's cut-out speed, count hits, misses and false alarms. Say a storm was forecast on 20 days and arrived on 12 of them, and 3 more storms arrived without a forecast (made-up numbers again).
Report the two together. A forecast that calls a storm every day has a perfect hit rate and a useless false alarm ratio. Fuller definitions are in the methods guide kept by the Joint Working Group on Forecast Verification Research, a working group under the WMO's World Weather Research Programme. METplus, from the Developmental Testbed Center with NCAR and NOAA, is a public verification framework.
A model value is an average over a grid square. An instrument measures one point. A single grid square can hold both a ridge and a valley. Height matters as well: an anemometer at 10 m says little about wind at 80 m. Part of the "error" is this mismatch, not the forecast.
A high-resolution model draws a sharp storm. If it puts that storm 20 km away or an hour late, a point score counts a miss where the storm was and a false alarm where it was forecast: two penalties for one near miss. A smooth, coarse forecast that never commits can score better while being less useful. Scores that allow a neighborhood in space or a window in time treat sharp forecasts more fairly.
One dramatic case proves nothing. Fix the period, the sites and the score before looking at results. Then report every case, the sample size, the baseline and what did not work.
Aerava, the weather intelligence platform operated by TempoQuest, publishes a wind comparison. Its parts line up with the checklist above.
Aerava also says what it has not scored: storm forecasts are not yet scored, and hail size is experimental guidance. Twelve nights at one site is a small sample, and the statement claims no more than those twelve nights. That is the pattern to ask of any vendor, TempoQuest included: the sample, the reference, the baseline, what failed and what is still unscored.
TempoQuest is developing the Forecast Verification Tool (FVT), designed to improve the verification of weather forecasts. The scores and pitfalls in this guide are general practice, not a description of FVT.
Read what Aerava's 1 km site forecasts are, or contact TempoQuest.

AceCAST 5 is available now. Here is what changed: WRF 4.8, four physics updates and four new model outputs.

Aerava runs a weather model around the site you pin and checks the result against your own storm, wind and turbine cut-out limits. Here is what you can run today, what it costs and what it says about accuracy.

One published 2023 benchmark and two Azure list prices, worked line by line: what a GPU VM costs against one CPU VM and against sixteen, and what the sums leave out.
Your forecast
Tell us the decision it has to serve. One short form reaches the team, and we review every request.