← Latest papers
🤖 machine learning

Evaluating deep learning models for fault diagnosis of a rotating machinery with epistemic and aleatoric uncertainty

This paper presents the first comprehensive comparative study of uncertainty-aware deep learning models for rotating machinery fault diagnosis, demonstrating that deep ensemble architectures outperform other state-of-the-art methods in detecting both epistemic and aleatoric uncertainties while offering shorter inference times.

Original authors: Reza Jalayer, Masoud Jalayer, Andrea Mor, Carlotta Orsenigo, Carlo Vercellis

Published 2026-06-19
📖 5 min read🧠 Deep dive

Original authors: Reza Jalayer, Masoud Jalayer, Andrea Mor, Carlotta Orsenigo, Carlo Vercellis

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are a mechanic trying to diagnose a problem with a giant, spinning industrial motor. You have a computer program (a "Deep Learning Model") that has been trained on thousands of recordings of this motor running perfectly, plus recordings of it with three specific, known problems (like a broken ball bearing or a cracked inner race).

The problem is: What happens when the motor makes a sound the computer has never heard before? Or, what if the microphone recording the sound is just really staticky?

This paper is like a massive "stress test" for different types of computer programs to see which one is best at saying, "Hey, I don't know what this is, or the data is too messy to trust!" instead of confidently guessing the wrong answer.

Here is the breakdown of the study using simple analogies:

1. The Two Types of "Confusion"

The researchers tested the computers against two different kinds of confusion:

  • Epistemic Uncertainty (The "Blind Spot"): Imagine the computer was trained only on dogs and cats. If you show it a picture of a hamster, it doesn't know it's a hamster. It might guess "dog" or "cat" confidently, but it's wrong. In the factory, this happens when a brand new type of fault appears that the computer has never seen. The computer lacks the knowledge to identify it.
  • Aleatoric Uncertainty (The "Static"): Imagine the computer is trying to listen to a song, but someone is screaming next to the microphone. The data is there, but it's noisy. The computer might get confused because the signal is dirty. In the factory, this is caused by electrical interference or a shaky sensor.

2. The Contenders: Three Different "Detectives"

The paper compared three different ways of building these computer programs to see which detective is best at spotting the "unknowns" or the "noise":

  • The "Gambler" (ConvLSTM-D): This model tries to guess the answer, but every time it makes a guess, it randomly forgets a few facts (like a student who closes their eyes and guesses). It does this 10 times. If it gets 10 different answers, it knows it's confused.
  • The "Probabilist" (Bayesian Neural Network): This model doesn't just have one set of facts; it has a whole library of possible versions of itself. It asks all of them for an opinion. If the library members disagree, it knows it's uncertain.
  • The "Council" (Deep Ensemble): This is the star of the show. Instead of one detective, they hire a team of four different detectives. They all look at the same problem independently. If the team agrees, it's a safe bet. If they all start arguing, the system knows, "Wait, something is weird here."

3. The Rules of the Game

To test them, the researchers created two scenarios:

  1. The "Unknown Fault" Test: They trained the computers on 5 types of motor problems, then secretly tested them on the 6th type (which they had never seen).
  2. The "Noise" Test: They took clean recordings and added different kinds of static (like the hiss of a radio, the crackle of a spark, or random static) to see if the computers could still tell the difference between a healthy motor and a broken one.

They also tested two different "alarm bells" (thresholds) to decide when to raise the red flag:

  • The "Panic Button" (Threshold 1): This is a very sensitive alarm. It screams "DANGER" at the slightest hint of confusion. It catches almost all the bad stuff, but it also screams at a lot of normal, healthy motors (false alarms).
  • The "Balanced Judge" (Threshold 2): This is a new method the authors invented. It tries to find the perfect middle ground where it catches the bad stuff without screaming at the good stuff too much.

4. The Results: Who Won?

  • When facing "Unknown Faults" (Epistemic): The Deep Ensemble (The Council) was the clear winner. It was the best at saying, "I don't know this," without guessing wrong. The other two models often confidently guessed the wrong fault.
  • When facing "Noise" (Aleatoric): The Deep Ensemble was again the winner. Interestingly, the more noise there was, the easier it was for the computers to realize something was wrong (because the noise made the data look very strange). However, when the noise was very low (just a little bit of static), it was very hard for any model to tell the difference. Even then, the Deep Ensemble handled the situation better than the others.
  • Speed: The Deep Ensemble took longer to train (learning the ropes) because they had to teach four detectives instead of one. However, once they were trained, they were actually faster at making a diagnosis than the other models. Why? Because the other models had to run their "guessing game" 10 times for every single check, while the Deep Ensemble just asked its four members once.

5. The Bottom Line

If you are building a system to monitor machines in the real world, the paper suggests you should use the Deep Ensemble approach.

  • It is the most reliable at spotting new, unknown problems.
  • It is the most robust when the sensors are noisy.
  • It is faster to run once it's set up.

The authors also suggest that if you are in a super-critical situation (like a nuclear plant), you should use the "Panic Button" alarm (Threshold 1) to catch everything, even if it means checking a few false alarms. If you are in a less critical situation, use the "Balanced Judge" (Threshold 2) to save time and effort.

In short: When you need a machine to tell you when it's sick, or when it's confused by a new disease, or when the microphone is broken, hiring a team of diverse experts (Deep Ensemble) works better than relying on a single expert who tries to guess or a single expert who is unsure of their own facts.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →