1988
DOI: 10.1109/64.21891
|View full text |Cite
|
Sign up to set email alerts
|

Argo: a system for design by analogy

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
8
0

Year Published

1988
1988
2022
2022

Publication Types

Select...
5
2
2

Relationship

0
9

Authors

Journals

citations
Cited by 24 publications
(8 citation statements)
references
References 17 publications
0
8
0
Order By: Relevance
“…This is described in (Carbonell, 1983). There may also be reasons to prefer more specific rules (Huhns & Acosta, 1988). However, when no deductive option is available this technique may give an alternative to backtracking or failure.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…This is described in (Carbonell, 1983). There may also be reasons to prefer more specific rules (Huhns & Acosta, 1988). However, when no deductive option is available this technique may give an alternative to backtracking or failure.…”
Section: Discussionmentioning
confidence: 99%
“…This transfer of knowledge between situations can be achieved by derivational analogy (Carbonell, 1983). Analogy has been used to map different situations to one another, in order to apply prior knowledge to a new situation (Huhns & Acosta, 1988); thereby performing transfer learning. This paper aims to use EBL and analogy in order to generate useful control rules for hardware which is outside the design of the controller.…”
Section: Analogymentioning
confidence: 99%
“…Analogies could be used to increase understanding of a novel design by allowing the designer to map previous experience onto the new device. There are many other uses for analogy in design, and there has been some work on models of design by analogy (Bhatta and Goel 1996, Howe et al 1986, Huhns and Acosta 1988. Other methods of transfer besides case-based reasoning and analogy have also been explored.…”
Section: Introductionmentioning
confidence: 99%
“…LEAP records the actions of the designer, generates proofs (or explanations) that those actions satisfy the design constraints, and then generalizes the proofs to create the conditions for new design rules. This idea has been further extended to acquiring generalized design plans in the ARGO system [18].…”
Section: Fig 42 -General Principles Of Designmentioning
confidence: 99%