Journal article
Balancing Informativity and Predictability in Circulation Type Forecasts: A Case Study of Energy Demand in Great Britain
- Abstract:
- Weather regimes and weather patterns, here jointly referred to as circulation types, are used to generate forecasts for a variety of applications, such as energy demand and flood risk. However, there are usually many different choices available for precisely which circulation types to use. Ideally, one would like to use circulation types that are both highly informative for the application and also highly predictable, but in practice, there is often a tradeoff between informativity and predictability. We present a simple, general framework for how to construct a circulation type forecast that optimally balances these factors by segueing between different choices of circulation types at different lead times based on information‐theoretic considerations. As an example, we apply this framework to the case of forecasting energy demand in Great British winters. We compare a set of 30 weather patterns produced by the UK Met Office with the much simpler two‐state framework consisting of a positive and negative North Atlantic Oscillation (NAO) regime and show how to optimally combine the two across a winter season.
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Version of record, pdf, 3.1MB, Terms of use)
-
- Publisher copy:
- 10.1002/met.70078
Authors
+ Natural Environment Research Council
More from this funder
- Funder identifier:
- https://ror.org/02b5d8509
- Publisher:
- Wiley
- Journal:
- Meteorological Applications More from this journal
- Volume:
- 32
- Issue:
- 4
- Article number:
- e70078
- Publication date:
- 2025-08-25
- Acceptance date:
- 2025-07-08
- DOI:
- EISSN:
-
1469-8080
- ISSN:
-
1350-4827
- Language:
-
English
- Keywords:
- Source identifiers:
-
3230811
- Deposit date:
-
2025-08-26
This ORA record was generated from metadata provided by an external service. It has not been edited by the ORA Team.
If you are the owner of this record, you can report an update to it here: Report update to this record