68/100

Moderate evidence

GainPublished recordClimateGood Space

Evaluating the Skill of Medium-Range Machine Learning–Based Convective Hazard Forecasts Derived from Convection-Allowing Ensembles

Truvace record
TRV-2026-2601raw data (JSON)
Version
v1Published
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
9084e3d3af6b…check it

Abstract We assess the skill of daily machine learning (ML)-based probabilistic convective hazard predictions generated from two experimental medium-range (i.e., extending to day 8) convection-allowing ensemble (CAE) systems to determine if such predictions are skillful over the CONUS. CAE forecasts were generated in real time for events in spring 2023 and 2024, and convective hazard predictions were produced using neural networks, trained with CAE output and observed storm reports (i.e., reports of tornadoes, h…

The gain

In a study of real-time forecasts from spring 2023 and 2024 over the continental US, machine learning hazard forecasts built from convection-allowing ensembles outperformed both updraft-helicity forecasts and climatology through day 8.

Sources

1 on file
  1. Weather and Forecastingdoi:10.1175/waf-d-25-0243.1
    Peer-reviewed2026-07-23

Cite this record

v1

Truvace Impact Record TRV-2026-2601, v1: “Evaluating the Skill of Medium-Range Machine Learning–Based Convective Hazard Forecasts Derived from Convection-Allowing Ensembles.” Truvace, 2026-11-12. /record/TRV-2026-2601 (accessed on the day you copy it). sha256 9084e3d3af6b496a…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv19084e3d3af6b…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

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