Perseus: Interactive Time Series Segmentation with Sparse Supervision via Stateful Memory

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2510.09930v2 Announce Type: replace-cross Abstract: Real-world systems, ranging from industrial manufacturing to wearable healthcare, generate multivariate time series with hierarchical states ranging from coarse regimes to fine-grained events. Unlike zero- or few-shot segmentation, our setting uses dense state labels for model training. Sparse expert prompts provide inference-time corrections that resolve sequence-specific ambiguities without retraining. In practice, this feedback is grouped around selected events or transitions, leaving large portions of the timeline unprompted. The prompt-based sliding-window baselines evaluated here are stateless with respect to user interaction history: they use guidance only within the current window and cannot retain it across these gaps. To address this, we propose Perseus (Persistent Segmentation with User Supervision), a framework that transitions from synchronous processing to asynchronous state management. Perseus decouples supervision from inference via a distinct Write-Read architecture: grouped user cues are asynchronously encoded into a persistent memory bank (Write), which is then actively queried by the inference engine (Read) to service unprompted windows. This mechanism bridges supervision gaps by conditioning predictions on a global history of interactions rather than solely on local inputs. Extensive experiments on six datasets demonstrate that while evaluated stateless prompting baselines degrade significantly under grouped supervision, Perseus maintains robustness and achieves up to 85% accuracy improvement …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2510.09930
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.