Papers › AR-Net: A simple Auto-Regressive Neural Network for time-series
AR-Net: A simple Auto-Regressive Neural Network for time-series
Oskar Triebe, Nikolay Laptev, Ram Rajagopal
In this paper we present a new framework for time-series modeling that combines the best of traditional statistical models and neural networks. We focus on time-series with long-range dependencies, needed for monitoring fine granularity data (e.g. minutes, seconds, milliseconds), prevalent in operational use-cases. Traditional models, such as auto-regression fitted with least squares (Classic-AR) can model time-series with a concise and interpretable model. When dealing with long-range dependencies, Classic-AR models can become intractably slow to fit for large data. Recently, sequence-to-sequence models, such as Recurrent Neural Networks, which were originally intended for natural language processing, have become popular for time-series. However, they can be overly complex for typical time-series data and lack interpretability. A scalable and interpretable model is needed to bridge the statistical and deep learning-based approaches. As a first step towards this goal, we propose modelling AR-process dynamics using a feed-forward neural network approach, termed AR-Net. We show that AR-Net is as interpretable as Classic-AR but also scales to long-range dependencies. Our results lead to three major conclusions: First, AR-Net learns identical AR-coefficients as Classic-AR, thus being equally interpretable. Second, the computational complexity with respect to the order of the AR process, is linear for AR-Net as compared to a quadratic for Classic-AR. This makes it possible to model long-range dependencies within fine granularity data. Third, by introducing regularization, AR-Net automatically selects and learns sparse AR-coefficients. This eliminates the need to know the exact order of the AR-process and allows to learn sparse weights for a model with long-range dependencies.
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):
get_harvested_code_for_paper(arxiv_id="1911.12436")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="1911.12436", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="1911.12436")
Code
Syntology 18 code samples harvested from 1 repository linked to this paper: 18 ran (of which 0 constructed an object rather than computing a result; 18 with no instrument failure: 0 honoured, 0 violated, 18 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.
By repository: official repository: 18 samples from 1 repository, 18 ran (18 with no instrument failure; 0 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 1 of its repositories that Syntology harvested for other papers:
- ourownstory/neural_prophet, community (archive-listed): harvested for another paper, listed under the repository
Levels written on 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.
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
18 samples harvested: 18 ran (of which 0 constructed an object rather than computing a result; 18 with no instrument failure: 0 honoured, 0 violated, 18 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures 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.
Licence: 0 of the 18 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 ourownstory/AR-Net. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.
527c7a9c2c4390e8 · report
fixture: signature est:ndarray/1/float, real:ndarray/1/float · returned float64 · level recorded 2026-09-25 d2af38682f6a1872 · report
fixture: signature results:dict/0/?, ar_params:ndarray/1/float, verbose:bool/0/bool · returned dict · level recorded 2026-09-25 89aadc6713c1f998 · report
fixture: signature series:ndarray/1/float, n_samples:int/0/int, sample_inp_size:int/0/int, sample_out_size:int/0/int, test:float/0/float, verbose:bool/0/bool, plot:bool/0/bool · returned tuple · level recorded 2026-09-25 c5efe350961d5eec · report
fixture: signature series:Series/1/float · returned float · level recorded 2026-09-25 dedbe9f211d8a475 · report
fixture: signature samples:int/0/int, ar_order:int/0/int, ma_order:int/0/int, noise_std:float/0/float, params:NoneType/0/? · returned tuple · level recorded 2026-09-25 0fc28d6ea3be0c4e · report
fixture: signature samples:int/0/int, noise_std:float/0/float, random_order:NoneType/0/?, params:tuple/1/ndarray, limit_abs_sum:bool/0/bool · returned tuple · level recorded 2026-09-25 991728b9f349a958 · report
fixture: signature results:dict/0/? · returned dict · level recorded 2026-09-25 f0883fc3148edfe1 · report
fixture: signature sources:list/1/dict · returned dict · level recorded 2026-09-25 e3506f6fa263adee · report
fixture: signature verbose:bool/0/bool, random:bool/0/bool · returned tuple · level recorded 2026-09-25 1bec0033bd0ae665 · report
fixture: signature data_path:str/0/str, data_name:str/0/str, load_config:bool/0/bool, verbose:bool/0/bool · returned tuple · level recorded 2026-09-25 786d91b066124aab · report
fixture: signature data:list/1/list · returned list · level recorded 2026-09-25 d10ec2aad3023ee6 · report
fixture: signature ar_params:list/1/list, n_lags:int/0/int, n_forecasts:int/0/int · returned list · level recorded 2026-09-25 census: 8 implementations from 9 papers, 7 distinct outputs across 5 buckets, one shared input per bucket v0_1/data_loader.py ran MIT (permissive) ·
638404fea1331535 · report
fixture: signature y:ndarray/1/float, offset:int/0/int, sample_inp_size:int/0/int, sample_out_size:int/0/int · returned tuple · level recorded 2026-09-25 06ac13db47706965 · report
fixture: signature save_path:str/0/str, series:ndarray/2/float, data_config:dict/0/? · returned str · level recorded 2026-09-25 a6349579c34e4496 · report
fixture: signature valid_p:float/0/float, n_sample:int/0/int, verbose:bool/0/bool · returned list · level recorded 2026-09-25 b0ff57b3010828b6 · report
fixture: signature series:DataFrame/0/?, n_lags:int/0/int, n_forecasts:int/0/int, nested_list:bool/0/bool · returned DataFrame · level recorded 2026-09-25 5c858795ca664e3c · report
fixture: signature model:callable/0/?, x:Tensor/2/float, y:Tensor/2/float, loss_fn:callable/0/? · returned tuple · level recorded 2026-09-25 b90b111ca6a0d319 · report
fixture: signature model:callable/0/?, x:Tensor/2/float, y:Tensor/2/float, optimizer:SGD/0/?, loss_fn:callable/0/?, lambda_value:float/0/float · returned float · level recorded 2026-09-25 Tasks
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