Design assistance for CAD frameworks

Lopez, J.C.; Jacome, M.F.; Director, Stephen W.

doi:10.1109/eurdac.1992.246308

Cited by 9 publications

(6 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Performance is only one part of the story. The design community is far away from fully exploiting the flexibility of RAs [34], supporting novel powerful techniques -directly in system jointly with all other components in real time, dramatically faster than simulation-for debugging, run-time profiling, verification, system-wide tuning, run-time API, field-Explorer System year source interactive status evaluation status generation DPE 1991 [49] no abstract models rule-based Clio 1992 [50] yes prediction models advice generator DIA 1998 [51] yes prediction fr. library rule-based DSE for RAW 1998 [41] no analytical models analytical ICOS 1998 [52] no fuzzy logic greedy search DSE f. Multimedia 1999 [53] no simulation branch and bound Xplorer 1999 [9] [42] yes fuzzy rule-based simulated annealing Fig.…”

Section: Discussionmentioning

confidence: 99%

“…Including effect predictors and proposal generators DPE (Design Planning System) [49] (using an expert system), Clio [50] (using a hierarchy of templates) and DIA (Datapath-Intensive ASICs) [51] (targeting semi-custom ASIC behavioural level and based on encapsulated expert knowledge), generate a design flow by creating a schematic, a data flow graph, or a layout from a specification and area, cycle time, power, e.a. constraints and to improve area, power, throughput etc.…”

Section: Design Space Explorationmentioning

confidence: 99%

See 1 more Smart Citation

Coarse grain reconfigurable architecture (embedded tutorial)

Hartenstein

2001

Proceedings of the 2001 Conference on Asia South Pacific Design Automation - ASP-DAC '01

View full text Add to dashboard Cite

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Design Space Explorationmentioning

confidence: 99%

Coarse grain reconfigurable architecture (embedded tutorial)

Hartenstein

2001

Proceedings of the 2001 Conference on Asia South Pacific Design Automation - ASP-DAC '01

View full text Add to dashboard Cite

show abstract

“…In this paper we present a formalism of design that allows for a complete, and general, characterization of design disciplines and for a unified representation of design processes that take place in the context of these disciplines. [1] This formalism has been used as the basis for the development of several prototype design process planning and management meta-tools (Minerva [2] and Clio [3]). The remainder of this paper is organized as follows.…”

Section: Introductionmentioning

confidence: 99%

A formal basis for design process planning and management

Jacome

Director

1996

IEEE Trans. Comput.-Aided Des. Integr. Circuits Syst.

Self Cite

View full text Add to dashboard Cite

In this paper we present a formalism that allows for a complete and general characterization of design disciplines and for a unified representation of arbitrarily complex design processes taking place in the context of these disciplines. This formalism has been used as the basis for the development of several prototype CAD meta-tools that offer effective design process planning and management services.

show abstract

“…The environment has a flexible application programming interface that allows a variety of external user interfaces to be used. In addition, since information resources and design data are becoming increasingly distributed across both the internet and company intranets, future versions of our design environment will be able to communicate with each other to share and reuse information and knowledge.Previous efforts in this area includes the work presented as "Clio", which offers design assistance within the Odyssey CAD framework [1][2] [3]. In Odyssey, knowledge is also organized in domains, but different domain hierarchies are not "orthogonal", i.e.…”

mentioning

confidence: 99%

“…Previous efforts in this area includes the work presented as "Clio", which offers design assistance within the Odyssey CAD framework [1][2] [3]. In Odyssey, knowledge is also organized in domains, but different domain hierarchies are not "orthogonal", i.e.…”

mentioning

confidence: 99%

A dynamic design estimation and exploration environment

Bentz

Rabaey

Lidsky

1997

Proceedings of the 34th Annual Conference on Design Automation Conference - DAC '97

View full text Add to dashboard Cite

many techniques that can be used to obtain estimates of power, so the design environment has to dynamically resolve which technique to use, based on all given parameters and constraints. The more constraints a designer gives, the more accurate or detailed the estimation can be, limited only by the available estimators.The observation that estimations generally are limited to a specific knowledge domain inspired the organization of estimation techniques, and all related parameters, constraints, etc., into entities called "domains".Definition: A "domain" is an encapsulation of knowledge regarding a specific design-related area of expertise. The knowledge which is captured in a domain includes parameters, constraints, tool encapsulations, file type definitions, etc. Domains are discussed in detail in section 3.1. A domain is intended to capture one dimension in the design space (e.g. architecture, cell library, technology, etc.), and domains can derive from other domains to capture increasingly confined portions of a particular dimension.By bringing together orthogonal domains, (i.e. domains that represent different dimensions in the design space) we can create a "context" which contains knowledge in the dimensions represented by the domains. This knowledge is as general or specific as the domains define.Definition: A "context" is a union of domains. Each design, or portion of a hierarchical design, has an associated context. The context can either be chosen by the designer, or it can be automatically chosen by the design environment, based on what is known about the design (parameters, constraints, properties, etc.). Intuitive commands are interpreted within a context, i.e. it is resolved what the meaning of a command is based on the knowledge contained in the union of domains.Example: To illustrate how intuitive commands are interpreted, consider the nine domains shown in figure 2. The six domains on the bottom are derived from the more general domains on top. The four sample contexts show by example how the command "area" is interpreted based on which domains are in the context.The presented environment offers ubiquitous access through the world wide web (WWW) to allow designers to use the environment remotely, for example from a portable terminal. The environment has a flexible application programming interface that allows a variety of external user interfaces to be used. In addition, since information resources and design data are becoming increasingly distributed across both the internet and company intranets, future versions of our design environment will be able to communicate with each other to share and reuse information and knowledge.Previous efforts in this area includes the work presented as "Clio", which offers design assistance within the Odyssey CAD framework [1][2] [3]. In Odyssey, knowledge is also organized in domains, but different domain hierarchies are not "orthogonal", i.e. representing different aspects of design. Thus, a context is represented by one domain, instead of a union of domains, an...

show abstract

Design assistance for CAD frameworks

Cited by 9 publications

References 8 publications

Coarse grain reconfigurable architecture (embedded tutorial)

Coarse grain reconfigurable architecture (embedded tutorial)

A formal basis for design process planning and management

A dynamic design estimation and exploration environment

Contact Info

Product

Resources

About