User interface for specification language for case-based mechanical design

1997 ◽  
Vol 11 (1) ◽  
pp. 17-31 ◽  
Author(s):  
Abhay Dandekar ◽  
Ibrahim Zeid ◽  
Theodore Bardasz
Keyword(s):  
User Interface ◽  
Graphical User Interface ◽  
Current Problem ◽  
Mechanical Design ◽  
Specification Language ◽  
User Interactions ◽  
Design Problems ◽  
Context Free ◽  
Feature Attribute ◽  
Case Based

AbstractCase-based design (CBD) systems aim to solve a design problem by tailoring previously solved design problems to the current problem. Designers' specifications are used for indexing the knowledge base of the CBD system to retrieve an appropriate design case. Menu-based systems fail to capture designers' specifications effectively due to lack of expressiveness, while natural language systems are too immature to satisfy the goal. This paper presents the development of a graphical user interface (GUI) to implement a mechanical design specification language (MDSL) (Stelling, 1994) used to facilitate indexing in case-based mechanical design. The specification language is context-free and hence computable. It represents mechanical design knowledge in a (feature):(attribute) format suitable for indexing. An augmented transition network (ATN) parser is built using the grammar of the specification language. The parser provides syntactic as well as semantic checks. It also has capabilities to expand grammar and to adapt to a specific user domain. A graphical front end to the parser assists and guides the user through the specification language syntax in entering the design specifications. Provisions have been made to expand or edit the language grammar and vocabulary. The ATN parser was implemented in Common Lisp and the graphical user interface was written using the Gold Hill Windows Toolkit. Sample user interactions with the interface and screen dumps of the GUI are included.

scholarly journals Erratum

1997 ◽  
Vol 11 (2) ◽  
pp. 169-169
Keyword(s):  
User Interface ◽  
Mechanical Design ◽  
Specification Language ◽  
Image Position ◽  
Case Based

The following erratum is to correct an omission of a table during the publication phase of the article entitled: “User interface for specification language for case-based mechanical design” by Abhay Dandekar, Ibrahim Zeid, and Theodore Bardasz (AI EDAM, 11(1), p. 18).The table referred to reads:The Editor-In-Chief and Publisher regret the inadvertent mistake.

scholarly journals Leveraging Graphical User Interface Automation for Generic Robot Programming

Robotics ◽  
2020 ◽  
Vol 10 (1) ◽  
pp. 3
Author(s):  
Tudor B. Ionescu
Keyword(s):  
User Interface ◽  
Graphical User Interface ◽  
Programming Models ◽  
Shop Floor ◽  
Robot Programming ◽  
User Interactions ◽  
Programming Environments ◽  
Automated Generation ◽  
Novel Approach ◽  
Block Based

A novel approach to generic (or generalized) robot programming and a novel simplified, block-based programming environment, called “Assembly”, are introduced. The approach leverages the newest graphical user interface automation tools and techniques to generate programs in various proprietary robot programming environments by emulating user interactions in those environments. The “Assembly” tool is used to generate robot-independent intermediary program models, which are translated into robot-specific programs using a graphical user interface automation toolchain. The generalizability of the approach to list, tree, and block-based programming is assessed using three different robot programming environments, two of which are proprietary. The results of this evaluation suggest that the proposed approach is feasible for an entire range of programming models and thus enables the generation of programs in various proprietary robot programming environments. In educational settings, the automated generation of programs fosters learning different robot programming models by example. For experts, the proposed approach provides a means for generating program (or task) templates, which can be adjusted to the needs of the application at hand on the shop floor.

A Blackboard Architecture to Support Case-Based Reasoning in Mechanical Design

1992 ◽  
Author(s):  
Theodore Bardsz ◽  
Ibrahim Zeid
Keyword(s):  
Problem Solving ◽  
Engineering Design ◽  
Mechanical Design ◽  
Maximum Amount ◽  
Design Solution ◽  
Case Based Reasoning ◽  
Design Problems ◽  
Engineering Design Problems ◽  
Design Plan ◽  
Case Based

Abstract One of the most significant issues in applying case-based reasoning (CBR) to mechanical design is to integrate previously unrelated design plans towards the solution of a new design problem. The total design solution (the design plan structure) can be composed of both retrieved and dynamically generated design plans. The retrieved design plans must be mapped to fit the new design context, and the entire design plan structure must be evaluated. An architecture utilizing opportunistic problem solving in a blackboard environment is used to map and evaluate the design plan structure effectively and successfuly. The architecture has several assets when integrated into a CBR environment. First, the maximum amount of information related to the design is generated before any of the mapping problems are addressed. Second, mapping is preformed as just another action toward the evaluation of the design plan. Lastly, the architecture supports the inclusion of memory elements from the knowledge base in the design plan structure. The architecture is implemented using the GBB system. The architecture is part of a newly developed CBR System called DEJAVU. The paper describes DEJAVU and the architecture. An example is also included to illustrate the use of DEJAVU to solve engineering design problems.

DEJAVU: Case-based reasoning for mechanical design

1993 ◽  
Vol 7 (2) ◽  
pp. 111-124 ◽  
Author(s):  
Theodore Bardasz ◽  
Ibrahim Zeid
Keyword(s):  
Mechanical Design ◽  
Design Knowledge ◽  
Case Based Reasoning ◽  
Design Environment ◽  
Design Problems ◽  
Evaluation Module ◽  
Main Components ◽  
Domain Independent ◽  
Synergistic Relationship ◽  
Case Based

The architecture and implementation of a mechanical designer's assistant shell called DEJAVU is presented. The architecture is based on an integration of design and CAD with some of the more well known concepts in case-based reasoning (CBR). DEJAVU provides a flexible and cognitively intuitive approach for acquiring and utilizing design knowledge. It is a domain independent mechanical design shell that can incrementally acquire design knowledge in the domain of the user. DEJAVU provides a design environment that can learn from the designer(s) until it can begin to perform design tasks autonomously or semi-autonomously. The main components of DEJAVU are a knowledge base of design plans, an evaluation module in the form of a design plan system, and a blackboard-based adaptation module. The existance of these components are derived from the utilization of a CBR architecture. DEJAVU is the first step in developing a robust designer's assistant shell for mechanical design problems. One of the major contributions of DEJAVU is the development of a clean architecture for the utilization of case-based reasoning in a mechanical designer's assistant shell. In addition, the components of the architecture have been developed, tailored or modified from a general CBR context into a more synergistic relationship with mechanical design.

HOW TO USE CROP GROWTH MODEL WOFOST FOR FORECASTING GROWTH AND YIELD OF A CROP

2016 ◽  
Vol 3 (1) ◽  
Author(s):  
LAL SINGH ◽  
PARMEET SINGH ◽  
RAIHANA HABIB KANTH ◽  
PURUSHOTAM SINGH ◽  
SABIA AKHTER ◽  
...  
Keyword(s):  
User Interface ◽  
Graphical User Interface ◽  
Input Data ◽  
Growth And Yield ◽  
Weather Data ◽  
Data Sets ◽  
Crop Growth Model ◽  
Control Center ◽  
Field Crops ◽  
Crop Calendar

WOFOST version 7.1.3 is a computer model that simulates the growth and production of annual field crops. All the run options are operational through a graphical user interface named WOFOST Control Center version 1.8 (WCC). WCC facilitates selecting the production level, and input data sets on crop, soil, weather, crop calendar, hydrological field conditions, soil fertility parameters and the output options. The files with crop, soil and weather data are explained, as well as the run files and the output files. A general overview is given of the development and the applications of the model. Its underlying concepts are discussed briefly.

Sign in / Sign up

Export Citation Format

Share Document