TRV-2026-2492Version 2 · Revised

Saved · see the current record

Why this version exists

Refiled from Problem to Trace: the study's main result, a 13.2% cut in temperature error, was missing from the record. The gain was added from the paper's abstract; the problem reading is unchanged.

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-2492
version: 2
kind: revised
reason: Refiled from Problem to Trace: the study's main result, a 13.2% cut in temperature error, was missing from the record. The gain was added from the paper's abstract; the problem reading is unchanged.
timestamp: 2026-11-12T08:34:24.425844Z
status: published
lens: trace
sector: climate
headline: Regional Evaluation of Pangu-Weather Driven by Multiple NWP Initial Fields over Shandong Province, China
dek: Accurate weather forecasting is essential for decision-making in agriculture, transportation, disaster prevention, and energy management. In recent years, data-driven artificial intelligence (AI) models have shown considerable potential for medium-range weather forecasting by substantially improving computational efficiency while maintaining competitive forecast skill. This study evaluates the regional performance of Pangu-Weather initialized with three global numerical weather prediction (NWP) systems—ECMWF-IFS…
gain_title: In a five-month test against 123 weather stations in Shandong, Pangu-Weather started from ECMWF data cut 2 m temperature error by about 13.2% against ECMWF's own operational forecasts, improving at 38 of 40 lead times.
problem_title: In the same Shandong test, Pangu-Weather runs started from CMA and NCEP data had larger errors than ECMWF forecasts at several longer lead times over coastal stations and at 500–700 hPa.
trace_subject: Pangu-Weather forecasts over Shandong Province
gain_reading: In a five-month test against 123 weather stations in Shandong, Pangu-Weather started from ECMWF data cut 2 m temperature error by about 13.2% against ECMWF's own operational forecasts, improving at 38 of 40 lead times.
gain_evidence: EC_PG reduces the mean 2 m temperature RMSE by approximately 13.2%, with improvement at 38 of 40 lead times and a maximum improvement of 28.3%
problem_reading: In the same Shandong test, Pangu-Weather runs started from CMA and NCEP data had larger errors than ECMWF forecasts at several longer lead times over coastal stations and at 500–700 hPa.
problem_evidence: CMA_PG and NCEP_PG have larger errors than EC at several longer lead times over coastal stations and at 500–700 hPa
quick_read: A peer-reviewed evaluation tested the AI model Pangu-Weather over Shandong Province, China, from August to December 2024. Started from ECMWF-IFS fields, it cut mean 2 m temperature error by about 13.2% compared with ECMWF operational forecasts, improving at 38 of 40 lead times, with a maximum gain of 28.3%.

Surface forecasts were checked against 123 national meteorological stations and upper-air forecasts against three radiosonde stations. Wind-speed error at 10 m fell at every lead time, by 5.7% on average and up to 10.6%. Specific-humidity forecasts improved in all three configurations, by 8.6–12.8% on average, with a peak of 33.7% in one comparison.

Results were not uniform. Runs started from CMA-GFS and NCEP-GFS fields had larger errors than ECMWF at several longer lead times over coastal stations and at 500–700 hPa, and upper-air temperature and wind gains varied by level, station and lead time. The authors say the model could serve as a regional forecasting aid, with performance depending on the initial fields, variable, location and lead time.
limitation: Performance depended on the initial fields, variable, location and lead time, and upper-air temperature and wind gains varied by pressure level, station and lead time.
tag: Dual reading
key_points: The test covered August to December 2024 over Shandong Province, China. | Pangu-Weather was started from three global systems: ECMWF-IFS, CMA-GFS and NCEP-GFS. | Surface forecasts were verified against 123 national meteorological stations; upper-air forecasts against three radiosonde stations. | The ECMWF-initialized run cut 2 m temperature error by about 13.2%, improving at 38 of 40 lead times. | Its 10 m wind-speed error was lower at every lead time, by 5.7% on average and 10.6% at most. | Specific-humidity forecasts improved in all three configurations, by 8.6–12.8% on average. | CMA- and NCEP-initialized runs were worse than ECMWF at several longer lead times over coastal stations and at 500–700 hPa.
rundown: The study assessed how Pangu-Weather, a data-driven AI model for medium-range forecasting, performs at regional scale when fed different operational starting fields. It compared runs from ECMWF-IFS, CMA-GFS and NCEP-GFS with ECMWF operational forecasts over Shandong Province.

The ECMWF-initialized run (EC_PG) gave the most robust overall performance. Its mean 2 m temperature error was about 13.2% lower than ECMWF operational forecasts, with a maximum improvement of 28.3%. Its 10 m wind-speed error was lower at every lead time, with a mean improvement of 5.7% and a maximum of 10.6%.

Upper-air results were mixed. Specific-humidity forecasts generally improved across three stations and three pressure levels, by 8.6–12.8% on average and up to 33.7% in one comparison. Temperature and wind improvements depended on pressure level, station and lead time, and the CMA- and NCEP-started runs trailed ECMWF at some longer lead times.
sources:
- peer_reviewed | Atmosphere | https://doi.org/10.3390/atmos17111087 | 2026-11-04
prev: 24242faf384544619cb5b364d344280b858d419c26271b453ada9a74649541ca
SHA-256 hash
7582b0bc371ae3c9cfe49104081e993b8b7ae11a143ac7e8e5f726dfc012cd2a
Previous version’s hash
24242faf384544619cb5b364d344280b858d419c26271b453ada9a74649541ca
Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2492 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.