<?xml version="1.0" encoding="UTF-8"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:lang="en">
  <teiHeader>
    <fileDesc>
      <titleStmt>
        <title>WeatherBench: A Benchmark Dataset for Data-Driven Weather Forecasting</title>
        <author>Stephan Rasp</author>
        <author>Peter D. Dueben</author>
        <author>Sebastian Scher</author>
        <author>Jonathan A. Weyn</author>
      </titleStmt>
      <publicationStmt>
        <p>Tag layer of the DHSS Meta-Tagging Project. The article text is reproduced from the
           staged copy named in sourceDesc and is not altered; the tags are held separately in
           standOff so that overlapping and nested spans are preserved.</p>
      </publicationStmt>
      <sourceDesc>
        <bibl>
          <title>WeatherBench: A Benchmark Dataset for Data-Driven Weather Forecasting</title>
          <date>2020</date>
          <publisher>Journal of Advances in Modeling Earth Systems / arXiv</publisher>
          <idno type="DOI">10.1029/2020MS002203</idno>
          <idno type="arXiv">2002.00469</idno>
          <idno type="record">rasp2020-weatherbench</idno>
          <note type="staged-file">rasp2020-weatherbench.txt, the project's staged copy</note>
          <note type="text-sha1">0c96639358562db217f8a257d7acc3491983b294</note>
          <note type="rights">arxiv-open</note>
        </bibl>
      </sourceDesc>
    </fileDesc>
    <profileDesc>
      <textClass><keywords><term>earth-science</term></keywords></textClass>
      <particDesc>
        <person xml:id="paper"><p>the paper's own words</p></person>
        <person xml:id="tagger"><p>the tag layer; a sentence written by the tagger about the
          paper, always anchored to a quotation but not itself a quotation</p></person>
      </particDesc>
    </profileDesc>
    <revisionDesc>
      <change when="2026-10-06"
              who="build_paper_edition.py">132 spans located by searching the stored text for the quote's exact words, allowing any whitespace between them</change>
    </revisionDesc>
  </teiHeader>
  <standOff>
    <spanGrp type="tags">
      <span xml:id="t0" from="#a5" to="#a6" type="claim_type" ana="#claim_type" resp="#paper">method</span>
      <span xml:id="t1" from="#a27" to="#a28" type="phenomenon" ana="#phenomenon" resp="#paper">data-driven medium-range weather forecasting</span>
      <span xml:id="t2" from="#a36" to="#a37" type="method" ana="#method" resp="#paper">system-or-tool-building<term>system-or-tool-building</term></span>
      <span xml:id="t3" from="#a84" to="#a89" type="mechanisms" ana="#mechanisms[0]" resp="#tagger" cert="0.9">Hourly sampling over 40 years gives about 350,000 samples, but consecutive hours are not independent; assuming one new weather situation per day leaves about 15,000, which is the count that bears on overfitting.<term>temporal correlation shrinks the usable training set</term></span>
      <span xml:id="t4" from="#a12" to="#a13" type="limitations" ana="#limitations[0]" resp="#tagger">current numerical weather prediction models still fall short for many applications<note>what this limits: the motivation for the benchmark: NUMERICAL WEATHER PREDICTION (NWP) MODELS STILL HAVE SHORTCOMING FOR MANY IMPORTANT APPLICATIONS</note></span>
      <span xml:id="t5" from="#a100" to="#a101" type="limitations" ana="#limitations[1]" resp="#tagger">The benchmark does not cover probabilistic forecasting, only deterministic scores.<note>what this limits: any probabilistic use of the benchmark: ONE IMPORTANT ASPECT THAT IS NOT CURRENTLY ADDRESSED BY THIS BENCHMARK IS PROBABILISTIC FORECASTING</note></span>
      <span xml:id="t6" from="#a110" to="#a111" type="limitations" ana="#limitations[2]" resp="#tagger">Climate-timescale prediction is outside the benchmark&#x27;s scope.<note>what this limits: any climate-timescale use: ANOTHER ASPECT THAT IS UNTOUCHED BY THE BENCHMARK CHALLENGE PROPOSED HERE IS CLIMATE PREDICTION</note></span>
      <span xml:id="t7" from="#a108" to="#a109" type="limitations" ana="#limitations[3]" resp="#tagger">Extreme weather events are deliberately excluded from the evaluation, with no standard metric offered for them.<note>what this limits: every score computed on this benchmark, which is a score on non-extremes: WE DECIDED TO OMIT EXTREMES FOR NOW BUT USERS ARE ENCOURAGED TO CHOSE THEIR OWN VERIFICATION OF EXTREMES</note></span>
      <span xml:id="t8" from="#a78" to="#a79" type="limitations" ana="#limitations[4]" resp="#tagger">The poor performance of the iterative CNN baseline may reflect the deliberately simple architecture rather than a property of iterative forecasting.<note>what this limits: the iterative CNN baseline result: THE POOR SKILL OF THE ITERATIVE FORECAST COULD EASILY BE A RESULT OF USING AN OVERLY SIMPLISTIC NETWORK ARCHITECTURE</note></span>
      <span xml:id="t9" from="#a65" to="#a67" type="limitations" ana="#limitations[5]" resp="#tagger" cert="1.0">The benchmark&#x27;s primary metric was chosen for ease of computation and for matching the usual machine-learning loss, not for being the right measure of forecast quality.<note>what this limits: a ranking on this benchmark as a ranking of forecast quality: the primary metric was chosen because it is easy to compute and mirrors the loss used for most ML applications</note></span>
      <span xml:id="t10" from="#a87" to="#a91" type="limitations" ana="#limitations[6]" resp="#tagger" cert="1.0">The usable amount of training data is far smaller than the raw count, by the authors&#x27; own assumption, and whether it suffices is stated to be unknown.<note>what this limits: the training-set size for this benchmark: 40 years of hourly data is around 350,000 samples, which the authors reduce to about 15,000 independent ones under a stated assumption, with sufficiency unknown without empirical evidence</note></span>
      <span xml:id="t11" from="#a97" to="#a98" type="limitations" ana="#limitations[7]" resp="#tagger" cert="1.0">Scaling the approach to the resolutions likely required runs into hardware, which the authors name as the binding constraint.<note>what this limits: the feasibility of a competitive data-driven weather model: the authors state high resolutions would be needed and that GPU RAM quickly becomes a limitation</note></span>
      <span xml:id="t12" from="#a107" to="#a109" type="limitations" ana="#limitations[8]" resp="#tagger" cert="1.0">THE BENCHMARK EXCLUDES THE CASE IT CALLS MOST IMPORTANT TO SOCIETY, AND SAYS SO: extreme events `will contribute little to regular verification metrics like the RMSE` yet `for society these events are highly important`. The exclusion is declared, reasoned and handed to the user - `users are encouraged to chose their own verification of extremes` - which means any two WeatherBench results on extremes are not comparable BY THE BENCHMARK&#x27;S OWN DESIGN.</span>
      <span xml:id="t13" from="#a1" to="#a2" type="transfers" ana="#transfers[0]" resp="#tagger">deep learning / data-driven methods (developed for image recognition and NLP) applied to weather forecasting</span>
      <span xml:id="t14" from="#a7" to="#a8" type="controls" ana="#controls[0]" resp="#tagger" cert="0.8">baseline scores from linear regression, deep learning and purely physical forecasting models, published with the benchmark<note>eliminates: that a data-driven forecast&#x27;s apparent skill exceeds what simple statistical or existing physical models already achieve · outcome: held</note></span>
      <span xml:id="t15" from="#a11" to="#a14" type="concepts" ana="#concepts[4]" resp="#paper">numerical weather prediction<term>numerical weather prediction</term></span>
      <span xml:id="t16" from="#a65" to="#a67" type="concepts" ana="#concepts[5]" resp="#paper">root mean squared error<term>root mean squared error</term></span>
      <span xml:id="t17" from="#a84" to="#a85" type="concepts" ana="#concepts[6]" resp="#paper">training data<term>training data</term></span>
      <span xml:id="t18" from="#a107" to="#a109" type="concepts" ana="#concepts[7]" resp="#paper" cert="1.0">extremes<term>extremes</term></span>
      <span xml:id="t19" from="#a17" to="#a18" type="concepts" ana="#concepts[8]" resp="#paper" cert="0.95">post-processing<term>post-processing</term></span>
      <span xml:id="t20" from="#a17" to="#a18" type="concepts" ana="#concepts[9]" resp="#paper" cert="0.95">statistical forecasting<term>statistical forecasting</term></span>
      <span xml:id="t21" from="#a19" to="#a22" type="concepts" ana="#concepts[10]" resp="#paper" cert="0.95">nowcasting<term>nowcasting</term></span>
      <span xml:id="t22" from="#a23" to="#a26" type="concepts" ana="#concepts[11]" resp="#paper" cert="0.95">hybrid modeling<term>hybrid modeling</term></span>
      <span xml:id="t23" from="#a23" to="#a26" type="concepts" ana="#concepts[12]" resp="#paper" cert="0.95">machine learning emulators<term>machine learning emulators</term></span>
      <span xml:id="t24" from="#a27" to="#a31" type="concepts" ana="#concepts[13]" resp="#paper" cert="0.95">purely-data driven prediction<term>purely-data driven prediction</term></span>
      <span xml:id="t25" from="#a27" to="#a31" type="concepts" ana="#concepts[14]" resp="#paper" cert="0.95">medium-range<term>medium-range</term></span>
      <span xml:id="t26" from="#a27" to="#a31" type="concepts" ana="#concepts[15]" resp="#paper" cert="0.95">baroclinic instabilities<term>baroclinic instabilities</term></span>
      <span xml:id="t27" from="#a27" to="#a31" type="concepts" ana="#concepts[16]" resp="#paper" cert="0.95">tropical cyclogenesis<term>tropical cyclogenesis</term></span>
      <span xml:id="t28" from="#a32" to="#a35" type="concepts" ana="#concepts[17]" resp="#paper" cert="0.95">common benchmark challenge<term>common benchmark challenge</term></span>
      <span xml:id="t29" from="#a32" to="#a35" type="concepts" ana="#concepts[18]" resp="#paper" cert="0.95">Benchmark datasets<term>Benchmark datasets</term></span>
      <span xml:id="t30" from="#a48" to="#a55" type="concepts" ana="#concepts[19]" resp="#paper" cert="0.95">ERA5 reanalysis dataset<term>ERA5 reanalysis dataset</term></span>
      <span xml:id="t31" from="#a48" to="#a55" type="concepts" ana="#concepts[20]" resp="#paper" cert="0.95">Reanalysis datasets<term>Reanalysis datasets</term></span>
      <span xml:id="t32" from="#a48" to="#a55" type="concepts" ana="#concepts[21]" resp="#paper" cert="0.95">forecast model<term>forecast model</term></span>
      <span xml:id="t33" from="#a48" to="#a55" type="concepts" ana="#concepts[22]" resp="#paper" cert="0.95">observations<term>observations</term></span>
      <span xml:id="t34" from="#a61" to="#a62" type="concepts" ana="#concepts[23]" resp="#paper" cert="0.95">split the data into three parts<term>split the data into three parts</term></span>
      <span xml:id="t35" from="#a61" to="#a62" type="concepts" ana="#concepts[24]" resp="#paper" cert="0.95">training dataset<term>training dataset</term></span>
      <span xml:id="t36" from="#a63" to="#a64" type="concepts" ana="#concepts[25]" resp="#paper" cert="0.95">validation dataset<term>validation dataset</term></span>
      <span xml:id="t37" from="#a63" to="#a64" type="concepts" ana="#concepts[26]" resp="#paper" cert="0.95">third, testing, dataset<term>third, testing, dataset</term></span>
      <span xml:id="t38" from="#a68" to="#a69" type="concepts" ana="#concepts[27]" resp="#paper" cert="0.95">persistence forecast<term>persistence forecast</term></span>
      <span xml:id="t39" from="#a68" to="#a69" type="concepts" ana="#concepts[28]" resp="#paper" cert="0.95">climatological forecast<term>climatological forecast</term></span>
      <span xml:id="t40" from="#a72" to="#a73" type="concepts" ana="#concepts[29]" resp="#paper" cert="0.95">direct predictions<term>direct predictions</term></span>
      <span xml:id="t41" from="#a72" to="#a73" type="concepts" ana="#concepts[30]" resp="#paper" cert="0.95">iterative model<term>iterative model</term></span>
      <span xml:id="t42" from="#a72" to="#a73" type="concepts" ana="#concepts[31]" resp="#paper" cert="0.95">previous output as input<term>previous output as input</term></span>
      <span xml:id="t43" from="#a74" to="#a75" type="concepts" ana="#concepts[32]" resp="#paper" cert="0.95">fully-convolutional neural network<term>fully-convolutional neural network</term></span>
      <span xml:id="t44" from="#a74" to="#a75" type="concepts" ana="#concepts[33]" resp="#paper" cert="0.95">translational invariances<term>translational invariances</term></span>
      <span xml:id="t45" from="#a74" to="#a75" type="concepts" ana="#concepts[34]" resp="#paper" cert="0.95">periodic convolutions<term>periodic convolutions</term></span>
      <span xml:id="t46" from="#a80" to="#a81" type="concepts" ana="#concepts[35]" resp="#paper" cert="0.95">unrealistically smooth fields<term>unrealistically smooth fields</term></span>
      <span xml:id="t47" from="#a80" to="#a81" type="concepts" ana="#concepts[36]" resp="#paper" cert="0.95">simple RMSE loss<term>simple RMSE loss</term></span>
      <span xml:id="t48" from="#a80" to="#a81" type="concepts" ana="#concepts[37]" resp="#paper" cert="0.95">chaotic behavior<term>chaotic behavior</term></span>
      <span xml:id="t49" from="#a82" to="#a83" type="concepts" ana="#concepts[38]" resp="#paper" cert="0.95">image-to-image translation<term>image-to-image translation</term></span>
      <span xml:id="t50" from="#a82" to="#a83" type="concepts" ana="#concepts[39]" resp="#paper" cert="0.95">assumption of translation invariance<term>assumption of translation invariance</term></span>
      <span xml:id="t51" from="#a92" to="#a93" type="concepts" ana="#concepts[40]" resp="#paper" cert="0.95">transfer learning<term>transfer learning</term></span>
      <span xml:id="t52" from="#a94" to="#a95" type="concepts" ana="#concepts[41]" resp="#paper" cert="0.95">data augmentation<term>data augmentation</term></span>
      <span xml:id="t53" from="#a96" to="#a99" type="concepts" ana="#concepts[42]" resp="#paper" cert="0.95">CPU RAM<term>CPU RAM</term></span>
      <span xml:id="t54" from="#a96" to="#a99" type="concepts" ana="#concepts[43]" resp="#paper" cert="0.95">GPU RAM<term>GPU RAM</term></span>
      <span xml:id="t55" from="#a100" to="#a102" type="concepts" ana="#concepts[44]" resp="#paper" cert="0.95">probabilistic forecasting<term>probabilistic forecasting</term></span>
      <span xml:id="t56" from="#a100" to="#a102" type="concepts" ana="#concepts[45]" resp="#paper" cert="0.95">ensemble<term>ensemble</term></span>
      <span xml:id="t57" from="#a100" to="#a102" type="concepts" ana="#concepts[46]" resp="#paper" cert="0.95">Monte Carlo forecast<term>Monte Carlo forecast</term></span>
      <span xml:id="t58" from="#a100" to="#a102" type="concepts" ana="#concepts[47]" resp="#paper" cert="0.95">parametric distribution<term>parametric distribution</term></span>
      <span xml:id="t59" from="#a103" to="#a106" type="concepts" ana="#concepts[48]" resp="#paper" cert="0.95">forecast uncertainty<term>forecast uncertainty</term></span>
      <span xml:id="t60" from="#a103" to="#a106" type="concepts" ana="#concepts[49]" resp="#paper" cert="0.95">spread (ensemble standard deviation) to error (RMSE) ratio<term>spread (ensemble standard deviation) to error (RMSE) ratio</term></span>
      <span xml:id="t61" from="#a103" to="#a106" type="concepts" ana="#concepts[50]" resp="#paper" cert="0.95">proper probabilistic scoring rule<term>proper probabilistic scoring rule</term></span>
      <span xml:id="t62" from="#a103" to="#a106" type="concepts" ana="#concepts[51]" resp="#paper" cert="0.95">continuous ranked probability score (CRPS)<term>continuous ranked probability score (CRPS)</term></span>
      <span xml:id="t63" from="#a112" to="#a113" type="concepts" ana="#concepts[52]" resp="#paper" cert="0.95">Climate models<term>Climate models</term></span>
      <span xml:id="t64" from="#a112" to="#a113" type="concepts" ana="#concepts[53]" resp="#paper" cert="0.95">prediction horizon of the atmosphere<term>prediction horizon of the atmosphere</term></span>
      <span xml:id="t65" from="#a114" to="#a115" type="concepts" ana="#concepts[54]" resp="#paper" cert="0.95">historical manifold of states<term>historical manifold of states</term></span>
      <span xml:id="t66" from="#a114" to="#a115" type="concepts" ana="#concepts[55]" resp="#paper" cert="0.95">Plain neural networks<term>Plain neural networks</term></span>
      <span xml:id="t67" from="#a116" to="#a117" type="concepts" ana="#concepts[56]" resp="#paper" cert="0.95">generative adverserial networks (GANs)<term>generative adverserial networks (GANs)</term></span>
      <span xml:id="t68" from="#a116" to="#a117" type="concepts" ana="#concepts[57]" resp="#paper" cert="0.95">Conditional GANs<term>Conditional GANs</term></span>
      <span xml:id="t69" from="#a48" to="#a55" type="unhoused_relations" ana="#unhoused_relations[0]" resp="#tagger" cert="0.95">ERA5 reanalysis dataset → forecast model with the available observations<note>ERA5 combines a forecast model with observations; composed-from is absent from the edge registry.</note></span>
      <span xml:id="t70" from="#a100" to="#a102" type="unhoused_relations" ana="#unhoused_relations[1]" resp="#tagger" cert="0.95">probabilistic forecasting → ensemble<note>Physical probabilistic forecasts are implemented by an ensemble; implemented-by is absent from the edge registry.</note></span>
      <span xml:id="t71" from="#a100" to="#a102" type="unhoused_relations" ana="#unhoused_relations[2]" resp="#tagger" cert="0.95">ensemble → Monte Carlo forecast<note>The ensemble is treated as a Monte Carlo forecast; method-role is absent from the edge registry.</note></span>
      <span xml:id="t72" from="#a103" to="#a106" type="unhoused_relations" ana="#unhoused_relations[3]" resp="#tagger" cert="0.95">forecast uncertainty → spread (ensemble standard deviation) to error (RMSE) ratio<note>The spread-to-error ratio is a first-order approximation for reliability; diagnostic-for is absent from the edge registry.</note></span>
      <span xml:id="t73" from="#a103" to="#a106" type="unhoused_relations" ana="#unhoused_relations[4]" resp="#tagger" cert="0.95">forecast uncertainty → continuous ranked probability score (CRPS)<note>CRPS is a more stringent reliability test; diagnostic-for is absent from the edge registry.</note></span>
      <span xml:id="t74" from="#a116" to="#a117" type="unhoused_relations" ana="#unhoused_relations[5]" resp="#tagger" cert="0.9">Conditional GANs → unrealistically smooth fields<note>Conditional GANs could potentially alleviate smooth mean-loss predictions; may-remedy is absent from the edge registry.</note></span>
      <span xml:id="t75" from="#a23" to="#a26" type="unhoused_relations" ana="#unhoused_relations[6]" resp="#tagger" cert="0.95">machine learning emulators → hybrid modeling<note>Machine-learning emulators are combined with physical components in hybrid modeling; combined-with is absent from the edge registry.</note></span>
      <span xml:id="t76" from="#a27" to="#a31" type="unhoused_relations" ana="#unhoused_relations[7]" resp="#tagger" cert="0.95">purely-data driven prediction → post-processing<note>The paper sets pure medium-range prediction apart from post-processing; set-apart-from is absent from the cue-governed registry.</note></span>
      <span xml:id="t77" from="#a27" to="#a31" type="unhoused_relations" ana="#unhoused_relations[8]" resp="#tagger" cert="0.95">purely-data driven prediction → nowcasting<note>The paper sets pure medium-range prediction apart from nowcasting; set-apart-from is absent from the cue-governed registry.</note></span>
      <span xml:id="t78" from="#a61" to="#a62" type="unhoused_relations" ana="#unhoused_relations[9]" resp="#tagger" cert="0.95">training dataset → split the data into three parts<note>Training is one partition of the three-way data split; partition-of is absent from the cue-governed registry.</note></span>
      <span xml:id="t79" from="#a63" to="#a64" type="unhoused_relations" ana="#unhoused_relations[10]" resp="#tagger" cert="0.95">validation dataset → split the data into three parts<note>Validation is one partition of the three-way data split; partition-of is absent from the cue-governed registry.</note></span>
      <span xml:id="t80" from="#a63" to="#a64" type="unhoused_relations" ana="#unhoused_relations[11]" resp="#tagger" cert="0.95">third, testing, dataset → split the data into three parts<note>Testing is the held final-evaluation partition; partition-of is absent from the cue-governed registry.</note></span>
      <span xml:id="t81" from="#a84" to="#a86" type="senses" ana="#senses[0]" resp="#tagger" cert="1.0">training samples - AS RAW COUNT: around 350,000, being 40 years of hourly data</span>
      <span xml:id="t82" from="#a88" to="#a90" type="senses" ana="#senses[1]" resp="#tagger" cert="1.0">training samples - AS EFFECTIVE COUNT: around 15,000, once temporal correlation is taken into account under the assumption of one new weather situation per day</span>
      <span xml:id="t83" from="#a120" to="#a121" type="senses" ana="#senses[2]" resp="#tagger" cert="1.0">success on this benchmark - defined by a SINGLE metric over two fields, which the paper presents as a virtue of the design</span>
      <span xml:id="t84" from="#a65" to="#a66" type="senses" ana="#senses[3]" resp="#tagger" cert="0.95">primary metric - chosen for computational convenience and for matching the ML community&#x27;s loss function, not for meteorological importance; the paper states both reasons</span>
      <span xml:id="t85" from="#a107" to="#a109" type="senses" ana="#senses[4]" resp="#tagger" cert="1.0">`extremes` - LEFT UNDEFINED ON PURPOSE, AND THE BENCHMARK DROPS THE PHENOMENON RATHER THAN PICK A DEFINITION: `defining extremes is ambiguous which is why there is no standard metric for evaluating extremes ... we decided to omit extremes for now but users are encouraged to chose their own verification`. THE AMBIGUITY IS UPSTREAM OF THE METRIC AND THE MISSING METRIC IS UPSTREAM OF THE BENCHMARK&#x27;S SCOPE - a definitional problem propagating into what a whole field will be measured on.</span>
      <span xml:id="t86" from="#a17" to="#a18" type="senses" ana="#senses[5]" resp="#tagger" cert="0.95">Post-processing - ML correction of physical-model output bias</span>
      <span xml:id="t87" from="#a17" to="#a18" type="senses" ana="#senses[6]" resp="#tagger" cert="0.95">Statistical forecasting - ML prediction of variables absent from physical-model output</span>
      <span xml:id="t88" from="#a19" to="#a22" type="senses" ana="#senses[7]" resp="#tagger" cert="0.95">Nowcasting - radar-only precipitation extrapolation up to six hours</span>
      <span xml:id="t89" from="#a23" to="#a26" type="senses" ana="#senses[8]" resp="#tagger" cert="0.95">Hybrid weather model - physical dynamics with selected uncertain or expensive components replaced by ML emulators</span>
      <span xml:id="t90" from="#a27" to="#a31" type="senses" ana="#senses[9]" resp="#tagger" cert="0.95">WeatherBench medium range - direct global atmospheric-flow prediction at three- and five-day leads</span>
      <span xml:id="t91" from="#a48" to="#a55" type="senses" ana="#senses[10]" resp="#tagger" cert="0.95">ERA5 reanalysis - forecast-model and observation synthesis used as atmospheric truth proxy</span>
      <span xml:id="t92" from="#a63" to="#a64" type="senses" ana="#senses[11]" resp="#tagger" cert="0.95">Train / validation / test - fitting data, tuning data, and held final-evaluation data</span>
      <span xml:id="t93" from="#a68" to="#a69" type="senses" ana="#senses[12]" resp="#tagger" cert="0.95">Persistence forecast - tomorrow’s field set equal to today’s field</span>
      <span xml:id="t94" from="#a72" to="#a73" type="senses" ana="#senses[13]" resp="#tagger" cert="0.95">Direct / iterative forecast - lead-specific model versus recursively applied short-lead model</span>
      <span xml:id="t95" from="#a74" to="#a75" type="senses" ana="#senses[14]" resp="#tagger" cert="0.95">CNN weather baseline - fully convolutional Z500/T850 model with longitude-periodic kernels</span>
      <span xml:id="t96" from="#a92" to="#a93" type="senses" ana="#senses[15]" resp="#tagger" cert="0.95">Transfer learning - pretrain on related simulations, then fine-tune on target observations</span>
      <span xml:id="t97" from="#a94" to="#a95" type="senses" ana="#senses[16]" resp="#tagger" cert="0.95">Physical-field augmentation - overfitting control constrained by non-interchangeable spatial directions</span>
      <span xml:id="t98" from="#a100" to="#a102" type="senses" ana="#senses[17]" resp="#tagger" cert="0.95">Probabilistic forecast - ensemble or parametric distribution expressing uncertainty</span>
      <span xml:id="t99" from="#a103" to="#a106" type="senses" ana="#senses[18]" resp="#tagger" cert="0.95">Forecast reliability - uncertainty accurately indicates error</span>
      <span xml:id="t100" from="#a112" to="#a113" type="senses" ana="#senses[19]" resp="#tagger" cert="0.95">Weather / climate prediction - future state before the horizon versus long-term statistics</span>
      <span xml:id="t101" from="#a114" to="#a115" type="senses" ana="#senses[20]" resp="#tagger" cert="0.95">Climate-change extrapolation - future states outside the historical training manifold</span>
      <span xml:id="t102" from="#a1" to="#a2" type="claim_relations" ana="#claim_relations[0]" resp="#tagger">builds-on → deep learning (data-driven prediction)</span>
      <span xml:id="t103" from="#a76" to="#a77" type="claim_relations" ana="#claim_relations[1]" resp="#tagger">replicates → Scher and Messori (2019a)</span>
      <span xml:id="t104" from="#a48" to="#a49" type="claim_relations" ana="#claim_relations[2]" resp="#tagger">builds-on → Hersbach et al. (2020), the ERA5 reanalysis dataset</span>
      <span xml:id="t105" from="#a118" to="#a119" type="claim_relations" ana="#claim_relations[3]" resp="#tagger">builds-on → Ebert-Uphoff et al. (2017), criteria for benchmark datasets</span>
      <span xml:id="t106" from="#a9" to="#a10" type="concept_edges" ana="#concept_edges[0]" resp="#tagger" cert="0.95">deep learning —is-a→ machine learning<note>strength of the relation: 0.9 · note: Defined in the paper&#x27;s first sentence of body text, and the definition carries the mechanism with it - multi-layered artificial neural networks.</note><term>deep learning</term><term>machine learning</term></span>
      <span xml:id="t107" from="#a65" to="#a66" type="concept_edges" ana="#concept_edges[1]" resp="#tagger" cert="0.95">root mean squared error —operationalised-as→ benchmark<note>strength of the relation: 0.9 · note: THE CHOICE IS MADE ON GROUNDS THAT ARE NOT ABOUT WEATHER: the metric was picked &#x27;because it is easy to compute and mirrors the loss used for most ML applications&#x27;. Convenience and alignment with the modelling community decide what counts as success on this benchmark - and the paper says so outright. The record already carries a sense noting success here is a SINGLE metric over two fields.
