Extreme Weather Bench (EWB)
Read our blog post here | Documentation | Changelog
As AI weather models are growing in popularity, we need a standardized set of community driven tests that evaluate the models across a wide variety of high-impact hazards. Extreme Weather Bench (EWB) builds on the successful work of WeatherBench and introduces a set of high-impact weather events, spanning across multiple spatial and temporal scales and different parts of the weather spectrum. We provide data to use for testing, standard metrics for evaluation by forecasters worldwide for each of the phenomena, as well as impact-based metrics. EWB is a community system and will be adding additional phenomena, test cases and metrics in collaboration with the worldwide weather and forecast verification community.
Events
EWB has cases broken down by multiple event types within src/extremeweatherbench/data/events.yaml between 2020 and 2024. EWB case studies are documented here.
Available:
| Event Type | Number of Cases |
|---|---|
| 🌇 Heat Waves | 46 |
| 🧊 Freezes | 14 |
| 🌀 Tropical Cyclones | 98 |
| ☔️ Atmospheric Rivers | 56 |
| 🌪️ Severe Convection | 115 |
| Total Cases | 329 |
EWB paper and talks
How do I suggest new data, metrics, or otherwise get involved?
We welcome your involvement! The success of a benchmark suite rests on community involvement and feedback. There are several ways to get involved:
- Get involved in community discussion using the discussion board
- Submit new code requests using the issues
- Send us email at hello@brightband.com
Installing EWB
Currently, the easiest way to install EWB is using pip or uv:
$ pip install extremeweatherbench
# Or, add to an existing uv virtual environment
$ uv add extremeweatherbench
If you'd like to install the most recent updates to EWB:
$ pip install git+https://github.com/brightbandtech/ExtremeWeatherBench.git
For extra installation options:
# For running the data prep modules:
$ pip install "extremeweatherbench[data-prep]"
$ uv add "extremeweatherbench[data-prep]"
How to Run EWB
Running EWB on sample data (included) is straightforward.
Using Jupyter Notebook or a Script:
import extremeweatherbench as ewb
# Load in a forecast; here, we load in GFS initialized FCNv2 from the CIRA MLWP archive with a default variable built-in for convenience
fcnv2_heatwave_forecast = ewb.defaults.cira_fcnv2_heatwave_forecast
# Load in ERA5 with another default convenience variable
era5_heatwave_target = ewb.defaults.era5_heatwave_target
# EvaluationObjects are used to evaluate a single forecast source against a single target source with a defined event type. Event types are declared with each case. One or more metrics can be evaluated with each EvaluationObject.
heatwave_evaluation_list = [
ewb.inputs.EvaluationObject(
event_type="heat_wave",
metric_list=[
ewb.metrics.MaximumMeanAbsoluteError(),
ewb.metrics.RootMeanSquaredError(),
ewb.metrics.MaximumLowestMeanAbsoluteError(),
],
target=era5_heatwave_target,
forecast=fcnv2_heatwave_forecast,
),
]
# Load in the EWB default list of event cases
case_metadata = ewb.cases.load_cases()
# Create the evaluation class, with cases and evaluation objects declared
ewb_instance = ewb.evaluate.ExtremeWeatherBench(
case_metadata=case_metadata,
evaluation_objects=heatwave_evaluation_list,
)
# Execute a parallel run and return the evaluation results as a pandas DataFrame
heatwave_outputs = ewb_instance.run_evaluation(
parallel_config={"n_jobs": 16} # Uses 16 jobs with the loky backend as default
)
# Save the results
heatwave_outputs.to_csv("heatwave_evaluation_results.csv")
Using command line initialization:
$ ewb --default
Note: this will run every event type, case, target source, and metric for the individual event type as they become available for GFS initialized FourCastNetv2. It is expected a full evaluation will take some time, even on a large VM.
Metadata
Release files for extremeweatherbench 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| extremeweatherbench-1.1.1.tar.gz | 165.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| extremeweatherbench-1.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 348.9 kB
Release files / extremeweatherbench-1.1.1.tar.gz
| Download URL | extremeweatherbench-1.1.1.tar.gz |
|---|---|
| Size | 165.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2f9f7e260febba23a89f418673748f0548ebf7ca7ce96033464b958e4a2632ea
|
|
BLAKE2b-256 checksum How to use checksums |
634d0978f21f2d3de9f5edfd725e82f46ba4292f5f00702af308868c96094e8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / extremeweatherbench-1.1.1-py3-none-any.whl
| Download URL | extremeweatherbench-1.1.1-py3-none-any.whl |
|---|---|
| Size | 183.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09c82ab77d4ef4a29893325bed3848796d267dfe75a5a07242dade0ecfa2ed69
|
|
BLAKE2b-256 checksum How to use checksums |
b136542941319089d872f276944f7c926cf3c5e5b3c35f8dcbe6a40f72f536bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency log