10 Famous Systems
10 Famous Systems
10 Famous Systems
1. DENDRAL
First expert system
Project began at Stanford in mid 1960's, and is still being used.
Domain: Organic chemistry - mass spectrometry
Task: identify molecular structure of unknown compounds
from mass spectra data
Input: Histogram giving mass number/intensity pairs
Output: Description of structure of the compound
Architecture: plan-generate-test with constrained heuristic search
Tools: production rules implemented in Lisp
Results: "Discovery" of knowledge engineering.
Many published results.
DENDRAL
Winston
DENDRAL
Winston
DENDRAL
Winston p. 200
DENDRAL
Procedure:
1. Spectra data given as input
2. Preliminary analysis determines
- necessary compounds -- spectra data
- forbidden compounds -- spectra data, expert knowledge
3. Generate and test:
B. Ross
DENDRAL
Example rule for analyzer:
Winston 201
2. MACSYMA
Developed at MIT since 1968 onwards
Domain: high-performance symbolic math (algebra, calculus,
differential equations,...)
Task: carry out complex mathematical derivations
Input: formulae and commands (interactive)
Output: Solutions to tough problems
Method: Brute force (expert techniques are encoded as algorithm)
Architecture: programmed in Lisp (300,000 lines of code)
Results: Widely used, powerful system.
Newest version: Maxima
- Free! Open source.
- works on Windows, linux, MacOS
- maxima.sourceforge.net
B. Ross Cosc 4f79
MACSYMA
p.136-7 Harmon
3. Hearsay I and II
Developed at Carnegie-Mellon in late 1960's
Domain: speech understanding for simple database query
Task: Using specific vocabulary and grammar criteria, generate
correct speech recognition
Input: Speech wave
Output: Ordered list of hypotheses of what was said, plus database query
based on best guess
Architecture: Opportunistic, agenda-based reasoning, using "blackboard"
to record hypotheses from multiple independent knowledge sources
(Definition: Blackboard: common working memory for independent systems)
Tools: Programmed in SAIL
10
HEARSAY
Results:
- proved feasibility of automated speech recognition
- pioneering effort in system architecture techniques
- blackboard for multiple knowledge sources
- power of symbolic computation over purely statistical ones
- Spawned other expert system projects.
11
HEARSAY
Harmon 138
12
HEARSAY
Harmon 139
13
4. INTERNIST/CADUCEUS
Developed at U of Pittsburgh in early 1970's thru mid 80s
Domain: diagnostic aid for all of internal medicine
Task: medical diagnosis given interactive input
Input: Answers to interactive queries
Output: ordered set of diagnoses
Architecture: forward chaining with "scores" for diseases
Tools: programmed in Lisp
Results: ambitious project; inspired other systems
14
INTERNIST
p.141-144 Harmon
15
INTERNIST
16
5. MYCIN
Stanford U in mid 70's
Domain: Medical diagnosis for bacterial and meningitis infections
Task: interview physician, make diagnosis and therapy recommendations
Input: Answers to queries
Output: Ordered set of diagnoses and therapies
Architecture: rule-based exhaustive backward chaining with uncertainty
Tools: programmed in LISP (shell called EMYCIN -- empty MYCIN)
Results: not in general use, but was ground-breaking work in
diagnostic consultation systems
Made acceptable diagnoses at a rate of 69% (better than human experts!)
17
MYCIN
p.16-20 Harmon
18
6. Prospector
Developed at SRI international in late 1970's
Domain: exploratory geology
Task: evaluate geological sites
Input: geological survey data
Output: maps and site evaluations
Architecture: rule-like semantic net with uncertainty
Tools: programmed in LISP, and is a descendant of MYCIN
Results: In one blind test, the program identified a previously
undiscovered site, thus showing commercial viability of expert systems.
19
PROSPECTOR
p. 146 Harmon
20
PROSPECTOR
p. 145 Harmon
21
7. PUFF
Developed at Stanford in 1979
Domain: Diagnosis of obstructive airway diseases using MYCIN's
inference engine and a new knowledge base
Task: Take data from instruments and dialog, and diagnose type and
severity of disease
Input: instruments, queries
Output: Written report for physician to review and annotate
Architecture:
uncertainty
22
PUFF
p.150 Harmon
23
PUFF
p. 151 Harmon
24
8. XCON (R1)
Originally called R1, developed at Carnegie Mellon and DEC in late 70's
Domain: configure computer hardware
Task: configure VAX systems by projecting the need for subassemblies given
a high-level description of the system
Input: Vax system description
Output: list of parts, accessories, and a plan for assembly
Architecture: forward-chained, rule-based, with almost no backtracking
Tools: OPS5, a production system tool
Results: Used by DEC and performed better than previous experts (since fired)
- by 1986, processed total of 80,000 orders with 95-98% accuracy
- saved DEC $25 million a year
25
XCON
p. 156 Harmon
26
XCON
as of 1991, XCON has 8000 (!) production rules
a serious problem has developed: maintenance
has been said that XCON replaced 75 experts with 150 XCON maintainers
shows the need for developing better maintenance systems for large
expert systems (and other large software systems)
27
28
Conclusion
p. 170 Harmon
29
30
System
31
32