Papers › When are dynamical systems learned from time series data statistically accurate?

When are dynamical systems learned from time series data statistically accurate?

9 Nov 2024arXiv:2411.06311archive 2025-07-28

Jeongjin Park, Nicole Yang, Nisha Chandramoorthy

Conventional notions of generalization often fail to describe the ability of learned models to capture meaningful information from dynamical data. A neural network that learns complex dynamics with a small test error may still fail to reproduce its physical behavior, including associated statistical moments and Lyapunov exponents. To address this gap, we propose an ergodic theoretic approach to generalization of complex dynamical models learned from time series data. Our main contribution is to define and analyze generalization of a broad suite of neural representations of classes of ergodic systems, including chaotic systems, in a way that captures emulating underlying invariant, physical measures. Our results provide theoretical justification for why regression methods for generators of dynamical systems (Neural ODEs) fail to generalize, and why their statistical accuracy improves upon adding Jacobian information during training. We verify our results on a number of ergodic chaotic systems and neural network parameterizations, including MLPs, ResNets, Fourier Neural layers, and RNNs.

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 16 code samples harvested from 1 repository linked to this paper: 8 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 3 where Syntology's instrument failed) · 8 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 16 samples from 1 repository, 8 ran (5 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.

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

ni-sha-c/stacnode officialmentioned in paperjaxSyntology: 16 samples, 8 ran (3 instrument-failed) · 8 unverified 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.

Code Syntology ran Syntology

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

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

Licence: 16 of the 16 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 ni-sha-c/stacnode. “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.

ni-sha-c/stacnode official repository 16 samples, 8 ran (3 instrument-failed) · 8 unverified
baker dyn_sys/dim2.py ran; the contract check could not run (RAISES) no licence file found · pointer only · ef392ad5c91d0746 · report fixture: signature X:tuple/1/Tensor, s3:float/0/float · returned Tensor · level recorded 2026-09-25
hyperchaos dyn_sys/dim4.py ran · our draft was wrong no licence file found · pointer only · fd4b8cebbb796086 · report fixture: signature t:float/0/float, X:tuple/1/Tensor · returned Tensor · level recorded 2026-09-25
lorenz in 11 papers dyn_sys/dim3.py ran no licence file found · pointer only · 93473ef0e934a7aa · report fixture: signature t:Tensor/0/float, u:Tensor/1/float, rho:float/0/float · returned Tensor · level recorded 2026-09-25
one_step_rk4 src/util.py ran no licence file found · pointer only · ce72947f8f7790fb · report fixture: signature f:callable/0/?, y0:Tensor/2/float, t:Tensor/1/float · returned Tensor · level recorded 2026-09-25
pinched_tent_map dyn_sys/dim1.py ran no licence file found · pointer only · 5fd8739b02954492 · report fixture: signature x:float/0/float, s:float/0/float · returned Tensor · level recorded 2026-09-25
rhs_KS_implicit dyn_sys/KS.py ran no licence file found · pointer only · 3d53f5662267e430 · report fixture: signature u:Tensor/1/float, dx:float/0/float, device:str/0/str · returned Tensor · level recorded 2026-09-25
rossler dyn_sys/dim3.py ran; the contract check could not run (RAISES) no licence file found · pointer only · 142c1ff3455d0696 · report fixture: signature t:Tensor/0/float, X:tuple/1/Tensor · returned Tensor · level recorded 2026-09-25
tilted_tent_map dyn_sys/dim1.py ran no licence file found · pointer only · caef15b9f4d5d675 · report fixture: signature x:Tensor/0/float, s:float/0/float · returned Tensor · level recorded 2026-09-25
Jacobian_Brusselator src/jacobian.py unverified no licence file found · pointer only · 2b9bad8cf287f61b · report
Jacobian_Henon src/jacobian.py unverified no licence file found · pointer only · 3f099c3031cf7c6d · report
Jacobian_Matrix src/jacobian.py unverified no licence file found · pointer only · b661eb54386be27e · report
create_data in 5 papers src/util.py unverified no licence file found · pointer only · 8153624831bf335c · report
define_dyn_sys src/util.py unverified no licence file found · pointer only · b62622cd18148570 · report
plucked_tent_map dyn_sys/dim1.py unverified no licence file found · pointer only · 5d4b3638f6d9857e · report
rhs_KS_explicit_linear dyn_sys/KS.py unverified no licence file found · pointer only · a31c1b0189739974 · report
rhs_KS_explicit_nl dyn_sys/KS.py unverified no licence file found · pointer only · b9d0d258e42f2577 · report

Tasks

Time Series

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