Papers › Oscillatory State-Space Models

Oscillatory State-Space Models

4 Oct 2024arXiv:2410.03943archive 2025-07-28

T. Konstantin Rusch, Daniela Rus

We propose Linear Oscillatory State-Space models (LinOSS) for efficiently learning on long sequences. Inspired by cortical dynamics of biological neural networks, we base our proposed LinOSS model on a system of forced harmonic oscillators. A stable discretization, integrated over time using fast associative parallel scans, yields the proposed state-space model. We prove that LinOSS produces stable dynamics only requiring nonnegative diagonal state matrix. This is in stark contrast to many previous state-space models relying heavily on restrictive parameterizations. Moreover, we rigorously show that LinOSS is universal, i.e., it can approximate any continuous and causal operator mapping between time-varying functions, to desired accuracy. In addition, we show that an implicit-explicit discretization of LinOSS perfectly conserves the symmetry of time reversibility of the underlying dynamics. Together, these properties enable efficient modeling of long-range interactions, while ensuring stable and accurate long-horizon forecasting. Finally, our empirical results, spanning a wide range of time-series tasks from mid-range to very long-range classification and regression, as well as long-horizon forecasting, demonstrate that our proposed LinOSS model consistently outperforms state-of-the-art sequence models. Notably, LinOSS outperforms Mamba by nearly 2x and LRU by 2.5x on a sequence modeling task with sequences of length 50k.

PaperPDFCodeCode Syntology ran

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

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2410.03943")

Code

Syntology Ran 4 of 8 code samples harvested from 1 repository linked to this paper; 4 have no recorded run. Of those that ran: 2 ran · our draft was wrong; 2 ran with no contract checked.

By repository: community (archive-listed): 8 samples from 1 repository, 4 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

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

8 samples harvested; 4 ran; 0 honoured the contract we drafted; 4 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

2ran · our draft was wrong
2ran
4unverified

Licence: 0 of the 8 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 tk-rusch/linoss. “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. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (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 from a repository marked official are listed first. 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 four 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; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). 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.

LinOSSLayer tk-rusch/linoss/models/LinOSS.py community (archive-listed) ran fingerprinted MIT (permissive) · 89731cf15fbb7099 · report
apply_linoss_im tk-rusch/linoss/models/LinOSS.py community (archive-listed) ran fingerprinted MIT (permissive) · 24eeb5f0aa98ab68 · report
binary_operator tk-rusch/linoss/models/LinOSS.py community (archive-listed) ran · our draft was wrong MIT (permissive) · 11738ec367aede4b · report
simple_uniform_init tk-rusch/linoss/models/LinOSS.py community (archive-listed) ran · our draft was wrong MIT (permissive) · 85bf175cdac4f823 · report
GLU tk-rusch/linoss/models/LinOSS.py community (archive-listed) unverified MIT (permissive) · eb21c6dcd5f470d8 · report
LinOSS tk-rusch/linoss/models/LinOSS.py community (archive-listed) unverified MIT (permissive) · e841118ce22d477e · report
LinOSSBlock tk-rusch/linoss/models/LinOSS.py community (archive-listed) unverified MIT (permissive) · ceb50921398bae85 · report
apply_linoss_imex tk-rusch/linoss/models/LinOSS.py community (archive-listed) unverified MIT (permissive) · 909ae39b93de5731 · report

Tasks

MambaState Space Models

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

BASEMamba

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