Model-Based Reasoning: Troubleshooting
To determine why something has stopped working, it is useful to know how it was supposed to work in the first place. That simple observation underlies some of the considerable interest generated in recent years on the topic of model-based reasoning, particularly its application to diagnosis and trou...
| Main Authors: | , |
|---|---|
| Language: | en_US |
| Published: |
2004
|
| Online Access: | http://hdl.handle.net/1721.1/6491 |
| _version_ | 1810997008430792704 |
|---|---|
| author | Davis, Randall Hamscher, Walter C. |
| author_facet | Davis, Randall Hamscher, Walter C. |
| author_sort | Davis, Randall |
| collection | MIT |
| description | To determine why something has stopped working, it is useful to know how it was supposed to work in the first place. That simple observation underlies some of the considerable interest generated in recent years on the topic of model-based reasoning, particularly its application to diagnosis and troubleshooting. This paper surveys the current state of the art, reviewing areas that are well understood and exploring areas that present challenging research topics. It views the fundamental paradigm as the interaction of prediction and observation, and explores it by examining three fundamental subproblems: Generating hypotheses by reasoning from a symptom to a collection of components whose misbehavior may plausibly have caused that symptom; testing each hypothesis to see whether it can account for all available observations of device behavior; then discriminating among the ones that survive testing. We analyze each of these independently at the knowledge level, i.e., attempting to understand what reasoning capabilities arise from the different varieties of knowledge available to the program. We find that while a wide range of apparently diverse model-based systems have been built for diagnosis and troubleshooting, they are for the most part variations on the central theme outlined here. Their diversity lies primarily in the varying amounts and kinds of knowledge they bring to bear at each stage of the process; the underlying paradigm is fundamentally the same. Our survey of this familiar territory leads to a second major conclusion of the paper: Diagnostic reasoning from a model is reasonably understood. Given a model of behavior and structure, we know how to use it in a variety of ways to produce a diagnosis. There is, by contrast, a rich supply of open research issues in the modeling process itself. In a sense we know how to do model-based reasoning; we do not know how to model the behavior of complex devices, how to create models, and how to select the "right" model for the task at hand. |
| first_indexed | 2024-09-23T14:22:14Z |
| id | mit-1721.1/6491 |
| institution | Massachusetts Institute of Technology |
| language | en_US |
| last_indexed | 2024-09-23T14:22:14Z |
| publishDate | 2004 |
| record_format | dspace |
| spelling | mit-1721.1/64912019-04-10T18:33:51Z Model-Based Reasoning: Troubleshooting Davis, Randall Hamscher, Walter C. To determine why something has stopped working, it is useful to know how it was supposed to work in the first place. That simple observation underlies some of the considerable interest generated in recent years on the topic of model-based reasoning, particularly its application to diagnosis and troubleshooting. This paper surveys the current state of the art, reviewing areas that are well understood and exploring areas that present challenging research topics. It views the fundamental paradigm as the interaction of prediction and observation, and explores it by examining three fundamental subproblems: Generating hypotheses by reasoning from a symptom to a collection of components whose misbehavior may plausibly have caused that symptom; testing each hypothesis to see whether it can account for all available observations of device behavior; then discriminating among the ones that survive testing. We analyze each of these independently at the knowledge level, i.e., attempting to understand what reasoning capabilities arise from the different varieties of knowledge available to the program. We find that while a wide range of apparently diverse model-based systems have been built for diagnosis and troubleshooting, they are for the most part variations on the central theme outlined here. Their diversity lies primarily in the varying amounts and kinds of knowledge they bring to bear at each stage of the process; the underlying paradigm is fundamentally the same. Our survey of this familiar territory leads to a second major conclusion of the paper: Diagnostic reasoning from a model is reasonably understood. Given a model of behavior and structure, we know how to use it in a variety of ways to produce a diagnosis. There is, by contrast, a rich supply of open research issues in the modeling process itself. In a sense we know how to do model-based reasoning; we do not know how to model the behavior of complex devices, how to create models, and how to select the "right" model for the task at hand. 2004-10-04T15:12:53Z 2004-10-04T15:12:53Z 1988-07-01 AIM-1059 http://hdl.handle.net/1721.1/6491 en_US AIM-1059 4915061 bytes 3844740 bytes application/postscript application/pdf application/postscript application/pdf |
| spellingShingle | Davis, Randall Hamscher, Walter C. Model-Based Reasoning: Troubleshooting |
| title | Model-Based Reasoning: Troubleshooting |
| title_full | Model-Based Reasoning: Troubleshooting |
| title_fullStr | Model-Based Reasoning: Troubleshooting |
| title_full_unstemmed | Model-Based Reasoning: Troubleshooting |
| title_short | Model-Based Reasoning: Troubleshooting |
| title_sort | model based reasoning troubleshooting |
| url | http://hdl.handle.net/1721.1/6491 |
| work_keys_str_mv | AT davisrandall modelbasedreasoningtroubleshooting AT hamscherwalterc modelbasedreasoningtroubleshooting |