Audit 2026-09-28: DOUBTFUL - read against its span and kept, but RMSE is the benchmark&#x27;s primary metric; operationalised-as runs from the benchmark, not to it.</note><term>root mean squared error</term><term>benchmark</term></span>
      <span xml:id="t108" from="#a72" to="#a73" type="concept_edges" ana="#concept_edges[4]" resp="#tagger" cert="0.95">iterative model —contrasted-with→ direct predictions<note>the relation itself is separately evidenced · strength of the relation: 1 · note: The paper contrasts a single recursively applied model with separate lead-specific models.</note><term>iterative model</term><term>direct predictions</term></span>
      <span xml:id="t109" from="#a80" to="#a81" type="concept_edges" ana="#concept_edges[5]" resp="#tagger" cert="0.95">simple RMSE loss —causes→ unrealistically smooth fields<note>the relation itself is separately evidenced · strength of the relation: 0.8 · note: Weight reflects the paper’s two-factor, likely-cause explanation for over-smoothing.
Audit 2026-09-28: DOUBTFUL - read against its full span and kept, but the span says the smoothness is LIKELY a result of two factors; hedged.</note><term>simple RMSE loss</term><term>unrealistically smooth fields</term></span>
      <span xml:id="t110" from="#a112" to="#a113" type="concept_edges" ana="#concept_edges[6]" resp="#tagger" cert="0.95">weather forecasting —contrasted-with→ Climate models<note>the relation itself is separately evidenced · strength of the relation: 1 · note: The paper explicitly contrasts future-state and long-term-statistics objectives.</note><term>weather forecasting</term><term>Climate models</term></span>
      <span xml:id="t111" from="#a53" to="#a54" type="content_tags" ana="#content_tags.quantities[0]" resp="#tagger">40 — time span of hourly ERA5 raw data</span>
      <span xml:id="t112" from="#a52" to="#a56" type="content_tags" ana="#content_tags.quantities[1]" resp="#tagger">721x1440 — native 0.25-degree ERA5 grid with 37 levels</span>
      <span xml:id="t113" from="#a57" to="#a58" type="content_tags" ana="#content_tags.quantities[2]" resp="#tagger">700 — size of a single vertical level over the full period</span>
      <span xml:id="t114" from="#a29" to="#a30" type="content_tags" ana="#content_tags.quantities[3]" resp="#tagger">3 and 5 — medium-range forecast lead times targeted</span>
      <span xml:id="t115" from="#a15" to="#a16" type="content_tags" ana="#content_tags.quantities[4]" resp="#tagger">50 — typical cap on probabilistic NWP forecasts</span>
      <span xml:id="t116" from="#a59" to="#a60" type="content_tags" ana="#content_tags.quantities[5]" resp="#tagger">191 — size of the full 5.625-degree benchmark dataset</span>
      <span xml:id="t117" from="#a33" to="#a34" type="content_tags" ana="#content_tags.findings[0]" resp="#tagger">benchmark datasets make algorithms quantitatively inter-comparable</span>
      <span xml:id="t118" from="#a3" to="#a4" type="content_tags" ana="#content_tags.findings[1]" resp="#tagger">absence of a common dataset made prior studies hard to compare<note>about this quote: QUOTE RECOVERED FROM THE PAPER&#x27;S OWN CHARACTERS. The recorded quote was LETTERS-ONLY IDENTICAL to this stretch of the staged text but not an exact substring of it - spaces, hyphens, ligature glyphs or mathematical operators differed, so it could never anchor. This is the file&#x27;s own text between the same two letters: not produced by a rule about the damage, copied out of the file. Round-trip checked (the recovered span is letters-only equal to the original) and length-checked. The text as originally recorded is kept in evidence as extracted.</note></span>
      <span xml:id="t119" from="#a40" to="#a41" type="content_tags" ana="#content_tags.findings[2]" resp="#tagger">a geopotential CNN performed best yet could not beat the physical baseline</span>
      <span xml:id="t120" from="#a42" to="#a43" type="content_tags" ana="#content_tags.findings[3]" resp="#tagger">directly-trained networks outperformed iterative forecasts</span>
      <span xml:id="t121" from="#a38" to="#a39" type="content_tags" ana="#content_tags.variables[0]" resp="#tagger">500 hPa geopotential<term>500 hPa geopotential</term></span>
      <span xml:id="t122" from="#a29" to="#a30" type="content_tags" ana="#content_tags.variables[1]" resp="#tagger">forecast lead time<term>forecast lead time</term></span>
      <span xml:id="t123" from="#a45" to="#a46" type="content_tags" ana="#content_tags.variables[4]" resp="#tagger">root mean squared error<term>root mean squared error</term></span>
      <span xml:id="t124" from="#a45" to="#a46" type="content_tags" ana="#content_tags.variables[5]" resp="#tagger">anomaly correlation coefficient<term>anomaly correlation coefficient</term></span>
      <span xml:id="t125" from="#a12" to="#a13" type="content_tags" ana="#content_tags.definitions[0]" resp="#tagger">numerical weather prediction (NWP)<term>numerical weather prediction (NWP)</term></span>
      <span xml:id="t126" from="#a20" to="#a21" type="content_tags" ana="#content_tags.definitions[1]" resp="#tagger">nowcasting<term>nowcasting</term></span>
      <span xml:id="t127" from="#a24" to="#a25" type="content_tags" ana="#content_tags.definitions[2]" resp="#tagger">hybrid modeling<note>about this quote: QUOTE RECOVERED FROM THE PAPER&#x27;S OWN CHARACTERS. The recorded quote was LETTERS-ONLY IDENTICAL to this stretch of the staged text but not an exact substring of it - spaces, hyphens, ligature glyphs or mathematical operators differed, so it could never anchor. This is the file&#x27;s own text between the same two letters: not produced by a rule about the damage, copied out of the file. Round-trip checked (the recovered span is letters-only equal to the original) and length-checked. The text as originally recorded is kept in evidence as extracted.</note><term>hybrid modeling</term></span>
      <span xml:id="t128" from="#a50" to="#a51" type="content_tags" ana="#content_tags.definitions[3]" resp="#tagger">reanalysis<term>reanalysis</term></span>
      <span xml:id="t129" from="#a44" to="#a47" type="content_tags" ana="#content_tags.statistics[0]" resp="#tagger">correlation<term>correlation</term></span>
      <span xml:id="t130" from="#a70" to="#a71" type="content_tags" ana="#content_tags.statistics[1]" resp="#tagger">regression<term>regression</term></span>
      <span xml:id="t131" from="#a104" to="#a105" type="content_tags" ana="#content_tags.statistics[2]" resp="#tagger">standard-deviation<term>standard-deviation</term></span>
    </spanGrp>
  </standOff>
  <text>
    <body>
        <p><anchor xml:id="a0"/> 0 2 0 2</p>
        <p>n u J</p>
        <p>1 1</p>
        <p>] h p -[ Passage withheld — in our stored copy of this paper these characters are set one per token and run backwards, which is what a PDF extractor returns for a table or a caption printed sideways. It is not what the page of the article looks like, so we do not reproduce it. The tags cut from this paper are unaffected. ]</p>
        <p>WeatherBench: A benchmark dataset for data-driven weather forecasting</p>
        <p>Stephan Rasp1, Peter D. Dueben2, Sebastian Scher3, Jonathan A. Weyn4, Soukayna Mouatadid5, and Nils Thuerey1 1Technical University of Munich, Germany 2European Centre for Medium-range Weather Forecasts, Reading, UK 3Department of Meteorology and Bolin Centre for Climate Research, Stockholm University, Sweden 4Department of Atmospheric Sciences, University of Washington, Seattle, USA 5Department of Computer Science, University of Toronto, Canada</p>
        <p>Correspondence: Stephan Rasp (stephan.rasp@tum.de)</p>
        <p>Abstract. <anchor xml:id="a1"/>Data-driven approaches, most prominently deep learning, have become powerful tools for prediction in many<anchor xml:id="a2"/> domains. A natural question to ask is whether data-driven methods could also be used to predict global weather patterns days</p>
        <p>in advance. First studies show promise but <anchor xml:id="a3"/>the lack of a common dataset and evaluation metrics make inter-comparison between studies difficult.<anchor xml:id="a4"/> <anchor xml:id="a5"/>Here we present a benchmark dataset for data-driven medium-range weather forecasting, a topic of</p>
        <p>high scientific interest for atmospheric and computer scientists alike.<anchor xml:id="a6"/> We provide data derived from the ERA5 archive that</p>
        <p>has been processed to facilitate the use in machine learning models. We propose simple and clear evaluation metrics which</p>
        <p>will enable a direct comparison between different methods. <anchor xml:id="a7"/>Further, we provide baseline scores from simple linear regression techniques, deep learning models, as well as purely physical forecasting models.<anchor xml:id="a8"/> The dataset is publicly available at</p>
        <p>https://github.com/pangeo-data/WeatherBench and the companion code is reproducible with tutorials for getting started. We</p>
        <p>hope that this dataset will accelerate research in data-driven weather forecasting.</p>
        <p>1</p>
        <p>Introduction</p>
        <p><anchor xml:id="a9"/>Deep learning, a branch of machine learning based on multi-layered artificial neural networks, has proven to be a powerful tool</p>
        <p>for a wide range of tasks, most notably image recognition and natural language processing<anchor xml:id="a10"/> (LeCun et al., 2015). More recently,</p>
        <p>deep learning has also been used in many fields of natural science. Much of the success of deep learning is based on the ability</p>
        <p>of neural networks to recognize patterns in high-dimensional spaces. A natural question to ask then is whether deep learning</p>
        <p>can also be used to predict future weather patterns.</p>
        <p>Currently, weather (and climate) predictions are based on purely physical computer models, in which the governing equations, or our best approximation thereof, of the atmosphere and ocean are solved on a discrete numerical grid (Bauer et al.,</p>
        <p>2015). Overall, this approach has been very successful. <anchor xml:id="a11"/>However, today’s <anchor xml:id="a12"/>numerical weather prediction (NWP) models still</p>
        <p>have shortcoming for many important applications<anchor xml:id="a13"/>, for example forecasting mesoscale convective systems over Africa<anchor xml:id="a14"/> (Vogel</p>
        <p>et al., 2018). Furthermore, huge amounts of computing power are required, especially for creating probabilistic forecasts which</p>
        <p>1</p>
        <p>are <anchor xml:id="a15"/>usually limited to 50 ensemble members or less<anchor xml:id="a16"/>. For these reasons and the growing popularity of machine learning (ML)</p>
        <p>there has been a growing interest to improve and speed up NWP with data-driven approaches.</p>
        <p><anchor xml:id="a17"/>ML can be applied to weather prediction in many different ways. Two long-standing applications of ML are post-processing</p>
        <p>– the correction of statistical biases in the output of physical models – and statistical forecasting – the prediction of variables</p>
        <p>not directly output by the physical model. Traditionally, this has been done using simple linear techniques but more recently</p>
        <p>modern machine learning approaches like random forests or neural networks have been explored (Gagne et al., 2014; Taillardat</p>
        <p>et al., 2016; McGovern et al., 2017; Lagerquist et al., 2017; Rasp and Lerch, 2018). Typically, these approaches target very</p>
        <p>specific variables or locations whereas the general evolution of the atmosphere is still predicted by a physical model<anchor xml:id="a18"/>. <anchor xml:id="a19"/>Another</p>
        <p>application that has recently been explored using ML is <anchor xml:id="a20"/>nowcasting, which describes the short range (up to 6 hours) prediction<anchor xml:id="a21"/></p>
        <p>of precipitation by directly extrapolating radar observation without a physical model involved<anchor xml:id="a22"/> (Shi et al., 2015, 2017; Agrawal</p>
        <p>et al., 2019; Grönquist et al., 2020).</p>
        <p><anchor xml:id="a23"/>Yet another direction for ML research is <anchor xml:id="a24"/>hybrid modeling, in which a physical model is combined with data-driven components<anchor xml:id="a25"/>, for example replacing heuristic cloud or radiation parameterizations (Chevallier et al., 1998; Krasnopolsky et al.,</p>
        <p>2005; Rasp et al., 2018; Brenowitz and Bretherton, 2018; Yuval and O’Gorman, 2020). The key idea behind these approaches</p>
        <p>is to only replace uncertain (e.g. clouds) or computationally expensive (e.g. line-by-line radiation) model components with</p>
        <p>machine learning emulators and leave other model components (e.g. large-scale dynamics) untouched<anchor xml:id="a26"/>. However such hybrid</p>
        <p>models also have drawbacks. First, the interaction between physical and machine learning components are poorly understood</p>
        <p>and can lead to unexpected instabilities and biases (Brenowitz and Bretherton, 2019). Second, they are difficult to implement</p>
        <p>from a technical perspective because one has to interface the machine learning components with complex climate model code,</p>
        <p>typically written in Fortran.</p>
        <p><anchor xml:id="a27"/>Here we focus on purely-data driven prediction of the global atmospheric flow in the medium-range.<anchor xml:id="a28"/> Specifically, we select</p>
        <p><anchor xml:id="a29"/>lead times of 3 and 5 days<anchor xml:id="a30"/>, for which the atmosphere is still reasonably deterministic but also exhibits complex nonlinear</p>
        <p>behaviour, such as baroclinic instabilities and tropical cyclogenesis. This forecast range is important from a societal point of</p>
        <p>view because it delivers crucial information for disaster preparation, for example for flooding, cold and hot spells or damaging</p>
        <p>winds (Lazo et al., 2009). Creating a good medium-range forecast requires understanding complex atmospheric dynamics</p>
        <p>and the interplay between several variables across a range of scales. This sets this challenge apart from post-processing and</p>
        <p>statistical forecasting, in which the large-scale dynamics are predicted by a physical model, and nowcasting, in which the</p>
        <p>considered evolution is univariate and short-term. In other words, this benchmark closely emulates the task performed by</p>
        <p>physical NWP models<anchor xml:id="a31"/>.</p>
        <p>There are several motivations for considering a purely-data driven approach. As mentioned above current NWP is computationally expensive and, nevertheless, has low skill for certain applications. If data-driven models were able to learn a more</p>
        <p>efficient representation of the underlying dynamical and physical equations, they might enable computationally cheaper forecasts. This can be useful for many applications, for example creating very large ensembles to better estimate the probability</p>
        <p>of extreme events. It is also possible that by learning from a diverse set of data sources, data-driven models can outperform</p>
        <p>physical models in areas where the latter struggle. While in this benchmark challenge the focus is on upper-level fields of</p>
        <p>2</p>
        <p>pressure and temperature – for which physical models perform very well – the hope is that the insights gained from this task</p>
        <p>can be leveraged for more impactful application. Further, recent research into interpretable machine learning might provide</p>
        <p>scientists with new analysis tools (McGovern et al., 2019; Toms et al., 2019). Finally, there is the basic scientific question to</p>
        <p>what extent purely data-driven models can learn the underlying dynamics of the atmosphere.</p>
        <p>Note also that while this benchmark is framed as a data-driven prediction challenge, the proposed framework can also be</p>
        <p>applied to post-processing using the same metrics.</p>
        <p>In machine learning research, the data-driven prediction of future states is an active area of research with applications from</p>
        <p>language translation (Sutskever et al., 2014), over audio signals (Oord et al., 2016), to numerical simulations (Morton et al.,</p>
        <p>2018). In this context, weather forecasts are a particularly challenging task. The behavior is highly complex and non-linear,</p>
        <p>but also exhibits some recurring patterns, albeit only on local scales (Hamill and Whitaker, 2006). As such the the proposed</p>
        <p>benchmark poses interesting challenges for deep learning algorithms, e.g., to evaluate different architectures (Ronneberger</p>
        <p>et al., 2015; He et al., 2015; Huang et al., 2016), regularization methods (Krogh and Hertz, 1992; Srivastava et al., 2014; Xie</p>
        <p>et al., 2017) or optimizers (Graves, 2013; Kingma and Ba, 2014).</p>
        <p>In the last couple of years, several studies (summarized in Section 2) have pioneered data-driven, global, medium-range</p>
        <p>weather prediction. All of them show that there is some potential in this approach but also highlight the need for further</p>
        <p>research. In particular, <anchor xml:id="a32"/>we currently lack a common benchmark challenge to accelerate progress. Benchmark datasets can have</p>
        <p>a huge impact because <anchor xml:id="a33"/>they make different algorithms quantitatively inter-comparable and foster constructive competition<anchor xml:id="a34"/>,</p>
        <p>particularly in a nascent direction of research. Famous examples are the computer vision datasets MNIST (LeCun et al., 1998)</p>
        <p>and ImageNet (Russakovsky et al., 2015). Further, well-curated benchmark datasets make it easier for people from different</p>
        <p>fields to work on a problem<anchor xml:id="a35"/> (Ebert-Uphoff et al., 2017).</p>
        <p>Here, we propose a benchmark problem for data-driven weather forecasting. <anchor xml:id="a36"/>We provide a ready-to-use dataset for download</p>
        <p>along with specific metrics to compare different approaches.<anchor xml:id="a37"/> In this paper, we start by reviewing the previous work done on this</p>
        <p>topic (Section 2), describe the dataset (Section 3) and the evaluation metrics (Section 4), and provide several baseline models</p>
        <p>(Section 5). Finally, we will highlight several promising directions for further research (Section 6) and conclude with a big</p>
        <p>picture view (Section 8).</p>
        <p>2 Overview of previous work</p>
        <p>In this section, we briefly describe the four existing studies on predicting the large-scale atmospheric state in the medium-range</p>
        <p>with a focus on the data, methods and evaluation.</p>
        <p>2.1 Dueben and Bauer (2018)</p>
        <p>In this study, the authors <anchor xml:id="a38"/>trained a neural network to predict 500 hPa geopotential (Z500; see Section 4 for details on commonly</p>
        <p>used fields)<anchor xml:id="a39"/>, and in some experiments 2 meter-temperature, 1 hour ahead. The training data was taken from the ERA5 archive</p>
        <p>for the time period from 2010 to 2017 and regridded to a 6 degree latitude-longitude grid. Two neural network variants were</p>
        <p>3</p>
        <p>Figure 1. Schematic of data-driven weather forecasting. a) Example of direct weather prediction for 5 days lead time. The input to the neural</p>
        <p>network are fields on a latitude-longitude grid. The fields can be several levels of the same variable and/or different variables. The goal is to</p>
        <p>predict the same fields some time ahead. b) Iterative forecasts are created from data-driven models trained on a shorter lead time, for example</p>
        <p>6 hours, which are then iteratively called up to the required forecast lead time.</p>
        <p>used, a fully connected neural network and a spatially localized network, similar to a convolutional neural network (CNN).</p>
        <p>After training they then created iterative forecasts up to 120 h lead time for 10 month validation period. They compared their</p>
        <p>data-driven forecasts to an operational NWP model and the same model run at a spatial resolution comparable to the datadriven method. One interesting detail is that their networks predict the difference from one time step to the next, instead of the</p>
        <p>absolute field. To create these iterative forecasts, they use a third-order Adams-Bashford explicit time-stepping scheme. The</p>
        <p><anchor xml:id="a40"/>CNN predicting only geopotential performed best but was unable to beat the low-resolution physical baseline<anchor xml:id="a41"/>.</p>
        <p>2.2 Scher (2018) and Scher and Messori (2019b)</p>
        <p>These two studies addressed the issue of data-driven weather forecasting in a simplified reality setting. Long runs of simplified</p>
        <p>General Circulation Models (GMCs) were used as “reality”. Neural networks were trained to predict the model fields several</p>
        <p>days ahead. The neural network architecture are CNNs with an encoder-decoder setup. They take as input the instantaneous</p>
        <p>3D model fields at one timestep, and output the same model fields at some time later. In Scher (2018), a separate network was</p>
        <p>trained for each lead-time up to 14 days. Scher and Messori (2019b) trained only on 1-day forecasts, and constructed longer</p>
        <p>forecasts iteratively. <anchor xml:id="a42"/>Interestingly, networks trained to directly predict a certain forecast time, e.g. 5 days, outperformed iterative</p>
        <p>networks<anchor xml:id="a43"/>. <anchor xml:id="a44"/>The forecasts were <anchor xml:id="a45"/>evaluated using the root mean squared error and the anomaly correlation coefficient<anchor xml:id="a46"/> of Z500<anchor xml:id="a47"/> and</p>
        <p>4</p>
        <p>Longitudet = 0t = 5 daysa) Direct predictionb) Iterative predictiont = 0t = 6 hourst = 5 daysLatitudeChannels = Variables xLevels 800 hPa temperature. Scher (2018) used a highly simplified GCM without hydrological cycle, and achieved very high predictive</p>
        <p>skill. Additionally, they were able to create stable &quot;climate&quot; runs (long series of consecutive forecasts) with the network. Scher</p>
        <p>and Messori (2019b) used several more realistic and complex GCMs. The data-driven model achieved relatively good shortterm forecast skill, but was unable to generate stable and realistic “climate” runs. In terms of neural-network architectures they</p>
        <p>showed that architectures tuned on simplified GCMs also work on more complex GCMs, and that the same architecture also</p>
        <p>has some prediction skill on single-level reanalysis data.</p>
        <p>2.3 Weyn et al. (2019)</p>
        <p>In this study, reanalysis-derived Z500 and 700-300 hPa thickness at 6-hourly time steps are predicted with deep CNNs. The data</p>
        <p>are from the Climate Forecast System (CFS) Reanalysis from 1979–2010 with 2.5-degree horizontal resolution and cropped to</p>
        <p>the northern hemisphere. The authors used similar encoder-decoder convolutional networks as those used by Scher (2018) and</p>
        <p>Scher and Messori (2019b) but also experimented with adding a convolution long short-term memory (LSTM; Hochreiter and</p>
        <p>Schmidhuber, 1997) hidden layer. As in Scher and Messori (2019b), forecasts are generated iteratively by feeding the model’s</p>
        <p>outputs back in as inputs. The authors found that using two input time steps, 6 h apart, and predicting two output time steps,</p>
        <p>performed better than using a single step. Their best CNN forecast outperforms a climatology benchmark at up to 120 h lead</p>
        <p>time, and appears to correctly asymptote towards persistence forecasts at longer lead times up to 14 days.</p>
        <p>These three approaches outline promising first steps towards data-driven forecasting. The differences of the proposed methods already highlight the importance of a common benchmark case to compare prediction skill.</p>
        <p>3 Dataset</p>
        <p><anchor xml:id="a48"/>For the proposed benchmark, we use the ERA5 reanalysis dataset (Hersbach et al., 2020) for training and testing.<anchor xml:id="a49"/> <anchor xml:id="a50"/>Reanalysis</p>
        <p>datasets provide the best guess of the atmospheric state at any point in time by combining a forecast model with the available</p>
        <p>observations<anchor xml:id="a51"/>. <anchor xml:id="a52"/>The raw data is <anchor xml:id="a53"/>available hourly for 40 years from 1979 to 2018<anchor xml:id="a54"/> on a 0.25°latitude-longitude grid (721×1440</p>
        <p>grid points) with 37 vertical levels<anchor xml:id="a55"/>.<anchor xml:id="a56"/></p>
        <p>Since this raw dataset is very large (<anchor xml:id="a57"/>a single vertical level for the entire time period amounts to almost 700GB of data<anchor xml:id="a58"/>), we</p>
        <p>regrid the data to lower resolutions. This is also a more realistic use case, since very high resolutions are still hard to handle for</p>
        <p>deep learning models because of GPU memory constraints and I/O speed. In particular, we chose 5.625° (32×64 grid points),</p>
        <p>2.8125° (64×128 grid points) and 1.40525° (128×256 grid points) resolution for our data. The regridding was done with the</p>
        <p>xesmf Python package (Zhuang, 2019) using a bilinear interpolation. Powers of two for the grid are used since this is common</p>
        <p>for many deep learning architectures where image sizes are halved in the algorithm. Further, for 3D fields we selected 13</p>
        <p>vertical levels: 50, 100, 150, 200, 250, 300, 400, 500, 600, 700, 850, 925, 1000 hPa. Note that it is common to use pressure</p>
        <p>in hecto-Pascals as a vertical coordinate instead of physical height. The pressure at sea level is approximately 1000 hPa and</p>
        <p>decreases roughly exponentially with height. 850 hPa is at around 1.5 km height. 500 hPa is at around 5.5 km height. If the</p>
        <p>surface pressure is smaller than a given pressure level, for example at high altitudes, the pressure-level values are interpolated.</p>
        <p>5</p>
        <p>The selected pressure levels contain the seven pressure levels that are commonly used for 3D output by the climate models in</p>
        <p>the Coupled Model Intercomparison Project Phase 6 (CMIP6, Eyring et al., 2016) which could be useful for pretraining. One</p>
        <p>regridded historical climate run is also available from the data repository with a template workflow for downloading further</p>
        <p>CMIP data on the Github repository.</p>
        <p>The processed data (see Table 1) are available at https://mediatum.ub.tum.de/1524895 (Rasp et al., 2020). The data are split</p>
        <p>into yearly NetCDF files for each variable and resolution, packed in a zip file. <anchor xml:id="a59"/>The entire dataset at 5.625° resolution has a size</p>
        <p>of 191GB<anchor xml:id="a60"/>. Individual variables amount to around 25GB three-dimensional and 2GB for two-dimensional fields. File sizes for</p>
        <p>2.8125° and 1.40525° resolutions are a factor 4 and 16 times larger. Data processing was organized using Snakemake (Koster and Rahmann, 2012). For further instructions on data downloading visit the Github page1. The available variables were chosen</p>
        <p>based on meteorological consideration. Geopotential, temperature, humidity and wind are prognostic state variables in most physical NWP and climate models. Geopotential at a certain pressure level p, typically denoted as Φ with units of m2s−2,</p>
        <p>defined as</p>
        <p>z at p (cid:90)</p>
        <p>g dz(cid:48)</p>
        <p>Φ =</p>
        <p>0</p>
        <p>(1)</p>
        <p>where z describes height in meters and g = 9.81 m s−2 is the gravitational acceleration. Horizontal relative vorticity, defined</p>
        <p>as ∂v/∂x − ∂u/∂y, describes the rotation of air at a given point in space. Potential vorticity (Hoskins et al., 1985; Holton,</p>
        <p>2004) is a commonly used quantity in synoptic meteorology which combines the rotation (vorticity) and vertical temperature gradient of the atmosphere. It is defined as P V = ρ−1ζa · ∇θ, where ρ is the density, ζa is the absolute vorticity (relative plus the Earth’s rotation) and θ is the potential temperature. In addition to the three-dimensional fields, we also include several twodimensional fields: 2 meter-temperature is often used as an impact variable because of its relevance for human activities and</p>
        <p>is directly affected by the diurnal solar cycle; 10 meter-wind is also an important impact-related forecast variable, for example</p>
        <p>for wind energy; similarly, total cloud cover is an essential variable for solar energy forecasting. We also included precipitation</p>
        <p>but urge caution since precipitation in reanalysis datasets often shows large deviation from observations (e.g. Betts et al.,</p>
        <p>2019; Xu et al., 2019). Finally, we added the top-of-atmosphere incoming solar radiation as it could be a useful input variable</p>
        <p>to encode the diurnal cycle. Further, there are several potentially important time-invariant fields, which are contained in the</p>
        <p>constants file. The first three variables enclose information about the surface: the land-sea mask is a binary field with ones for land points; the soil type consists of seven different soil categories2; orography is simply the surface height. In addition,</p>
        <p>we included two-dimensional fields with the latitude and longitude values at each point. Particularly the latitude values could</p>
        <p>become important for the network to learn latitude-specific information such as the grid structure or the Coriolis effect (see</p>
        <p>Section 6). The Github code repository includes all scripts for downloading and processing of the data. This enables users to</p>
        <p>download additional variables or regrid the data to a different resolution.</p>
        <p>1https://github.com/pangeo-data/WeatherBench 2Coarse = 1, Medium = 2, Medium fine = 3, Fine = 4, Very fine = 5, Organic = 6, Tropical organic = 7, see https://apps.ecmwf.int/codes/grib/param-db?</p>
        <p>id=43</p>
        <p>6</p>
        <p>Table 1. List of variables contained in the benchmark dataset.</p>
        <p>Short name Description</p>
        <p>z</p>
        <p>t</p>
        <p>q</p>
        <p>r</p>
        <p>u</p>
        <p>v</p>
        <p>vo</p>
        <p>pv</p>
        <p>t2m</p>
        <p>u10</p>
        <p>v10</p>
        <p>tcc</p>
        <p>tp</p>
        <p>tisr</p>
        <p>lsm</p>
        <p>slt</p>
        <p>Proportional to the height of a pressure level</p>
        <p>Temperature</p>
        <p>Mixing ratio of water vapor</p>
        <p>Humidity relative to saturation</p>
        <p>Wind in x/longitude-direction</p>
        <p>Wind in y/latitude direction</p>
        <p>Relative horizontal vorticity</p>
        <p>Potential vorticity</p>
        <p>Temperature at 2 m height above surface</p>
        <p>Wind in x/longitude-direction at 10 m height</p>
        <p>Wind in y/latitude-direction at 10 m height</p>
        <p>Fractional cloud cover</p>
        <p>Hourly precipitation</p>
        <p>Accumulated hourly incident solar radiation</p>
        <p>File containing time-invariant fields</p>
        <p>Land-sea binary mask</p>
        <p>Soil-type categories</p>
        <p>orography</p>
        <p>Height of surface</p>
        <p>lat2d</p>
        <p>lon2d</p>
        <p>2D field with latitude at every grid point</p>
        <p>2D field with longitude at every grid point</p>
        <p>Unit</p>
        <p>[m2s−2]</p>
        <p>[K] [kg kg−1]</p>
        <p>[%] [m s−1] [m s−1] [1 s−1] [K m2 kg−1 s−1]</p>
        <p>[K] [m s−1] [m s−1]</p>
        <p>(0–1)</p>
        <p>[m] [J m−2]</p>
        <p>(0/1)</p>
        <p>see text</p>
        <p>[m]</p>
        <p>[°]</p>
        <p>[°]</p>
        <p>Levels</p>
        <p>13 levels</p>
        <p>13 levels</p>
        <p>13 levels</p>
        <p>13 levels</p>
        <p>13 levels</p>
        <p>13 levels</p>
        <p>13 levels</p>
        <p>13 levels</p>
        <p>Single level</p>
        <p>Single level</p>
        <p>Single level</p>
        <p>Single level</p>
        <p>Single level</p>
        <p>Single level</p>
        <p>Single level</p>
        <p>Single level</p>
        <p>Single level</p>
        <p>Single level</p>
        <p>Single level</p>
        <p>Long name</p>
        <p>geopotential</p>
        <p>temperature</p>
        <p>specific_humidity</p>
        <p>relative_humidity</p>
        <p>u_component_of_wind</p>
        <p>v_component_of_wind</p>
        <p>vorticity</p>
        <p>potential_vorticity</p>
        <p>2m_temperature</p>
        <p>10m_u_component_of_wind</p>
        <p>10m_v_component_of_wind</p>
        <p>total_cloud_cover</p>
        <p>total_precipitation</p>
        <p>toa_incident_solar_radiation</p>
        <p>constants</p>
        <p>land_binary_mask</p>
        <p>soil_type</p>
        <p>orography</p>
        <p>latitude</p>
        <p>longitude</p>
        <p>4 Evaluation</p>
        <p>Evaluation is done for the years 2017 and 2018. To make sure no overlap exists between the training and test dataset, the</p>
        <p>first test date is 1 January 2017 00UTC plus forecast time (i.e. for a three day forecast the first test date would be 4 January</p>
        <p>2017 00UTC) while the last training target is 31 December 2016 23UTC. Further, the evaluation presented here is done on 5.625° resolution3. This means that predictions at higher resolutions have to be downscaled to the evaluation resolution. We</p>
        <p>also evaluated some baselines at higher resolutions and found that the scores were almost identical with differences smaller</p>
        <p>than 1%. Therefore we are reassured that little information is lost by evaluating at a coarser resolution.</p>
        <p>A note on validation and testing: <anchor xml:id="a61"/>In machine learning it is good practice to split the data into three parts: the training, validation and test sets. The training dataset is used to actually fit the model<anchor xml:id="a62"/>. The validation dataset is used during experimentation</p>
        <p>3The evaluation of all baselines in this paper are done in this Jupyter notebook: https://github.com/pangeo-data/WeatherBench/blob/master/notebooks/</p>
        <p>4-evaluation.ipynb</p>
        <p>7</p>
        <p>to check the model performance on data not seen during training. <anchor xml:id="a63"/>However, there is the danger that through continued tuning</p>
        <p>of hyperparameters one unwillingly overfits to the validation dataset. Therefore it is advisable to keep a third, testing, dataset</p>
        <p>for final evaluations of model performance<anchor xml:id="a64"/>. For this benchmark this final evaluation is done for the years 2017 and 2018.</p>
        <p>Therefore, we strongly encourage users of this dataset to pick a period from 1979 to 2016 for validation of their models for hyperparameter tuning. Because meteorological fields are highly correlated in time, it is advisable to choose a longer contiguous</p>
        <p>chunk of data for validation instead of a completely random split. Here we chose the year 2016 for validation.</p>
        <p>We chose 500 hPa geopotential and 850 hPa temperature as primary verification fields. Geopotential at 500 hPa pressure,</p>
        <p>often abbreviated as Z500, is a commonly used variable that encodes the synoptic-scale pressure distribution. It is the standard</p>
        <p>verification variable for most medium-range NWP models. Note that geopotential height, also commonly used, is defined as</p>
        <p>Φ/g with units of meters. We picked 850 hPa temperature as our secondary verification field because temperature is a more</p>
        <p>impact-related variable. 850 hPa is usually above the planetary boundary layer and therefore not affected by diurnal variations</p>
        <p>but provides information about broader temperature trends, including cold spells and heat waves. In addition we also provide</p>
        <p>some baseline scores for total 6-hourly accumulated precipitation (TP; but noting the dubious quality mentioned above) and</p>
        <p>2-meter temperature (T2M). However, they will not be further discussed here.</p>
        <p><anchor xml:id="a65"/>We chose the root mean squared error (RMSE) as our primary metric because it is easy to compute and mirrors the loss used</p>
        <p>for most ML applications<anchor xml:id="a66"/>.<anchor xml:id="a67"/> We define the RMSE as the mean latitude-weighted RMSE over all forecasts:</p>
        <p>RMSE =</p>
        <p>1 Nforecasts</p>
        <p>Nforecasts(cid:88)</p>
        <p>(cid:118) (cid:117) (cid:117) (cid:116)</p>
        <p>i</p>
        <p>1 NlatNlon</p>
        <p>Nlat(cid:88)</p>
        <p>Nlon(cid:88)</p>
        <p>j</p>
        <p>k</p>
        <p>L(j)(fi,j,k − ti,j,k)2</p>
        <p>(2)</p>
        <p>where f is the model forecast and t is the ERA5 truth. L(j) is the latitude weighting factor for the latitude at the jth latitude</p>
        <p>index:</p>
        <p>L(j) =</p>
        <p>cos(lat(j)) (cid:80)Nlat j</p>
        <p>cos(lat(j))</p>
        <p>1 Nlat</p>
        <p>(3)</p>
        <p>In addition, we also evaluate the baselines using the latitude weighted anomaly correlation coefficient (ACC; see Section</p>
        <p>7.6.4 of Wilks, 2006) and the mean absolute error (MAE). The tables and figures can be found in the Appendix A. For smooth</p>
        <p>fields like Z500 and T850 the qualitative differences between the metrics are small. For intermittent fields like precipitation the</p>
        <p>choice of metric matters a lot more.</p>
        <p>5 Baselines</p>
        <p>To evaluate the skill of a forecasting model it is important to have baselines to compare to. In this section, we compute scores</p>
        <p>for several baselines. The results are summarized in Fig. A3 and Table 2.</p>
        <p>5.1 Persistence and Climatology</p>
        <p><anchor xml:id="a68"/>The two simplest possible forecasts are a) a persistence forecast in which the fields at initialization time are used as forecasts</p>
        <p>(&quot;tomorrow’s weather is today’s weather&quot;), and b) a climatological forecast<anchor xml:id="a69"/>. For the climatological forecast, two different</p>
        <p>8</p>
        <p>Figure 2. RMSE of a) 500 hPa geopotential and b) 850 hPa temperature for different baselines at 5.625° resolution. <anchor xml:id="a70"/>Solid lines for linear</p>
        <p>regression and CNN indicate iterative forecasts, while dots represent direct forecasts for 3 and 5 days lead time.<anchor xml:id="a71"/></p>
        <p>Table 2. Baseline RMSE for 3 and 5 days forecast time at 5.625° resolution. Best machine learning baseline and physical model are highlighted. TP is 6 hourly accumulated precipitation.</p>
        <p>Baseline</p>
        <p>Persistence</p>
        <p>Climatology</p>
        <p>Weekly climatology</p>
        <p>RMSE (3 days / 5 days)</p>
        <p>Z500 [m2 s−2]</p>
        <p>T850 [K]</p>
        <p>T2M [K]</p>
        <p>TP [mm]</p>
        <p>936 / 1033</p>
        <p>4.23 / 4.56</p>
        <p>3.00 / 3.27</p>
        <p>3.23 / 3.24</p>
        <p>1075</p>
        <p>816</p>
        <p>5.51</p>
        <p>3.50</p>
        <p>6.07</p>
        <p>3.19</p>
        <p>2.36</p>
        <p>2.32</p>
        <p>Linear regression (direct)</p>
        <p>693 / 783</p>
        <p>3.19 / 3.44</p>
        <p>2.39 / 2.60</p>
        <p>2.37 / 2.37</p>
        <p>Linear regression (iterative)</p>
        <p>718 / 810</p>
        <p>626 / 757</p>
        <p>3.17 / 3.48</p>
        <p>2.87 / 3.37</p>
        <p>CNN (direct)</p>
        <p>CNN (iterative)</p>
        <p>IFS T42</p>
        <p>IFS T63</p>
        <p>Operational IFS</p>
        <p>1114 / 1559</p>
        <p>4.48 / 9.69</p>
        <p>489 / 743</p>
        <p>268 / 463</p>
        <p>154 / 334</p>
        <p>3.09 / 3.83</p>
        <p>3.21 / 3.69</p>
        <p>1.85 / 2.52</p>
        <p>2.04 / 2.44</p>
        <p>1.36 / 2.03</p>
        <p>1.35 / 1.77</p>
        <p>2.36 / 2.59</p>
        <p>climatologies were computed from the training dataset (1979–2016): first, a single mean over all times in the training dataset</p>
        <p>and, second, a mean computed for each of the 52 calendar weeks. The weekly climatology is significantly better, approximately</p>
        <p>matching the persistence forecast between 1 and 2 days, since it takes into account the seasonal cycle. This means that to be</p>
        <p>useful, a forecast system needs to beat the weekly climatology and the persistence forecast.</p>
        <p>9</p>
        <p>012345Forecast time [days]020040060080010001200Z500 RMSE [m2 s2]a) Z500PersistenceClimatologyWeekly clim.OperationalIFS T42IFS T63LR (iterative)CNN (iterative)LR (direct)CNN (direct)012345Forecast time [days]0123456T850 RMSE [K]b) T850 5.2 Operational NWP model</p>
        <p>The gold standard of medium-range NWP is the operational IFS (Integrated Forecast System) model of the European Center for Medium-range Weather Forecasting (ECMWF)4. We downloaded the forecasts for 2017 and 2018 from the THORPEX Interactive Grand Global Ensemble (TIGGE; Bougeault et al., 2010) archive5, which contains the operational forecasts, initialized at 00 and 12 UTC regridded to a 0.5° by 0.5° grid, which we further regridded to 5.625°. Note that the forecast error starts</p>
        <p>above zero because the operational IFS is initialized from a different analysis. Operational forecasting is computationally very</p>
        <p>expensive. The current IFS deterministic forecast is computed on a cluster with 11,664 cores. One 10 day forecast at 10 km</p>
        <p>resolution takes around 1 hour of real time to compute.</p>
        <p>5.3 Physical NWP model run at coarser resolution</p>
        <p>To provide physical baselines more in line with the computational resources of a data-driven model, we ran the IFS model</p>
        <p>at two coarser horizontal resolutions, T42 (approximately 2.8° or 310 km resolution at the equator (NCAR)) with 62 vertical</p>
        <p>levels and T63 (approximately 1.9° or 210 km) with 137 vertical levels. The T42 run was initialized from ERA5 whereas</p>
        <p>the T63 run was initialized from the operational analysis. The gap in skill at t = 0 is caused by the conversion to spherical</p>
        <p>coordinates at coarse resolutions. For Z500 the skill for these two runs lies in-between the operational IFS and the machine</p>
        <p>learning baselines. For T850, the T42 run is significantly worse. The likely reason for this is that temperature close to the</p>
        <p>ground is much more affected by the resolution and representation of topography within the model. Further, the model was</p>
        <p>not specifically tuned for these resolutions. Computationally, a single forecast takes 270 seconds for the T42 model and 503</p>
        <p>seconds for the T64 model on a single XC40 node with 36 cores. Since the computational costs and resolutions of these runs</p>
        <p>are much closer to those of a data-driven method, beating those baselines should be a realistic target. note, however, that the</p>
        <p>model was not tuned to run at such coarse resolutions.</p>
        <p>5.4 Linear regression</p>
        <p><anchor xml:id="a72"/>As a first purely data-driven baseline we fit a simple linear regression model. For the direct predictions a separate model was</p>
        <p>trained for each of the four variables. For this purpose the 2D fields were flattened from 32×64 → 2048. This was done for 3 d</p>
        <p>and 5 d forecast time. In addition an iterative model for Z500 and T850 was trained. Here we use a single linear regression to</p>
        <p>predict 6 hours ahead where the two fields are concatenated (2×32×64 → 4096). The advantage of iterative forecasts is that a</p>
        <p>single model is able to make predictions for any forecast time rather than having to train several models. For iterative forecasts</p>
        <p>the model takes its previous output as input for the next step. To create a 5 day iterative forecast the model trained to predict</p>
        <p>6 hour forecasts is called 20 times<anchor xml:id="a73"/>. For this model, the iterative forecast performs just as well as the direct forecast due to its</p>
        <p>linear nature. At 5 days, the linear regression forecast is about as good as the weekly climatology.</p>
        <p>4https://www.ecmwf.int/en/forecasts/documentation-and-support 5The TIGGE data for total precipitation and 2m temperature was damaged for 2017. For this reason the TIGGE evaluation for these variables is only done</p>
        <p>using the 2018 data.</p>
        <p>10</p>
        <p>5.5 Simple convolutional neural network</p>
        <p><anchor xml:id="a74"/>As our deep learning baseline we chose a simple fully-convolutional neural network. CNNs are the natural choice for spatial</p>
        <p>data since they exploit translational invariances in images/fields. Here we train a CNN with 5 layers. Each hidden layer has</p>
        <p>64 channels with a convolutional kernel of size 5 and ELU activations (Clevert et al., 2015). The input and output layers have</p>
        <p>two channels, representing Z500 and T850. The model was trained using the Adam optimizer (Kingma and Ba, 2014) and a</p>
        <p>mean squared error loss function. The total number of trainable parameters is 313,858. We implemented periodic convolutions</p>
        <p>in the longitude direction but not the latitude direction<anchor xml:id="a75"/>. The implementation can be found in the Github repository. The direct</p>
        <p>CNN forecasts beat the linear regression forecasts for 3 and 5 days forecast time. However, at 5 days these forecasts are only</p>
        <p>marginally better than the weekly climatology (see Table 2). This baseline, however, is to be seen simply as a starting point</p>
        <p>for more sophisticated data driven methods. The iterative CNN forecast, which equivalently to the linear regression iterative</p>
        <p>forecast was created by chaining together 6 hourly predictions, performs well up to around 1.5 days but then the network’s</p>
        <p>errors grow quickly and diverge. <anchor xml:id="a76"/>This confirms the findings of Scher and Messori (2019a) whose experiments showed that</p>
        <p>training with longer lead time yields better results than chaining together short-term forecasts.<anchor xml:id="a77"/> <anchor xml:id="a78"/>However, the poor skill of the</p>
        <p>iterative forecast could easily be a result of using an overly simplistic network architecture.<anchor xml:id="a79"/> The iterative forecasts of Weyn</p>
        <p>et al. (2019), who employ a more complex network structure, show stable long term performance up to two weeks with realistic</p>
        <p>statistics.</p>
        <p>5.6 Example forecasts</p>
        <p>To further illustrate the prediction task, Fig. 3 shows example geopotential and temperature fields. The ERA5 temporal differences show several interesting features. First, the geopotential fields and differences are much smoother compared to the</p>
        <p>temperature fields. The differences in both fields are also much smaller in the tropics compared to the extratropics where propagating fronts can cause rapid temperature changes. An interesting feature is detectable in the 6h Z500 difference field in the</p>
        <p>tropics. These alternating patterns are signatures of atmospheric tides.</p>
        <p>The CNN forecasts for 6h lead time are not able to capture these wave-like patterns which hints at a failure to capture the</p>
        <p>basic physics of the atmosphere. <anchor xml:id="a80"/>For 5 days forecast time the CNN model predicts unrealistically smooth fields. This is likely</p>
        <p>a result of two factors: first, the two input fields used in this baseline CNN contain insufficient information to create a skillful</p>
        <p>5 day forecast; and second, at 5 days the atmosphere already shows some chaotic behavior which causes a model trained with</p>
        <p>a simple RMSE loss to predict smooth fields<anchor xml:id="a81"/> (see Section 6). The IFS operational forecast has much smaller errors than the</p>
        <p>CNN forecast. It is able to capture the propagation of tropical waves. Its main errors appear at 5 days in the mid-latitudes where</p>
        <p>extratropical cycles are in slightly wrong positions.</p>
        <p>11</p>
        <p>Figure 3. Example fields for 2017-01-01 00UTC initialization time. The top two rows show the ERA5 &quot;truth&quot; fields for geopotential (Z500)</p>
        <p>and temperature (T850) at initialization time (t=0h) and for 6h and 5d forecast time. In addition, the difference between the forecast times</p>
        <p>and the initialization time is shown. The third and fourth rows show the forecasts from the CNN model. Rows five and six show the IFS</p>
        <p>operational model. For the CNN forecasts the first column is identical to the ERA5 truth. We selected the 6h iterative CNN model for the 6h</p>
        <p>forecast but the 5d direct CNN model for the 5 day forecast. For the IFS the initial states (t=0h) differ slightly albeit not visibly. In addition</p>
        <p>to the forecast fields the error relative to the ERA5 &quot;truth&quot; is shown in the third and fifth columns. Please note that the colorbars for the</p>
        <p>difference fields change.</p>
        <p>12</p>
        <p>ERA5 “Truth”CNN forecastsIFS forecasts 6 Discussion</p>
        <p>6.1 Weather-specific challenges</p>
        <p><anchor xml:id="a82"/>From a ML perspective, state-to-state weather prediction is similar to image-to-image translation. For this sort of problem many</p>
        <p>deep learning techniques have been developed in recent years (Kaji and Kida, 2019). However, forecasting weather differs in</p>
        <p>some important ways from typical image-to-image applications and raises several open questions.</p>
        <p>First, the atmosphere is three-dimensional. So far, this aspect has not been taken into account. In the networks of Scher and</p>
        <p>Messori (2019a), for example, the different levels have been treated as separate channels of the CNN. However, simply using a</p>
        <p>three-dimensional CNN might not work either because atmospheric dynamics and grid spacings change in the vertical, thereby</p>
        <p>violating the assumption of translation invariance which underlies the effectiveness of CNNs<anchor xml:id="a83"/>. This directly leads to the next</p>
        <p>challenge: On a regular latitude-longitude grid, the dynamics also change with latitude because towards the poles the grid cells</p>
        <p>become increasingly stretched. This is in addition to the Coriolis effect, the deflection of wind caused by the rotation of Earth,</p>
        <p>which also depends on latitude. A possible solution in the horizontal could be to use spherical convolutions (Cohen et al., 2018;</p>
        <p>Perraudin et al., 2019; Jiang et al., 2019) or to feed in latitude information to the network.</p>
        <p><anchor xml:id="a84"/>Another potential issue is the limited amount of training data available.<anchor xml:id="a85"/> 40 years of hourly data amounts to around 350,000</p>
        <p>samples.<anchor xml:id="a86"/> <anchor xml:id="a87"/>However, the samples are correlated in time. <anchor xml:id="a88"/>If one assumes that a new weather situation occurs every day, then</p>
        <p>the number of samples is reduced to around 15,000<anchor xml:id="a89"/>.<anchor xml:id="a90"/> Without empirical evidence it is hard to estimate whether this number</p>
        <p>is sufficient to train complex networks<anchor xml:id="a91"/> without overfitting. <anchor xml:id="a92"/>Should overfitting be a problem, one could try transfer learning.</p>
        <p>In transfer learning, the network is pretrained on a similar task or dataset, for example, climate model simulations, and then</p>
        <p>finetuned on the actual data. This is common practice in computer vision and has been successfully applied to seasonal ENSO</p>
        <p>forecasting<anchor xml:id="a93"/> (Ham et al., 2019). <anchor xml:id="a94"/>Another common method to prevent overfitting is data augmentation, which in traditional</p>
        <p>computer vision is done by e.g. randomly rotating or flipping the image. However, many of the traditional data augmentation</p>
        <p>techniques are questionable for physical fields. Random rotations, for example, will likely not work for this dataset since the x</p>
        <p>and y directions are physically distinct. Thus, finding good data augmentation techniques for physical fields is an outstanding</p>
        <p>problem<anchor xml:id="a95"/>. Using ensemble analyses and forecasts could provide more diversity in the training dataset.</p>
        <p><anchor xml:id="a96"/>Finally, there are technical challenges. Data for a single variable with ten levels at 5.625° resolution take up around 30 GB of</p>
        <p>data. For a network with several variables or even at higher resolution, the data might not fit into CPU RAM any more and data loading could become a bottleneck. For image files, efficient data loaders have been created6. For netCDF files, however, so</p>
        <p>far no efficient solution exists to our knowledge. Further, <anchor xml:id="a97"/>one can assume that to create a competitive data-driven NWP model,</p>
        <p>high resolutions have to be used, for which GPU RAM quickly becomes a limitation.<anchor xml:id="a98"/> This suggests that multi-GPU training</p>
        <p>might be necessary to scale up this approach<anchor xml:id="a99"/> (potentially similar to the technical achievement of Kurth et al. (2018)).</p>
        <p>6See e.g. https://keras.io/preprocessing/image/ or https://pytorch.org/tutorials/beginner/data_loading_tutorial.html. One promising but so far unexplored</p>
        <p>option is to use Tensorflow’s TFRecords (https://www.tensorflow.org/tutorials/load_data/tfrecord)</p>
        <p>13</p>
        <p>6.2 Probabilistic forecasts and extremes</p>
        <p><anchor xml:id="a100"/>One important aspect that is not currently addressed by this benchmark is probabilistic forecasting.<anchor xml:id="a101"/> Because of the chaotic</p>
        <p>evolution of the atmosphere, it is very important to also have an estimate of the uncertainty of a forecast. In physical NWP</p>
        <p>this is done by running several forecasts, called an ensemble, from slightly different initial conditions and potentially with</p>
        <p>different or stochastic model physics (Palmer, 2019). From this Monte Carlo forecast one can then estimate a probability</p>
        <p>distribution. A different approach, which is often taken in statistical post-processing of NWP forecasts, is to directly estimate a</p>
        <p>parametric distribution<anchor xml:id="a102"/> (e.g. Gneiting et al., 2005; Rasp and Lerch, 2018). <anchor xml:id="a103"/>For a probabilistic forecast to be reliable the forecast</p>
        <p>uncertainty has to be an accurate indicator of the error. <anchor xml:id="a104"/>A good first order approximation for this is the spread (ensemble</p>
        <p>standard deviation) to error (RMSE) ratio which should be one (Leutbecher and Palmer, 2008).<anchor xml:id="a105"/> A more stringent test is to</p>
        <p>use a proper probabilistic scoring rule, for example the continuous ranked probability score (CRPS)<anchor xml:id="a106"/> (Gneiting and Raftery,</p>
        <p>2007; Gneiting and Katzfuss, 2014). For deterministic forecast the CRPS reduces to the mean absolute error. Extending this</p>
        <p>benchmark to probabilistic forecasting simply requires computing a probabilistic score. How to produce probabilistic datadriven forecasts is a very interesting research question in its own right. We encourage users of this benchmark to explore this</p>
        <p>dimension.</p>
        <p>A related issue is the question of extreme weather situations, for example heat waves. These events are, by definition, rare,</p>
        <p>which means that they will contribute little to regular verification metrics like the RMSE. However, for society these events</p>
        <p>are highly important. For this reason, it would make sense to evaluate extreme situations separately. <anchor xml:id="a107"/>But defining extremes</p>
        <p>is ambiguous which is why there is no standard metric for evaluating extremes. The goal of this benchmark is to provide a</p>
        <p>simple, clear problem. <anchor xml:id="a108"/>Therefore, we decided to omit extremes for now but users are encouraged to chose their own verification</p>
        <p>of extremes.<anchor xml:id="a109"/></p>
        <p>6.3 Climate simulations</p>
        <p><anchor xml:id="a110"/>Another aspect that is untouched by the benchmark challenge proposed here is climate prediction.<anchor xml:id="a111"/> <anchor xml:id="a112"/>Even though weather and</p>
        <p>climate deal with the same underlying physical system, they pose different forecasting challenges. In weather forecasting the</p>
        <p>goal is to predict the state of the atmosphere at a specific time into the future. This is only possible up to the prediction</p>
        <p>horizon of the atmosphere, which is thought to be at roughly two weeks. Climate models, on the other hand, are evaluated</p>
        <p>by comparing long-term statistics to observations<anchor xml:id="a113"/>, for example the mean surface temperature (Stocker et al., 2013). Scher and</p>
        <p>Messori (2019a) created iterative climate time scale runs with their data-driven models and compared first and second-order</p>
        <p>statistics. They found that the model sometimes produced a stable climate but with significant biases and a poor seasonal</p>
        <p>cycle. This indicates that, so far, iterative data-driven models have been unable to produce physically reasonable long-term</p>
        <p>predictions. This remains a key challenge for future research. While not specifically included in this benchmark, a good test for</p>
        <p>climate simulations is to look at long term mean statistics and the seasonal cycle as done in Figs. 6 and 7 of Scher and Messori</p>
        <p>(2019a).</p>
        <p>14</p>
        <p>Climate change simulations represent another step up in complexity. To start with, external greenhouse gas forcing would</p>
        <p>have to be included. Further, <anchor xml:id="a114"/>future climates will produce atmospheric states that lie outside of the historical manifold of states.</p>
        <p>Plain neural networks are very bad at extrapolating to climates beyond what they have seen in the training dataset (Rasp et al.,</p>
        <p>2018). For this reason, climate change simulations with current data-driven methods are likely not a good idea<anchor xml:id="a115"/>. However,</p>
        <p>research into physical machine learning is ongoing and might offer new opportunities in the near future (e.g. Bar-Sinai et al.,</p>
        <p>2019; Beucler et al., 2019).</p>
        <p>6.4 Promising research directions</p>
        <p>There is a wide variety of promising research directions for data-driven weather forecasting. The most obvious direction is</p>
        <p>to increase the amount of data used for training and the complexity of the network architecture. This dataset provides a, so</p>
        <p>far, unexploited volume and diversity of data for training. It is up to future research to find out exactly which combination</p>
        <p>of variables will turn out to be useful. Further, this dataset offers a four times higher horizontal resolution than all previous</p>
        <p>studies. The hope is that this data will enable researcher to train more complex models than have previously been used.</p>
        <p>With regards to model architecture, there is a huge variety of network architectures that can be explored. U-Nets (Ronneberger et al., 2015) have been used extensively for image segmentation tasks that require computations across several spatial</p>
        <p>scales. Resnets (He et al., 2015) are currently the state of the art for image classification and their residual nature could be a</p>
        <p>good fit for state-to-state forecasting tasks. <anchor xml:id="a116"/>For synthesis tasks, generative adverserial networks (GANs) (Goodfellow et al.,</p>
        <p>2014) were shown to be particularly powerful for creating realistic natural images and fluid flows (Xie et al., 2018). This might</p>
        <p>be attractive since minimizing a mean loss, such as the MSE, for random or stochastic data leads to unrealistically smooth</p>
        <p>predictions as seen in Fig. 3. Conditional GANs (Mirza and Osindero, 2014; Isola et al., 2016) could potentially alleviate this</p>
        <p>issue but it is still unclear to what extent GAN predictions are able to recover the multi-variate distribution of the training</p>
        <p>samples<anchor xml:id="a117"/>.</p>
        <p>7 Code and data availability</p>
        <p>The dataset is available at https://mediatum.ub.tum.de/1524895 (Rasp et al., 2020). Code, instructions for dowloading the data</p>
        <p>and evaluating forecasts can be found at https://github.com/pangeo-data/WeatherBench.</p>
        <p>8 Conclusions</p>
        <p>In this paper a benchmark dataset for data-driven weather forecasting is presented. It focuses on global medium-range (roughly</p>
        <p>2 days to 2 weeks) prediction. With the rise of deep learning in physics, weather prediction is a challenging and interesting</p>
        <p>target because of the large overlap with traditional deep learning tasks (Reichstein et al., 2019). While first attempts have</p>
        <p>been made in this direction, as discussed in Section 2, the field currently lacks a common dataset which enables the inter-</p>
        <p>15</p>
        <p>comparison of different methods. We hope that this benchmark can provide a foundation for accelerated research in this area.</p>
        <p><anchor xml:id="a118"/>Loosely following Ebert-Uphoff et al. (2017), the key features of this benchmark are:<anchor xml:id="a119"/></p>
        <p>– Scientific impact: Numerical weather forecasting impacts many aspects of society. Currently, NWP model run on massive super-computers at very high computational cost. Building a capable data-driven model would be beneficial in many</p>
        <p>ways (see Section 1). In addition, there is the open, and highly debated, question whether fully data-driven methods are</p>
        <p>able to learn a good representation of atmospheric physics.</p>
        <p>– Challenge for data science: While global weather prediction is conceptually similar an image-to-image task, and therefore allows for the application of many state-of-the-art deep learning techniques, there are some unique challenges to this</p>
        <p>problem: the three-dimensional, anisotropic nature of the atmosphere; non-uniform-grids; potentially limited amounts of</p>
        <p>training data and the technical challenge of handling large data volumes.</p>
        <p>– <anchor xml:id="a120"/>Clear metric for success: We defined a single metric (RMSE) for two fields (500 hPa geopotential and 850 hPa temperature). These scores provide a simple measure of success<anchor xml:id="a121"/> for data-driven, medium-range forecast model.</p>
        <p>– Quick start: The code repository contains a quick-start Jupyter notebook for reading the data, training a neural network</p>
        <p>and evaluating the predictions against the target data. In addition, the repository contains many functions which are likely</p>
        <p>to be used frequently, for example an implementation of periodic convolutions in Keras.</p>
        <p>– Reproducibility and citability: All baselines and results form this paper are fully reproducible from the code repository.</p>
        <p>Further, the baseline predictions are all saved in the data repository. The data has been assigned a permanent DOI.</p>
        <p>– Communication platform: We will use the Github code repository as an evolving hub for this project. We encourage</p>
        <p>users of this dataset to start by forking the repository and eventually merge code that might be useful for others back into</p>
        <p>the main branch. The main platform for communication, e.g. asking questions, about this project will be Github issues.</p>
        <p>We hope that this benchmark will foster collaboration between atmospheric and data scientists in the ways we imagined and</p>
        <p>beyond.</p>
        <p>16</p>
        <p>(A1)</p>
        <p>(cid:80) tj,k.</p>
        <p>Appendix A: Additional metrics</p>
        <p>The anomaly correlation coefficient (ACC) is defined as</p>
        <p>ACC =</p>
        <p>(cid:80)</p>
        <p>i,j,kt(cid:48) i,j,k L(j)f (cid:48) (cid:80)</p>
        <p>i,j,k L(j)f (cid:48)2</p>
        <p>i,j,k</p>
        <p>i,j,k i,j,k L(j)t(cid:48)2</p>
        <p>i,j,k</p>
        <p>(cid:113)(cid:80)</p>
        <p>where the prime (cid:48) denotes the difference to the climatology. Here the climatology is defined as climatologyj,k = 1 The mean absolute error is defined just like the MSE (Eq. 2) but with the absolute instead of the squared difference.</p>
        <p>Ntime</p>
        <p>Figure A1. RMSE of a) 2-meter temperature and b) 6-hourly accumulated precipitation for different baselines at 5.625° resolution.</p>
        <p>17</p>
        <p>012345Forecast time [days]0123456T2M RMSE [K]a) T2MPersistenceClimatologyWeekly clim.OperationalIFS T42IFS T63LR (direct)012345Forecast time [days]0.00.51.01.52.02.53.03.5TP RMSE [mm]b) TP Figure A2. ACC of a) 500 hPa geopotential, b) 850 hPa temperature, c) 2-meter temperature and d) 6-hourly accumulated precipitation for</p>
        <p>different baselines at 5.625° resolution.</p>
        <p>18</p>
        <p>012345Forecast time [days]0.50.60.70.80.91.0Z500 ACCa) Z500PersistenceClimatologyWeekly clim.OperationalIFS T42IFS T63LR (iterative)CNN (iterative)LR (direct)CNN (direct)012345Forecast time [days]0.600.650.700.750.800.850.900.951.00T850 ACCb) T850012345Forecast time [days]0.40.50.60.70.80.91.0T2M ACCc) T2M012345Forecast time [days]0.00.20.40.60.81.0TP ACCd) TP Figure A3. MAE of a) 500 hPa geopotential, b) 850 hPa temperature, c) 2-meter temperature and d) 6-hourly accumulated precipitation for</p>
        <p>different baselines at 5.625° resolution.</p>
        <p>19</p>
        <p>012345Forecast time [days]0100200300400500600700Z500 MAE [m2 s2]a) Z500PersistenceClimatologyWeekly clim.OperationalIFS T42IFS T63LR (iterative)CNN (iterative)LR (direct)CNN (direct)012345Forecast time [days]0.00.51.01.52.02.53.03.54.0T850 MAE [K]b) T850012345Forecast time [days]0.00.51.01.52.02.53.03.5T2M MAE [K]a) T2M012345Forecast time [days]0.00.20.40.60.81.0TP MAE [mm]b) TP Table A1. Baseline ACC for 3 and 5 days forecast time at 5.625° resolution. Best machine learning baseline and physical model are highlighted. TP is 6 hourly accumulated precipitation.</p>
        <p>Baseline</p>
        <p>Persistence</p>
        <p>Climatology</p>
        <p>Weekly climatology</p>
        <p>ACC (3 days / 5 days)</p>
        <p>Z500</p>
        <p>T850</p>
        <p>T2M</p>
        <p>TP</p>
        <p>0.62 / 0.53</p>
        <p>0.69 / 0.65</p>
        <p>0.88 / 0.85</p>
        <p>0.06/0.06</p>
        <p>0</p>
        <p>0.65</p>
        <p>0</p>
        <p>0.77</p>
        <p>0</p>
        <p>0.85</p>
        <p>0</p>
        <p>0.16</p>
        <p>Linear regression (direct)</p>
        <p>0.76 / 0.68</p>
        <p>0.81 / 0.78</p>
        <p>0.92 / 0.90</p>
        <p>0.15 / 0.13</p>
        <p>Linear regression (iterative)</p>
        <p>0.76 / 0.67</p>
        <p>0.82 / 0.78</p>
        <p>CNN (direct)</p>
        <p>CNN (iterative)</p>
        <p>IFS T42</p>
        <p>IFS T63</p>
        <p>0.81 / 0.71</p>
        <p>0.85 / 0.79</p>
        <p>0.61 / 0.41</p>
        <p>0.72 / 0.31</p>
        <p>0.90 / 0.78</p>
        <p>0.86 / 0.78</p>
        <p>0.87 / 0.83</p>
        <p>0.97 / 0.91</p>
        <p>0.94 / 0.90</p>
        <p>0.94 / 0.92</p>
        <p>Operational IFS</p>
        <p>0.99 / 0.95</p>
        <p>0.97 / 0.93</p>
        <p>0.98 / 0.96</p>
        <p>0.43 / 0.30</p>
        <p>Table A2. Baseline MAE for 3 and 5 days forecast time at 5.625° resolution. Best machine learning baseline and physical model are</p>
        <p>highlighted. TP is 6 hourly accumulated precipitation.</p>
        <p>Baseline</p>
        <p>Persistence</p>
        <p>Climatology</p>
        <p>Weekly climatology</p>
        <p>MAE (3 days / 5 days)</p>
        <p>Z500 [m2 s−2]</p>
        <p>T850 [K]</p>
        <p>T2M [K]</p>
        <p>TP [mm]</p>
        <p>572 / 634</p>
        <p>2.91 / 3.12</p>
        <p>1.81 / 1.95</p>
        <p>1.07 / 1.08</p>
        <p>708</p>
        <p>525</p>
        <p>3.84</p>
        <p>2.48</p>
        <p>3.77</p>
        <p>2.00</p>
        <p>0.92</p>
        <p>0.88</p>
        <p>Linear regression (direct)</p>
        <p>431 / 489</p>
        <p>2.23 / 2.41</p>
        <p>1.48 / 1.60</p>
        <p>0.96 / 0.97</p>
        <p>Linear regression (iterative)</p>
        <p>447 / 508</p>
        <p>403 / 476</p>
        <p>2.20 / 2.42</p>
        <p>2.02 / 2.38</p>
        <p>CNN (direct)</p>
        <p>CNN (iterative)</p>
        <p>IFS T42</p>
        <p>IFS T63</p>
        <p>Operational IFS</p>
        <p>892 / 1263</p>
        <p>3.49 / 7.49</p>
        <p>295 / 449</p>
        <p>188 / 307</p>
        <p>97 / 198</p>
        <p>1.99 / 2.53</p>
        <p>1.83 / 2.12</p>
        <p>1.30 / 1.73</p>
        <p>1.28 / 1.53</p>
        <p>0.93 / 1.35</p>
        <p>0.84 / 1.08</p>
        <p>0.69 / 0.81</p>
        <p>Author contributions. SR, PD, SS and JW conceived the idea. SR prepared the data and baselines and led the writing. All authors contributed</p>
        <p>to the manuscript.</p>
        <p>20</p>
        <p>Competing interests. The authors declare no competing interests.</p>
        <p>Acknowledgements. Stephan Rasp acknowledges funding from the German Research Foundation (DFG). We thank the Copernicus Climate</p>
        <p>Change Service (C3S) for allowing us to redistribute the data. Peter D. Dueben gratefully acknowledges funding from the Royal Society for</p>
        <p>his University Research Fellowship and the ESIWACE2 project. The ESIWACE2 project have received funding from the European Union’s</p>
        <p>Horizon 2020 research and innovation programme under grant agreement No 823988.</p>
        <p>21<anchor xml:id="a122"/></p>
    </body>
  </text>
</TEI>
