AI-enabled crack-length estimation from acoustic emission signal signatures

Sarah Ennis,Victor Giurgiutiu

Journal of nondestructive evaluation, diagnostics and prognostics of engineering systems(2023)

Cited 0|Views1
No score
Abstract
Abstract This article addresses the classification of fatigue crack length using artificial intelligence (AI) applied to acoustic emission (AE) signals. The AE signals were collected during fatigue of two specimen types. One specimen type had a 1-mm hole for crack initiation. The other specimen type had a 150-micron wide slit of various lengths. Fatigue testing was performed under stress-intensity-factor control to moderate crack advancement. The slit specimen produced AE signals only from crack advancement at the slit tips whereas the 1-mm hole specimens produced AE signals both from crack tip advancement and crack rubbing or clapping. The AE signals were captured with a piezoelectric wafer active sensor (PWAS) array connected to MISTRAS instrumentation and AEwin software. The collected AE signals were preprocessed using time-of-flight filtering and denoising. Choi Williams transform converted time-domain AE-signals into spectrograms. To apply machine learning, the spectrogram images were used as input data for the training, validation, and testing of a GoogLeNet convolutional neural network (CNN). The CNN was trained to sort the AE signals into crack-length classes. CNN performance enhancements, including synthetic data generation and class balancing were developed. A three-class example with crack lengths of (i) 10-12 mm; (ii) 12-14 mm; and (iii) 14-16 mm is provided. Our AI approach was able to classify the AE signals into these three classes with 91% accuracy thus proving that the AE signals contain sufficient information for crack estimation using an AI-enabled approach.
More
Translated text
Key words
acoustic emission signal signatures,estimation,ai-enabled,crack-length
AI Read Science
Must-Reading Tree
Example
Generate MRT to find the research sequence of this paper
Chat Paper
Summary is being generated by the instructions you defined