Papers › DeepAR: Probabilistic Forecasting with Autoregressive Recurrent Networks

DeepAR: Probabilistic Forecasting with Autoregressive Recurrent Networks

13 Apr 2017arXiv:1704.04110archive 2025-07-28

David Salinas, Valentin Flunkert, Jan Gasthaus

Probabilistic forecasting, i.e. estimating the probability distribution of a time series' future given its past, is a key enabler for optimizing business processes. In retail businesses, for example, forecasting demand is crucial for having the right inventory available at the right time at the right place. In this paper we propose DeepAR, a methodology for producing accurate probabilistic forecasts, based on training an auto regressive recurrent network model on a large number of related time series. We demonstrate how by applying deep learning techniques to forecasting, one can overcome many of the challenges faced by widely-used classical approaches to the problem. We show through extensive empirical evaluation on several real-world forecasting data sets accuracy improvements of around 15% compared to state-of-the-art methods.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 3 code samples harvested from 1 repository linked to this paper: 3 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code.

By repository: community (archive-listed): 3 samples from 1 repository, 3 ran (0 with no instrument failure; 3 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 4 of its repositories that Syntology harvested for other papers:

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

19 repositories listed; official and paper-mentioned ones first.

Nixtla/neuralforecast mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to N-BEATS: Neural basis expansion analysis for interpretable time series forecasting (arXiv:1905.10437; that paper's own run record: 34 ran (of which 0 constructed an object rather than computing a result; 29 with no instrument failure: 5 honoured, 0 violated, 24 with no contract checked; 5 where Syntology's instrument failed) · 5 unverified); nothing checks that they implement this paper's method. report
Timbasa/Sample_GluonTS mentioned on GitHubSyntology: not harvested report
Yonder-OSS/D3M-Primitives mentioned on GitHubtfSyntology: not harvested report
alphaj-jaeminyx/DeepAR-keras mentioned on GitHubtfSyntology: not harvested report
bingblackbean/water_supply_network_pressure_pred_deepar mentioned on GitHubSyntology: not harvested report
dhopp1/nowcasting_benchmark mentioned on GitHubSyntology: not harvested report
eeci/annex_37 mentioned on GitHubpytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to N-HiTS: Neural Hierarchical Interpolation for Time Series Forecasting (arXiv:2201.12886; that paper's own run record: 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
husnejahan/DeepAR-pytorch mentioned on GitHubpytorchSyntology: not harvested report
kshmawj111/solar_energy_forecast mentioned on GitHubmxnetSyntology: not harvested report
ledererlab/deepcar mentioned on GitHubSyntology: not harvested report
nuankw/Summer-Research-2018-Part-One mentioned on GitHubpytorchSyntology: not harvested report
potosnakw/neuralforecast mentioned on GitHubpytorchApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Deep Learning for Time Series Forecasting: Tutorial and Literature Survey (arXiv:2004.10240; that paper's own run record: 7 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
rekahalmai/ImpliedVolatilityPrediction mentioned on GitHubmxnetSyntology: not harvested report
skp2/Electricity-Load mentioned on GitHubSyntology: not harvested report
ucl-exoplanets/deepARTransit mentioned on GitHubtfSyntology: not harvested report
xinzezhang/timeseriesforecasting-torch mentioned on GitHubpytorchSyntology: 3 samples, 3 ran (3 instrument-failed) · 0 unverified report
zhykoties/DeepAR mentioned on GitHubpytorchSyntology: not harvested report
etna-team/etna pytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Time-Series Representation Learning via Temporal and Contextual Contrasting (arXiv:2106.14112; that paper's own run record: 2 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
jdb78/pytorch-forecasting pytorchMITSyntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

3 samples harvested: 3 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · our draft was wrong
1ran; the contract check could not run

Licence: 3 of the 3 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from xinzezhang/timeseriesforecasting-torch. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

xinzezhang/timeseriesforecasting-torch community (archive-listed) 3 samples, 3 ran (3 instrument-failed) · 0 unverified
get_metrics in 46 papers models/training/deepAR.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 8252d4bcce662261 · report fixture: signature sample_mu:Tensor/2/float, labels:Tensor/2/float, predict_start:int/0/int, samples:Tensor/3/float, relative:bool/0/bool · returned dict · level recorded 2026-09-22
init_metrics models/training/deepAR.py ran · our draft was wrong no licence file found · pointer only · 1ac937a48e910d3d · report fixture: signature sample:bool/0/bool · returned dict · level recorded 2026-09-22
update_metrics models/training/deepAR.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic no licence file found · pointer only · 28bb99867acbde6e · report fixture: signature raw_metrics:dict/0/?, input_mu:Tensor/2/float, input_sigma:Tensor/2/float, sample_mu:Tensor/2/float, labels:Tensor/2/float, predict_start:int/0/int, samples:Tensor/3/float, relative:bool/0/bool · returned dict · level recorded 2026-09-22

Tasks

Multivariate Time Series ForecastingProbabilistic Time Series ForecastingTime SeriesTime Series AnalysisTime Series Forecasting

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections