A Gas-Weighted Degree Day (GWDD) is a measure of weather-driven natural gas demand that weights temperature by regional gas consumption. Unlike standard Heating Degree Days (HDDs), GWDDs assign more weight to high-consumption regions like the Midwest and Mid-Atlantic, making them a more accurate signal for storage draws and price moves in the natural gas market.
Most weather services report Heating Degree Days (HDDs) as a simple national average. A cold snap in Montana gets the same weight as a cold snap in Ohio, even though Ohio consumes roughly 10x more natural gas. This creates a disconnect between the weather data traders see and the actual demand signal that drives storage draws and prices.
Equal-area or population-weighted average of max(0, 65°F - T) across the Lower 48. Treats all regions the same regardless of gas consumption.
Consumption-weighted average using EIA regional gas demand data. Regions that burn more gas carry more weight in the national figure.
GasAlpha calculates Gas-Weighted Degree Days by extracting forecast temperatures from multiple weather models, computing regional heating degree days across the 9 EIA census divisions, and weighting each region by its share of national gas consumption. The result is a single number that reflects where heating demand actually matters for the gas market.
Unlike standard population-weighted HDDs, GWDDs emphasize high-consumption regions where gas actually gets burned during heating season. This makes GWDDs a more accurate proxy for storage draws and price sensitivity.
GasAlpha runs four independent weather models to provide a consensus view and quantify forecast uncertainty:
| Model | Source | Resolution | Cycles | Forecast Range |
|---|---|---|---|---|
| GFS | NOAA / NCEP | 0.25° (~28km) | 00z, 12z | 14 days |
| GEFS | NOAA / NCEP | 0.25° ensemble mean | 00z, 12z | 10 days |
| IFS | ECMWF | ~9km (operational) | 00z, 12z | 10 days |
| AIFS | ECMWF (AI) | ~28km | 00z, 12z | 10 days |
GasAlpha projects weekly EIA storage changes using a regression model calibrated to the modern market regime. The model uses observed temperature data and GWDD estimates to predict weekly storage draws and injections.
Projections carry confidence tiers that decrease with forecast lead time, reflecting the inherent uncertainty in extended-range weather forecasts.
The GasAlpha dashboard updates automatically 4 times daily, timed to ensure all models from each cycle are available before processing:
| Update (UTC) | Central Time | Models Captured |
|---|---|---|
| 05:00 UTC | 12:00 AM CT | GFS / GEFS 00z |
| 09:00 UTC | 4:00 AM CT | All models 00z (incl. IFS/AIFS) |
| 13:00 UTC | 8:00 AM CT | Morning refresh — full 00z snapshot |
| 21:00 UTC | 4:00 PM CT | All models 12z — full 12z snapshot |
Weather models take several hours to process after initialization. The dashboard captures each model as soon as its data becomes available:
| Model | Cycle | Available (UTC) | Central Time | First Captured |
|---|---|---|---|---|
| GFS | 00z | ~05:00 UTC | ~12:00 AM CT | 05:00 UTC run |
| GFS | 12z | ~17:00 UTC | ~12:00 PM CT | 21:00 UTC run |
| GEFS | 00z | ~05:00 UTC | ~12:00 AM CT | 05:00 UTC run |
| GEFS | 12z | ~17:00 UTC | ~12:00 PM CT | 21:00 UTC run |
| IFS | 00z | ~08:00 UTC | ~3:00 AM CT | 09:00 UTC run |
| IFS | 12z | ~20:00 UTC | ~3:00 PM CT | 21:00 UTC run |
| AIFS | 00z | ~08:00 UTC | ~3:00 AM CT | 09:00 UTC run |
| AIFS | 12z | ~20:00 UTC | ~3:00 PM CT | 21:00 UTC run |
Henry Hub prompt pricing updates every 5 minutes during NYMEX trading hours.
Every weather model initializes from a snapshot of current atmospheric observations — surface stations, radiosondes, satellite retrievals, aircraft reports, and ocean buoys. These observations are assimilated into the model's starting state through a process called data assimilation. The quality and quantity of observations available at initialization time has a direct effect on forecast accuracy, which is why the two main cycles — 00z and 12z — can produce meaningfully different results even on the same day.
Model cycles are named for the UTC time of their initialization. The 00z cycle initializes at midnight UTC (6pm CT / 7pm ET the prior evening) and the 12z cycle initializes at noon UTC (6am CT / 7am ET). Both cycles run twice daily for GFS, GEFS, IFS, and AIFS. The models take several hours to process after initialization before forecast data becomes available for download.
| Cycle | Initializes (UTC) | Data Available | GasAlpha Captures |
|---|---|---|---|
| 00z | Midnight UTC | ~05:00–08:00 UTC | 05:00 UTC (GFS/GEFS), 09:00 UTC (IFS/AIFS), 13:00 UTC (full snapshot) |
| 12z | Noon UTC | ~17:00–20:00 UTC | 21:00 UTC (all models) |
Each cycle ingests a fresh set of observations. Between the 00z and 12z initialization windows, additional upper-air balloon soundings, aircraft data, and satellite passes become available. When the atmosphere is in a transitional pattern — a front moving through, a ridge building, a storm deepening — the 12z run can see that evolution in ways the 00z couldn't. This is why 12z can sometimes show a dramatically different GWDD total than the prior 00z, especially in the extended range beyond day 5.
There is no universally correct answer, but here is a practical framework:
Model skill degrades rapidly beyond day 7. In the day 1–3 range, 00z and 12z typically agree closely and both are reliable. In the day 4–7 range, meaningful run-to-run differences are normal and expected. Beyond day 7, individual model runs should be treated as probabilistic guidance, not point forecasts. A 10-day GWDD total that includes days 8–10 carries substantially more uncertainty than one anchored to the near-term window.
This is why large cycle-to-cycle swings in the 10-day GWDD — even 50–100 GWDDs — are not necessarily a data quality issue. They reflect genuine forecast uncertainty in a volatile atmospheric pattern. The appropriate response is to widen your confidence interval, not to anchor on either run exclusively.
GasAlpha is a forecasting tool, not a crystal ball. Important limitations to understand: