TRV-2026-2514Version 1 · Published

Saved · see the current record

Why this version exists

Certified into the record

The exact text we saved

This is the version exactly as it was saved, character for character. The SHA-256 hash below is a 64-character code worked out from that text. Run the same text through SHA-256 and you get the same code; change a single letter and the code comes out completely different. Each version also stores the previous version’s hash, which chains them together so no version can be swapped out quietly.

TRUVACE RECORD VERSION
record: TRV-2026-2514
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-11-12T07:45:43.940737Z
status: published
lens: trace
sector: climate
headline: Comparative Verification of IFS-Control, AIFS, and WeatherNext 2 Mean for Short-Range (6–84 h) Temperature and Precipitation Forecasts over Inner Mongolia
dek: Whether advances in global weather forecasting translate into local forecast skill requires regional verification. Using observations at 117 stations in Inner Mongolia during the June–August 2026 flood season, we compared three publicly distributed forecast fields at 6–84 h lead times: the Integrated Forecasting System control forecast (IFS-Control), the Artificial Intelligence Forecasting System (AIFS), and WeatherNext 2’s 64-member ensemble mean (WN2). Because WN2 is an ensemble mean and the others are single…
gain_title: In a verification against 117 Inner Mongolia stations over the June–August 2026 flood season, temperature mean absolute error was about 15.7% lower for AIFS and 13.1% lower for WeatherNext 2 than for the IFS-Control forecast.
problem_title: In the same station-based study, both AI products under-forecast heavy-rain frequency and extremes, and IFS-Control clearly beat AIFS for 6-hour heavy rain (13 mm or more).
trace_subject: Short-range temperature and precipitation forecasts over Inner Mongolia, flood season 2026
gain_reading: In a verification against 117 Inner Mongolia stations over the June–August 2026 flood season, temperature mean absolute error was about 15.7% lower for AIFS and 13.1% lower for WeatherNext 2 than for the IFS-Control forecast.
gain_evidence: Temperature mean absolute error was approximately 15.7% lower for AIFS and 13.1% lower for WN2 than for IFS-Control
problem_reading: In the same station-based study, both AI products under-forecast heavy-rain frequency and extremes, and IFS-Control clearly beat AIFS for 6-hour heavy rain (13 mm or more).
problem_evidence: Both AI products under-forecast heavy-rain frequency and extremes | IFS-Control robustly outperformed AIFS for 6 h heavy rain (≥13 mm)
quick_read: A verification study using observations from 117 stations in Inner Mongolia compared three forecast products over the June–August 2026 flood season at lead times of 6 to 84 hours: the conventional IFS-Control, the AI-based AIFS, and the 64-member ensemble mean of WeatherNext 2. For 2 m temperature, mean absolute error was about 15.7% lower for AIFS and 13.1% lower for WeatherNext 2 than for IFS-Control.

Rain forecasts were mixed. Both AI products beat IFS-Control for 6-hour moderate rain (4 mm or more). For 6-hour heavy rain (13 mm or more), IFS-Control clearly outperformed AIFS, while its edge over WeatherNext 2 did not hold up under a stricter multiple-comparison correction.

The temperature gains came mainly from smaller correlation-error terms, while IFS-Control had the smallest systematic bias. Both AI products under-forecast heavy-rain frequency and extremes, which matters for flood-season warnings. A limited member experiment suggests ensemble averaging may contribute to this, though it cannot be separated from model differences.
limitation: The findings apply only to the product versions, region and season evaluated, and the comparison pits an ensemble mean against single deterministic forecasts, so it cannot isolate the underlying models.
tag: Dual reading
key_points: The study used observations from 117 stations in Inner Mongolia during June–August 2026. | Forecasts were verified at 6–84 hour lead times for 2 m temperature and precipitation. | Temperature mean absolute error was about 15.7% lower for AIFS and 13.1% lower for WeatherNext 2 than for IFS-Control. | IFS-Control had the smallest systematic temperature bias; the AI gains came mainly through smaller correlation-error terms. | Both AI products outperformed IFS-Control for 6-hour moderate rain (4 mm or more). | IFS-Control clearly beat AIFS for 6-hour heavy rain (13 mm or more); its advantage over WeatherNext 2 did not survive stricter correction. | Both AI products under-forecast heavy-rain frequency and extremes.
rundown: The researchers asked whether global advances in AI weather forecasting carry over to local skill, which they say requires regional verification. They compared three publicly distributed forecast fields: the IFS control forecast, AIFS, and the 64-member ensemble mean of WeatherNext 2.

Because WeatherNext 2 is an ensemble mean and the other two are single deterministic forecasts, the comparison is between operational products, not the underlying models. Verification used Murphy error decomposition and block-bootstrap sensitivity tests.

For temperature, the AI products had lower mean absolute error, mainly through smaller correlation-error terms, although IFS-Control had the smallest systematic bias. For precipitation, the picture depended on intensity: AI products led for moderate rain at 6 hours, while IFS-Control led for heavy rain, clearly over AIFS and less certainly over WeatherNext 2.

Both AI products under-forecast heavy-rain frequency and extremes. A limited member experiment suggests ensemble averaging may play a part, but not separably from differences between models.
sources:
- peer_reviewed | Atmosphere | https://doi.org/10.3390/atmos17111053 | 2026-10-27
prev: 0000000000000000000000000000000000000000000000000000000000000000
SHA-256 hash
5841b05a6f34fdde99eddd6662b7c4541acc8ada53bf99ec0b6508fac702eb21
Previous version’s hash
0000000000000000000000000000000000000000000000000000000000000000
Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2514 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.