How Many Diagnoses Do We Need?

Abstract

A known limitation of many diagnosis algorithms is that the number of diagnoses they return can be very large. This raises the question of how to use such a large set of diagnoses. For example, presenting hundreds of diagnoses to a human operator (charged with repairing the system) is meaningless. In various settings, including decision support for a human operator and automated troubleshooting processes, it is sufficient to be able to answer a basic diagnostic question: is a given component faulty? We propose a way to aggregate an arbitrarily large set of diagnoses to return an estimate of the likelihood of a given component to be faulty. The resulting mapping of components to their likelihood of being faulty is called the system's health state. We propose two metrics for evaluating the accuracy of a health state and show that an accurate health state can be found without finding all diagnoses. An empirical study explores the question of how many diagnoses are needed to obtain an accurate enough health state, and a simple online stopping criterion is proposed.

Batch Repair with Heuristic Search

“…where SystemRepair(γ) is the probability that Repair(γ) will fix the system (SystemRepair( )can be derived automatically from Ω and p(•) (Stern et al 2015)). The values of cost F P and cost F N , however, are not known, and thus one cannot compute C W C .…”