Backend
A Memory Efficient Unified Algorithm for Online Learning of Linear Dynamical Systems
arXiv eess.SY0 views
arXiv:2607.02050v3 Announce Type: replace-cross Abstract: Motivated by the challenge of stabilizing a general unknown linear dynamical system (LDS) from observations, we study the natural prerequisite of online prediction. Our goal is to achieve sublinear regret with a memory footprint that adapts to the intrinsic complexity of the dynamics rather than the full hidden-state dimension. We focus on the practically central regime of systems with low instability complexity -- eigenvalues outside the real stable interval that do not decay rapidly, together with non-semisimple modes -- potentially embedded in an otherwise stable real spectrum of much higher dimension; we write $k$ for this count. This regime is the primary setting in which stabilization is plausible: we show that many systems with high instability complexity cannot be stabilized without exponentially large controls. Thus, prediction is meaningful for stabilization precisely when the instability complexity is small. Within this regime, we introduce a unified online algorithm that handles every LDS (including non-diagonalizable systems with complex or exploding modes) with a learnable parameter count of $\widetilde{O}(k)$. Finally, we prove a lower bound showing that $k$ is a valid complexity measure: any filter-based predictor needs at least $k$ filters. Experiments corroborate our theory: on a high-dimensional system, our predictor sharply outperforms prior methods at an equal parameter budget.
Source:https://arxiv.org/abs/2607.02050PreviousBeyond Benchmarks: Continuous Edge Inference for Traffic Sign Recognition on Embedded Vehicular HardwareNextRADAR Perception for Dynamic Obstacle Avoidance onboard small-scale Quadrotor UAVs
Related posts
From One Sentence to a Working App: What Vibe Coding Gets Right — and Where It Still Needs You
0dev.to
A button people press 57 times per visit: building a no-backend tap counter that doesn't lose counts
0dev.to
The 15-Day Clock: Could You Reconstruct an AI Incident Before the Deadline?
0dev.to
DOBI: machine identity, DAMs, and x402 payments as a device workflow
0dev.to

When "Not Found" Doesn't Mean "Never Happened"
0dev.to
Blameless Postmortems: A Leader’s Guide to Learning From Incidents
0dev.to