Published October 16, 2026
| Version v1.1.1
Software
Open
brightbandtech/ExtremeWeatherBench: v1.1.1
Authors/Creators
- 1. @TheWeatherCompany
- 2. @Brightbandtech
- 3. @fraunhoferhhi
Description
Added
defaults.preprocess_derive_geopotential: a forecast preprocess that derivesgeopotentialfor forecasts that don't publish it, using the newcalc.geopotential_from_temperature_and_humidity(hypsometric integration of temperature and specific humidity upward from mean sea level pressure, a Numba column kernel applied lazily). Lets tropical cyclone tracking and the Craven-Brooks significant severe parameter (CBSS) run on such forecasts; a no-op whengeopotentialorgeopotential_heightis present (#433).station_qcmodule (ewb.station_qc) with the GHCNh checks used by theGHCNtarget (exclude_stations,mask_sentinel_values,mask_out_of_range,mask_spikes,apply_ghcnh_row_checks,apply_ghcnh_quality_control) and their default settings (GHCNH_*constants), plus aGHCN.quality_controlfield (defaultTrue) (#431).- Two
InputBasehooks for custom inputs, both no-ops by default:maybe_apply_quality_control(data), whichrun_pipelinecalls right after variable mapping and before preprocess, andcolumns_kept_through_variable_subset(), which names extra columns to keep through the tabular variable subset.maybe_subset_variablestakes a matchingkeep_if_present=argument (#431, #435).
Changed
- Clear any
cache_dirreused from 1.1.0 runs. Cached aligned targets are named by case and target name only, so a cache written by 1.1.0 is reused as-is and its GHCN targets skip the new quality control. GHCNdrops rows with no non-null values before building the dataset, and never turns thestationornamecolumns into data variables, whether or notquality_controlis on. Hours whose only value was nulled are therefore missing from the time axis rather than NaN, and a valid row now wins over an empty duplicate at the same time and place, soquality_control=Falsedoes not exactly reproduce 1.1.0.- GHCN quality control expects raw GHCNh units (°C, hPa, m/s, %) under EWB
column names; it runs after
variable_mapping, so sources with other column names are checked too. A custom GHCN-format source in other units (e.g. Kelvin temperatures) must passquality_control=False, or the range check nulls its values. With quality control on, subclasses that overrideGHCN._custom_convert_to_datasetalso receive thestationcolumn, and should drop it (#435).
Fixed
- The
GHCNtarget now quality-controls station observations before scoring (newstation_qcmodule, on by default; passquality_control=Falseto turn it off). It nulls missing-value sentinels such as -999 (e.g. one station reporting -999 C for all of 2020), physically impossible values (e.g. 928 C air temperature), and isolated up-then-down spikes in temperature and dew point. The spike check can also remove a real short-lived extreme such as a heat burst; pressure is not spike-checked, since tropical-cyclone eye passages and derecho wake lows look like spikes (pressure still gets the sentinel and range checks). It also drops the 39 Greenland ice-sheet stations named "MOVING ICE STATION", several of which report temperatures far too warm for weeks at a time (e.g. NEM averages +4.3 C over Jan-Mar 2023); this is a stopgap until a climatology or neighbor-station check exists. GHCN scores for cases touching affected stations change, and a case whose only stations are excluded is no longer scored against GHCN (#431). GHCNandLSRnow subset correctly for case regions that cross the antimeridian. They filtered on the region'stotal_bounds, which for a crossing region is -180..180, so the whole latitude band was kept (e.g. a 166.5E-190E box took stations from Alaska to Scandinavia). They now use the same wrapped bounds as the gridded targets. A region spanning 359 degrees of longitude or more (e.g. the 0E-359.75E boxes of cases 1000-1003) is still treated as global, rather than losing the stations just west of 0.LSRalso no longer drops a region whose east edge is exactly 180, which was converted to -180 (this also makes LSR select the near-global boxes, which it previously left empty). Default (events.yaml) scores are unchanged; GHCN and LSR scores for the affected marginal-temperature and long-event cases change (#432).
Full changelog: https://github.com/brightbandtech/ExtremeWeatherBench/compare/v1.1.0...v1.1.1
Files
brightbandtech/ExtremeWeatherBench-v1.1.1.zip
Additional details
Related works
- Is supplement to
- Software: https://github.com/brightbandtech/ExtremeWeatherBench/tree/v1.1.1 (URL)
Software
- Repository URL
- https://github.com/brightbandtech/ExtremeWeatherBench