MoRF-AST: Calibrated Probabilistic Virtual Sensing for Structural Monitoring under Changing Operating Conditions

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:2608.24531v1 Announce Type: cross Abstract: Probabilistic full-field reconstruction provides uncertainty-aware response evidence for structural reliability assessment, yet inference from sparse and noisy measurements remains underdetermined. Most existing methods overlook shifts between offline training and operational distributions. Under such shifts, posterior intervals may become miscalibrated, causing the reported uncertainty to lose its probabilistic meaning. This study proposes Modal Residual Flow Matching with Context-Conditioned Affine Spread Transport (MoRF-AST) for calibrated structural virtual sensing under changing operating conditions. MoRF constructs an analytic Gaussian reference posterior in normalized modal coordinates and trains a conditional flow only on posterior-whitened residuals. At deployment, AST estimates response scale from historical measurements at installed sensors and uses gated, mean-preserving Bures-Wasserstein transport to adjust posterior spread. On a bridge-deck benchmark, MoRF achieves a posterior-mean normalized root-mean-square error (NRMSE) of 7.20%, compared with 16.1% and 17.9% for two direct conditional flows. Across eight shifted traffic domains, AST reduces MoRF's cross-domain average coverage error from 0.0535 to 0.0236, a 55.9% reduction, while preserving posterior-mean accuracy. The same transport does not improve the tested alternatives in aggregate, showing that calibration gains require its direction to match the base posterior's dispersion bias. MoRF-AST provides a data-efficient framework for probabilistic …

Vollständiger Originalartikel ↗

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