Computational Autonomy. Broadening the Focus Computational Autonomy is seen as a way of enlarging the narrow focus of a program, which carries out one.

Slides:



Advertisements
Similar presentations
WARWICK MBA IB8020: Organisational Behaviour Lesson 4: Attributes of Groups Lesson 5: Group Decision Making.
Advertisements

ARCHITECTURES FOR ARTIFICIAL INTELLIGENCE SYSTEMS
Some questions o What are the appropriate control philosophies for Complex Manufacturing systems? Why????Holonic Manufacturing system o Is Object -Oriented.
BOUNDARY SPANNING AND TEAM LEADERSHIP
JADE: The Bully Algorithm. Problem Context of distributed computing Problem of leader election: leader election is the process of designating a single.
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright  Rational Software, all rights reserved 1/18 Use Case Analysis – continued Control Classes.
Chapter 11 EFFECTIVE WORK GROUPS AND TEAMS. CHAPTER 11 Effective Work Groups and Teams Copyright © 2002 Prentice-Hall 2.
From Words to Knowledge ORION Active Structure. ORION Active Structure Two Approaches We could separate the process of turning words into knowledge into.
1 Intelligent Agents Software analog to human agents real estate agent, librarian, salesperson Perform tasks individually, or in collaboration Static and.
Orion Philosophy and Rationale. If it really is structure, what sort of structure is it? We are asserting that it is active dynamic undirected structure.
Human Computer Interaction G52HCI
1 Frameworks. 2 Framework Set of cooperating classes/interfaces –Structure essential mechanisms of a problem domain –Programmer can extend framework classes,
Knowledge, Mental Models and HCI. Introduction 4 If we want to –predict learning time –identify “typical” errors –relative ease of performance of tasks.
A Summary of the Article “Intelligence Without Representation” by Rodney A. Brooks (1987) Presented by Dain Finn.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Essentials of interaction diagrams Lecture 23 & 24.
Essentials of interaction diagrams Lecture Outline Collaborations Interaction on collaboration diagrams Sequence diagrams Messages from an object.
Agent-Based Acceptability-Oriented Computing International Symposium on Software Reliability Engineering Fast Abstract by Shana Hyvat.
Intelligent Agents revisited.
Group Processes and Work Teams Chapter Nine. © Copyright Prentice-Hall Group Dynamics Group dynamics focus on the nature of groups – the variables.
Orion Overview. We build an internal model of the world, so we can predict future behaviour - we make the model out of active structure so it is interoperable.
Multiagent Systems: Local Decisions vs. Global Coherence Leen-Kiat Soh, Nobel Khandaker, Adam Eck Computer Science & Engineering University of Nebraska.
Identity Development in Adolescence Samuel R. Mathews, Ph.D. Department of Psychology The University of West Florida.
©Ian Sommerville 2006Critical Systems Slide 1 Critical Systems Engineering l Processes and techniques for developing critical systems.
The Tutoring Session By: Eva Lam. Contents Table of Contents What is a tutor?………..………………………………...3 Introduction..…………………………………………..4 In Other Words………………………………………………..6.
Stages of Second Language Acquisition
IOL National Conference 12 October st Century Team Building Master Class 21st Century Team Building - Bob Larcher.
Advances in Language Design
Software Testing Verification and validation planning Software inspections Software Inspection vs. Testing Automated static analysis Cleanroom software.
Databases From A to Boyce Codd. What is a database? It depends on your point of view. For Manovich, a database is a means of structuring information in.
Qualitative differences in teachers’ approaches to task-based teaching and learning in ESL classrooms International Conference on task-based language teaching’
Some Aspects of Propagation. Operators Are Not Functions Network operators rarely behave as functions - they can have multiple outputs a range can turn.
GRASP Principles. How to Design Objects The hard step: moving from analysis to design How to do it? –Design principles (Larman: “patterns”) – an attempt.
1.eCognition Overview. 1 eCognition eCognition is a knowledge utilisation platform based on Active Knowledge Network technology eCognition covers the.
HCIMA Unit 3 The Internet Revolution and Electronic Tools Next slide.
VCE Learning. To unpack the challenge of enhancing the quality of VCE learning What does the student need to know about how to interpret the task ? Ho.
Active Structure A + B = C. Logic and Numbers IF A + B = C THEN D + E = F.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 2Slide 1 Chapter 2 Computer-Based System Engineering As modified by Randy Smith.
Learning objectives By the end of this lecture you should be able to:  have a well-earned rest! Ch 24 Beyond the second semester.
Goals  Correlation/dependency: The storing of correlations and dependencies  Integration: Methodology for integrating correlated risk distributions into.
Databases From A to Boyce Codd. What is a database? It depends on your point of view. For Manovich, a database is a means of structuring information in.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Software Verification, Validation and Testing.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
MODULE 13:. Principles of Information Systems Analysis & DesignDesign © 2009 by Dr. Martin Schedlbauer Visualizing Scenarios UML offers three diagrams.
MOTIVATION Process Theories of Motivation. “Process theories attempt to identify the relationship among the dynamic variables which make up motivation.
Modularity, Upgradeability and Openness – How to meet Requirements in a Family of Systems Peter Henderson University of Southampton.
Week 2 Introduction to Data Modelling
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Fall 2002 SJSU -- CMPE Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department – RM# College of Engineering San José.
Lecture VIII: Software Architecture
OOD OO Design. OOD-2 OO Development Requirements Use case analysis OO Analysis –Models from the domain and application OO Design –Mapping of model.
Motivation Expectancy Theory of Work Motivation (Jones and George 289) Expectancy Theory Formulated by Victor H. Vroom in the 1960’s. States that motivation.
What is cohesion? What different types of cohesion are there? 4.3- Cohesion.
SM Sec.1 Dated 13/11/10 STRATEGY & STRUCTURE Group 3.
1 Usability Analysis n Why Analyze n Types of Usability Analysis n Human Subjects Research n Project 3: Heuristic Evaluation.
ECognition Model Components. 2. eCognition Model Components1 Model Components Variables and Constants Operators and Functions Links Logical States Messages.
Tupai Business Systems Predictive Models using eCognition TM.
ITEC1301 Object-Oriented Systems Construction Lecture Notes #4 1.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 2Slide 1 Chapter2: Systems Engineering l Designing, implementing, deploying and operating.
Done by Fazlun Satya Saradhi. INTRODUCTION The main concept is to use different types of agent models which would help create a better dynamic and adaptive.
Rationality and Power: the “gap in the middle” in ICT
Parent Education Evening Learning at WPPS
Information exchanges between router agents
Web *.0 ? Combining peer production and peer-to-peer systems
Sports Psychology.
Introduction There are many situations in which we might use replicated data Let’s look at another, different one And design a system to work well in that.
Chapter 13 Quality Management
The Habits of Highly Connected Learners
Presentation transcript:

