Abstract Industrial robot grasping faces several key challenges, such as subtle anomaly features, scarce abnormal samples, significant domain shifts in training trajectories, and constrained edge computing capacities. To address these issues, this study introduces an unsupervised anomaly detection method, namely the Physical Residual-Decoupled U-shaped Kolmogorov-Arnold Network (PR-UKAN). Unlike a simple combination of physical modeling, U-shaped reconstruction, and KAN-based nonlinear fitting, PR-UKAN is motivated by a residual-decoupled semantic-conflict interpretation. Specifically, physical residual decoupling based on robot dynamics first removes task-level macroscopic motion interference and converts weak disturbances into physically meaningful residual features; cascaded smoothing and differential enhancement then expose transient micro-anomaly components that are easily submerged in raw sensor signals; finally, the U-KAN autoencoder preserves local high-frequency abnormal details through skip connections while the Efficient-KAN bottleneck constrains the reconstruction to the normal global manifold learned from anomaly-free samples. The observed branch behavior is consistent with the interpretation that a mismatch between local abnormal details and the normal bottleneck representation may increase reconstruction errors for out-of-distribution micro-anomalies. On the voraus-AD dataset, PR-UKAN achieved a mean AUROC of 93.7±0.4%, compared with 93.1±5.8% for MVT-FLOW under the common evaluation protocol. This descriptive difference did not establish statistical superiority. The measured CPU forward-reconstruction time was 4.19±0.68 ms for one preprocessed 1×36×1168 sequence. Because preprocessing and anomaly scoring were excluded, this measurement did not represent end-to-end detection latency. These results indicate competitive detection performance under the evaluated protocol, while real-time online deployment remains to be validated.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The perception of the impact of agile methods is predominantly positive, and several challenge areas were discovered, but based on this study, agile methods are here to stay.
M. Laanti, O. Salo, P. Abrahamsson· Information and Software Tec...· 260 citations· ⚡20
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 8, 2026
Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity. The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.