Probabilistic Diagnosis of Intermittent Faults

You are reading version 1 of this direction, frozen 2026-10-04. The latest version is version 2.

Version 1 of 223 papers36 conceptsfrozen 2026-10-04

In traditional engineering, we often assume that if a component breaks, it stays broken. This "persistence assumption" simplifies troubleshooting: if a system fails, you look for the broken part; if a test passes, you "exonerate" the components involved and move on.

However, real-world systems—from deep-space probes to nationwide communication networks—frequently suffer from intermittent faults. These are the "ghosts in the machine" that appear and disappear without intervention. As Johan de Kleer notes in Diagnosing Multiple Persistent and Intermittent Faults, these faults are notoriously difficult to isolate because they violate the basic logic of binary diagnosis. When a component only fails sporadically, a passing test is no longer proof of health.

The Flaw of Binary Exoneration

The core challenge of intermittent diagnosis is the "No Fault Found" (NFF) phenomenon. Jing Qiu and colleagues explain in Intermittent fault’s parameter framework and stochastic petri net based formalization model that NFF outcomes occur when a system fails in the field but appears functional during maintenance.

Traditional diagnostic engines use a process of elimination. If a software test passes, every line of code executed during that test is assumed to be correct. But in the presence of "flaky tests" or race conditions, a faulty component might produce a correct output 90% of the time. Rui Abreu 0001, Peter Zoeteweij, and Arjan J. C. van Gemund addressed this in their work on BARINEL (A New Bayesian Approach to Multiple Intermittent Fault Diagnosis). Instead of exonerating components, they treat a passing test as probabilistic evidence.

BARINEL uses maximum likelihood estimation to calculate a "failure intermittency parameter"—the exact probability that a faulty component will "act healthy" during any given observation. This allows the diagnostic engine to maintain a suspicion level for a component even if it just passed a test, preventing the algorithm from prematurely ruling out the true culprit.

Modeling the Temporal Dimension

Intermittent faults are often tied to time or specific system states. A loose connection might only cause data corruption during high-vibration maneuvers, or a transistor might only fail when it reaches a specific thermal threshold.

To catch these, researchers have moved toward temporal and state-based modeling:

Why Intermittency is More Dangerous Than Failure

A permanent failure is often "safe" because it triggers binary monitors. If a motor dies, the system stops. However, as Homa Alemzadeh and Zbigniew Kalbarczyk demonstrate in the context of robotic surgery, intermittent faults can bypass these safety triggers (Systems-Theoretic Safety Assessment of Robotic Telesurgical Systems).

A transient data glitch might cause a robotic arm to "jump" or vibrate violently without ever triggering an emergency stop, because the system's monitors are looking for a total hardware shutdown, not a momentary deviation. This makes the ability to diagnose and route around intermittent faults essential for cyber-physical resilience, a theme echoed by Xu Zheng in the study of smart city infrastructures (Special Issue on Selected Technologies and Applications in Wireless Communications for Smart City Computing).

Scaling Diagnosis to Big Data

When dealing with billions of web requests or nationwide networks, simple logic models break down. John C. Platt and Emre Kiciman pioneered the use of fast variational inference to handle this scale (Fast Variational Inference for Large-scale Internet Diagnosis). By using a "noisy-OR" graphical model, they could probabilistically link intermittent failures across a massive bipartite graph of users and services, identifying root causes in hours rather than days.

Similarly, in software testing, the SEQUOIA algorithm (Spectrum-Based Sequential Diagnosis) and the TDP paradigm by Tom Zamir and Roni Stern use Markov Decision Processes to intelligently choose the next test to run. By explicitly modeling the "flakiness" of a bug, these systems can reduce the number of tests needed to find a fault by up to 80% (Using Model-Based Diagnosis to Improve Software Testing).

Summary of the Intuition

The shift in this research area is from deterministic elimination to probabilistic accumulation.

  1. Don't Exonerate: A passing test is just a "maybe."
  2. Model the Flicker: Every component has a probability of failing and a probability of "acting healthy" while failed.
  3. Use Context: Look for faults that only appear during specific state transitions or time windows.
  4. Update Beliefs: Use Bayesian inference to constantly adjust the suspicion level of every component based on a stream of noisy, intermittent observations.

Papers in this version

History & citationVersion 2 · 2026-10-04

Current · Permanent link

  1. Version 2 (latest) · 2026-10-04 · 40 papers
  2. Version 1 · 2026-10-04 · 23 papers
Cite this direction

Latest version (a living page):

@misc{lacuna_intermittent_fault_modeling_95378582,
  title = {intermittent fault modeling},
  author = {{Lacuna}},
  howpublished = {Lacuna research direction},
  year = {2026},
  url = {https://lacuna.tiptreesystems.com/direction/intermittent-fault-modeling/rdr_95378582e4794e06892c47772a89ec2e},
  note = {Latest version of a living research direction; cite a version for a fixed text. Accessed 2026-11-19},
}

This exact version (version 1, frozen text):

@misc{lacuna_probabilistic_diagnosis_of_intermittent__95378582_v1,
  title = {Probabilistic Diagnosis of Intermittent Faults},
  author = {{Lacuna}},
  howpublished = {Lacuna research direction},
  year = {2026},
  url = {https://lacuna.tiptreesystems.com/direction/probabilistic-diagnosis-of-intermittent-faults/rdr_95378582e4794e06892c47772a89ec2e/v/1},
  note = {Version 1, frozen 2026-10-04. Accessed 2026-11-19},
}