Computational Autonomy

Broadening the Focus Computational Autonomy is seen as a way of enlarging the narrow focus of a program, which carries out one instruction at a time. Instead of a program, there are many separate and autonomous agents. Each agent is assigned one or more relatively atomic roles, and a reward/punishment structure is used to ensure the agent “does what is required”. With these agents cooperating with each other, it is thought that problems in complex domains will become more tractable.

Assumptions There are several large assumptions present in the foregoing: Autonomy of action is desirable A complex interaction is reducible to independent tasks The agents communicate with each other, but only with messages at the beginning and end of their tasks A stable and static punishment/reward structure can be devised for each agent

Autonomy of Action Project Management is all about limiting autonomy of action on the jobsite, because, untrammeled, it results in chaos. Higher level control is exercised, to ensure a smooth interaction among all the different crafts. This can’t be exercised at the level of each craft, because not one of them knows what the overall plan is.

A Complex Interaction eCommerce is often given as an example where autonomy is required. If we look at the interaction, Manufacturing in Organisation 1 gives Purchaser a requirement. The product may be available, or the Supplier may need to modify what they offer, or Manufacturing may need to modify their specification. Control is shifting back and forth, based on communication of a complex object. This is Distributed Control, not Autonomy

Punishment/Reward Structure As any parent will tell you, it is very hard to devise a successful set of punishments and rewards, particularly if the agent can learn how to avoid one and maximise the other. Simply put, a static structure won’t work. An example is drink-driving.

Drink Driving People drive while drunk, with disastrous consequences. Fines are increased, to stop the practice. The people who can’t afford the fines don’t pay them, the people who can afford them don’t feel constrained by them. Potential loss of licence is introduced. People drive while unlicensed. The only effective deterrent is immediate incarceration. This is typical of a static punishment structure attempting to control behaviour of autonomous agents.

Alternative Approach Rather than autonomy as a direct goal, it may be better to pursue distributed control and complex messaging, with computational autonomy emerging as an end-product. We show a network of quasi-autonomous operators.

A Simple Operator The PLUS operator determines its response based on the state of its connections - it can propagate a state, a range or a singular value down any connection, including one that functioned as an input. The operator may appear to be locked in a static framework.

Self Modification X =+ List Link A% X =+ B C D B=9 C=3 X=5 D=-7 + The statement X = SUM(List) requires that the PLUS operator have as many connections as the list has members - a dynamic self-modification property has been introduced.

The quake struck The PARSE operators here analyse their local environment, and then change the structure, destroying themselves in the process, allowing a more complex structure to emerge. Punishment/reward is irrelevant if altruism is required. Information Extraction

A Complex System Information Extraction relies on knowledge in the area, and the knowledge is enhanced by the information extracted. This means that processes interact - grammar helping to resolve POS tags, semantics helping to resolve grammar, and so on. Distributed control and complex messaging are essential for complex applications.

Learning If we are to justify the label of autonomy for a system, then we should expect it to learn from its interactions. The diagram shows operators connected together that store occurrences in related dimensions, then make those occurrences available as probability distributions, relying on the ability of the network to propagate ranges.

Autonomy Autonomy is a natural result of building systems with uncommitted structure, distributed control and complex messaging. These same attributes are needed for many applications in operations, engineering, finance, management.