Not enough data to create a plot.
Try a different view from the menu above.
taxnodes:Technology: Instructional Materials
Artificial Intelligence Research in Australia -- A Profile
Smith, Elizabeth, Whitelaw, John
Does the United States have a 51st state called Australia? A superficial look at the artificial intelligence (AI) research being done here could give that impression. A look beneath the surface, though, indicates some fundamental differences and reveals a dynamic and rapidly expanding AI community. General awareness of the Australian AI research community has been growing slowly for some time. AI was once considered a bit esoteric -- the domain of an almost lunatic fringe- but the large government -backed programs overseas, as well as an appreciation of the significance of AI products and potential impact on the community, have led to a reassessment of this image and to concerted attempt to discover how Australia is to contribute to the world AI research effort and hoe the country is to benefit from it. What we have seen as result is not an incremental creep of AI awareness in Australia but a quantum leap with significant industry and government support. The first systematic study of the Australian AI effort was undertaken by the Australian Department of Science (DOS) in 1986. The study took as its base the long-running research report Artificial Intelligence in Australia (AIIA), produced by John Debenham (1986). The picture that emerged is interesting. AI researchers are well qualified, undertaking research at the leading edge in their fields, and have significant potential to develop further. The results of this study were published by DOS in the Handbook of Research and Researchers in Artificial Intelligence in Australia (Department of Science1986). This article is based on key findings from the study and on additional information gained through meeting and talking with researchers and research groups.
OPGEN: The Evolution of an Expert System for Process Planning
Freedman, Roy S., Frail, Robert P.
Initial Development Approach In the following eight subsections, we present a brief discussion of methodology for expert system development, selection of problem and tools, knowledge engineering and prototype implementation, operational feasibility, and the actual development of a working prototype of a process planning expert system. Methodology for Expert System Development Expert systems require a software development methodology that differs in some respects from those methodologies used for conventional systems. Most knowledge-based development methodologies used by organizations experienced in building expert systems are similar in that they concentrate on the early (feasibility) stages of a project. Very little has been published on the later stages, which are concerned with expert system delivery, integration, and maintenance. During the development of OPGEN, we incorporated the lessons learned in these early stages and revised our original approach to provide for integration and maintenance. Most expert system development methodologies are a variation on the following theme, which paraphrases Haycs-Roth (1985): (1) expert system technology is determined to be relevant to a product; (2) management provides an opportunity for action; (3) a preliminary business application is assembled; (4) a knowledge engineering consultant verifies the opportunity; (5) a knowledge engineering project team is formed and assesses the knowledge; (6) the knowledge engineering project manager plans the project; (7) the user organization Figure 2 OPGEN bzput Circuit Layout Diagram.
Recent and Current Artificial Intelligence Research in the Department of Computer Science SUNY at Buffalo
Hardt, Shoshana L., Rapaport, William J.
The interpretation of images of postal mail pieces is The Vision Group the domain of this investigation. Our efforts have included It is becoming increasingly important for vision researchers the development of various operators for visual data processing in diverse fields to interact, and the Vision Group at SUNY and image segmentation. The invocation of these Buffalo was formed to facilitate that interaction Current routines and the interpretation of the information they return membership includes 25 faculty and 25 students from 10 is determined by a control structure that uses a variant departments (computer science, electrical and computer of relaxation combined with a rule-based methodology.
Letters to the Editor
Nilsson, Nils J., Stefik, Mark, Partridge, Derek, Lanning, Stan
He then proved that In addition, I noticed that John McCarthy was snapping network representations (such as that of the brain) cannot freely with his camera at the workshop. He may have some possibly exhibit intelligence-tapes, as in Turing Machines, amusing illustrations of the unlikely events rec0rded.l
AAAI-86: Experimenting with a New Conference Format
Mazzetti, Claudia, Tenenbaum, Jay Martin, Brachman, Ronald J., Genesereth, Michael, Stefik, Mark
During the balmy summer of 1980, about 800 AI researchers pose of the new format, the Committee's recommendation, met on the Stanford campus to hold the first and some expanded ways for members to participate in the AAAI conference. The conference program had no more conference this year. For many of Conference Goals those attendees, it was a special, unique opportunity to have deep colleagial interactions in a very comfortable setting. The most radical change that was considered, but not adopted, was the division of the science and engineering interests into two separate conferences at different times of Even the first national conference, however, was more the year. Many Council members expressed concern that than a gathering of researchers.
Starting a Knowledge Engineering Project: A Step-By-Step Approach
Freiling, Michael, Alexande, Jim, Messick, Steve, Rehfuss, Stefe, Shulman, Sherri
One reason is that the requirements-oriented methods and intuitions learned in the development of other types of software do not carry over well to the knowledge engineering task. Another reason is that methodologies for developing expert systems by extracting, representing, and manipulating an expert's knowledge have been slow in coming. At Tektronix, we have been using step-by-step approach to prototyping expert systems for over two years now. This methodology has helped us collect the knowledge necessary to implement several prototype knowledge-based systems, including a troubleshooting assistant for the Tektronix FG-502 function generator and an operator's assistant for a wave solder machine.