Defining Energy Indicators for Impact Identification on Aerospace Composites: A Structured Feature Selection Approach Guided by Domain Knowledge

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:2511.01592v2 Announce Type: replace Abstract: Energy estimation is critical to impact identification on aerospace composites, where low-velocity impacts can induce internal damage that is undetectable at the surface. Data sparsity, signal noise, complex feature interdependencies, non-linear dynamics, massive design spaces, and the ill-posed nature of the inverse problem often constrain current methodologies for energy prediction. Machine learning enriched with prior knowledge is a promising direction for overcoming these constraints. Prior knowledge can be incorporated by acting on the input space, where the choice of data representation directly influences how effectively the model relates measured signals to impact energy. Despite its importance, the selection of effective features lacks a systematic procedure, with no consensus on how to choose among the many candidate descriptors available. The present study addresses that gap through a structured workflow that designs the input space using domain knowledge. Features are extracted from the time, frequency, and time-frequency domains, then filtered for statistical significance, correlation, dimensionality reduction, and robustness to noise. Exploratory data analysis further relates the retained descriptors to the dynamics. The resulting indicators form the input space for a fully connected neural network, which is trained and validated on experimental data from multiple impact scenarios, including pristine and damaged states. The model reduces the prediction error by a factor of three relative to conventional …

Vollständiger Originalartikel ↗

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