Artificial Intelligence and Lisp Lecture 9 Reasoning about Actions and Planning, II LiU Course TDDC65 Autumn Semester, 2010 http://www.ida.liu.se/ext/TDDC65/

Slides:



Advertisements
Similar presentations
REVIEW : Planning To make your thinking more concrete, use a real problem to ground your discussion. –Develop a plan for a person who is getting out of.
Advertisements

Language for planning problems
CSCI 115 Chapter 6 Order Relations and Structures.
1 Turing Machines and Equivalent Models Section 13.2 The Church-Turing Thesis.
1 Constraint operations: Simplification, Optimization and Implication.
Lecture 8: Three-Level Architectures CS 344R: Robotics Benjamin Kuipers.
The Ramification and Qualification Problems in Temporal Databases Nikos Papadakis & Dimitris Plexousakis University of Crete and.
1.2 Row Reduction and Echelon Forms
Artificial Intelligence 2005/06
Introduction to Computability Theory
Planning Copyright, 1996 © Dale Carnegie & Associates, Inc. Chapter 11.
Temporal Specification Chris Patel Vinay Viswanathan.
A Preliminary Study on Reasoning About Causes Pedro Cabalar AI Lab., Dept. of Computer Science University of Corunna, SPAIN.
Planning Copyright, 1996 © Dale Carnegie & Associates, Inc. Chapter 11.
Artificial Intelligence and Lisp Lecture 12 Finish "Programming in Lisp, II" + Lab 5 a-b + Review and Synthesis of the Course LiU Course TDDC65 Autumn.
Artificial Intelligence and Lisp Lecture 5 LiU Course TDDC65 Autumn Semester, 2010
CS5371 Theory of Computation Lecture 8: Automata Theory VI (PDA, PDA = CFG)
Maria-Cristina Marinescu Martin Rinard Laboratory for Computer Science Massachusetts Institute of Technology A Synthesis Algorithm for Modular Design of.
CS1Q Computer Systems Lecture 8
Slide 1 Propositional Definite Clause Logic: Syntax, Semantics and Bottom-up Proofs Jim Little UBC CS 322 – CSP October 20, 2014.
An Ontological Framework for Web Service Processes By Claus Pahl and Ronan Barrett.
Dale Roberts 1 Program Control - Algorithms Department of Computer and Information Science, School of Science, IUPUI CSCI N305.
Laws of concurrent design Tony Hoare Microsoft ResearchCambridge FMCAD October.
Automated Reasoning Early AI explored how to automated several reasoning tasks – these were solved by what we might call weak problem solving methods as.
Course14 Dynamic Vision. Biological vision can cope with changing world Moving and changing objects Change illumination Change View-point.
Artificial Intelligence and Lisp Lecture 9 Reasoning about Actions and Planning, II LiU Course TDDC65 Autumn Semester, 2010
Condition Testing. Condition testing is a test case design method that exercises the logical conditions contained in a program module. A simple condition.
EEL 5937 The Bond Agent System (1) EEL 5937 Multi Agent Systems Lecture 8, Jan 30, 2003 Lotzi Bölöni.
1 Lecture 3 The Languages of K, T, B and S4. 2 Last time we extended the language PC to the language S5 by adding two new symbols ‘□’ (for ‘It is necessary.
Artificial Intelligence Knowledge Representation.
1 Proving Properties of Recursive List Functions CS 270 Math Foundations of CS Jeremy Johnson.
Artificial Intelligence and Lisp #8 State-space Characterization of Actions Algorithmic Planning.
Proof And Strategies Chapter 2. Lecturer: Amani Mahajoub Omer Department of Computer Science and Software Engineering Discrete Structures Definition Discrete.
Visual Basic 2010 How to Program © by Pearson Education, Inc. All Rights Reserved.-Edited By Maysoon Al-Duwais1.
Artificial Intelligence and Lisp Lecture 6 LiU Course TDDC65 Autumn Semester,
COP Introduction to Database Structures
Logical Database Design and the Rational Model
Introduction to Logic for Artificial Intelligence Lecture 2
Artificial Intelligence and Lisp #10
Artificial Intelligence and Lisp #3
Chapter 2: Simplification, Optimization and Implication
Chapter - 12 GRAPH MATRICES AND APPLICATIONS.
Condition Testing.
Evolution strategies and genetic programming
Input Space Partition Testing CS 4501 / 6501 Software Testing
Chapter 9 Structuring System Requirements: Logic Modeling
Timing Model Start Simulation Delay Update Signals Execute Processes
Artificial Intelligence and Lisp Lecture 5 LiU Course TDDC65 Autumn Semester,
Artificial Intelligence and Lisp Lecture 13 Additional Topics in Artificial Intelligence LiU Course TDDC65 Autumn Semester,
Chapter 7: Beyond Definite Knowledge
Programming Fundamentals
Hidden Markov Models Part 2: Algorithms
Chapter 9 Structuring System Requirements: Logic Modeling
EECS 498 Introduction to Distributed Systems Fall 2017
Chapter 9 Structuring System Requirements: Logic Modeling
Linear Equations in Linear Algebra
Metatheorems Computational Logic Lecture 8
Department of Computer Science
Axiomatic Semantics Will consider axiomatic semantics (A.S.) of IMP:
ECE 352 Digital System Fundamentals
Computer Science cpsc322, Lecture 20
This Lecture Substitution model
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 9 Structuring System Requirements: Logic Modeling
Independence and Counting
Independence and Counting
Independence and Counting
Linear Equations in Linear Algebra
Logical Agents Prof. Dr. Widodo Budiharto 2018
Presentation transcript:

Artificial Intelligence and Lisp Lecture 9 Reasoning about Actions and Planning, II LiU Course TDDC65 Autumn Semester, 2010 http://www.ida.liu.se/ext/TDDC65/

Schemas for characterizing actions State transition schema (in earlier lecture): one prestate, one poststate Extended state transition schema: allow conditional and nondeterministic actions. Set of prestate/poststate pairs State transition with immediate causation (STIC): direct effects of actions are followed by indirect effects, but still with sequential execution. Indirect effects are “instantaneous” Trajectory set schema (TSS): Actions are characterized by a set of trajectories consisting of two or more partial states. Trajectory of length 2 corresponds to the above. This allows for concurrent actions and actions with extended duration.

Schemas for characterizing actions State transition schema (in earlier lecture): one prestate, one poststate Extended state transition schema: allow conditional and nondeterministic actions. Set of prestate/poststate pairs. This will be considered integrated with STIC (next item). State transition with immediate causation (STIC): direct effects of actions are followed by indirect effects, but still with sequential execution. Indirect effects are “instantaneous” Trajectory set schema (TSS): Actions are characterized by a set of trajectories consisting of two or more partial states. Trajectory of length 2 corresponds to the above. This allows for concurrent actions and actions with extended duration.

State transition with immediate causation (STIC) Replace the use of prest and post functions by atrans function. Example: from {[: agent-has 22]} to {<{[: agent-has 22]} {[: agent-has 21]}> <{[: agent-has 22]} {[: agent-has 23]}> <{[: agent-has 23]} {[: agent-has 22]}> <{[: agent-has 23]} {[: agent-has 24]}> ... } Replace function apply by Apply (Apply play (Apply play {[: agent-has 22]} )) = {{[: agent-has 20]}{[: agent-has 22]}{[: agent-has 24]}} Introduce ficticious action called causation Consider actions to be atomic (no arguments or parameters)

Convergence and stable state Consider .S (Apply causation .S) (Apply causation (Apply causation .S)) (Apply causation (Apply causation (Apply causation .S))) ... and so on If two successive expressions have equal value then we have obtained convergence in a stable state set, written as. (Apply* causation .S) This is the only case that is of interest here. Specify total effects of an action .a as (Apply* causation (Apply .a .s))

Regressive planning with conditional and nondeterministic actions Point of nondeterminism: (atrans a) contains both <s, s'> and <s , s”> where s' and s” are not equal For every combination of a and s that is a point of nondeterminism, select one of the s', s”, etc as the primary one Find a solution to the planning problem using only the primary outcomes in every such point Identify all points in the solution that relies on a primary outcome. Make additional planning in order to have plans for the other outcome(s). If different outcomes have different probability, then choose the most likely one as primary, and consider the other ones in order Some (esp. unlikely) cases may be postponed to execution time.

Progressive planning and conditional plans Progressive planning: start with initial state; build sequences of actions forward until goal state is reached (simple case) More general case requires conditional plans, formed as [soares a1 a2 ... an R] [if c at af] Must R = (Apply an (Apply an-1 (Apply ... (Apply a1 start)...))) Start with [soares start] containing no actions Add actions to soares expression, obtaining [soares a1 a2 ... an an+1 (Apply an+1 R)] Add conditional expression obtaining instead [soares a1 a2 ... an [if c [soares Rt] [soares Rf]] R] where Rt and Rf are complementary subsets of R where the condition c is true or false, respectively

Example of conditional plan [soares a1 a2 ... an [if [= has-money true] [soares buy-food {{[: hungry false][: have-money true]} {[: hungry false][: have-money false]} }] [soares beg-food {{[: hungry false][: have-money false]}} ]] R ] where R is the set of two states above

Progressive planning with immediate causation Regressive planning: may be possible to generalize the use of primary outcome Progressive planning: straightforward

Middle-out planning using islands Method uses the following steps: 1. Choose main action(s) and an order on them 2. Identify likely enabling actions for the first main action, and insert them into the plan 3. Find plan from starting state to first main action, directly or via the chosen enabling actions 4. Repeat 2-3 for steps to later main actions, and to goal Backup: if step 3 fails, then return to an earlier cycle and find another plan.

Logic for characterizing actions Earlier effect rule: (imp (and [existsroad .fr .to] [D .s .t [moveto .o .fr .to]] [H .s (the position of .r) .fr] ) [H .t (the position of .r) .to] ) Easy to use for conditional effects: (imp (and [D .s .t toggle][H .s light on]) [H .t light off] ) (imp (and [D .s .t toggle][H .s light off]) [H .t light on] )

Frame problem and occlusion In order to avoid frame axioms, use PMON axiom: (imp (and [H .s .f .v] [H (succ .s .a) .f .w] [/= .v .w] ) [X .s (succ .s .a) .f] ) together with axioms that imply X for specific actions and specific features. Example. (imp [D .s .t toggle] (and [X .s .t light] (imp [H .s light on][H .t light off]) (imp [H .s light off][H .t light on]) ))

Immediate Causation Rules in Logic Example (imp [D .s .t [toggle .sw]] (and [X .s .t (state .sw)] (imp [H .s (state .sw) on][H .t (state .sw) off]) (imp [H .s (state .sw) off][H .t (state .sw) on]) )) (imp (and [H .s (state .sw) on][controls .sw .lmp]) [H .s (light .lmp) on]) (imp (and [H .s (state .sw) off][controls .sw .lmp]) [H .s (light .lmp) off]) [connected myswitch mylamp]

Occlusion in Causation Rules (imp (and [controls .sw .lmp][X .s .t (state .sw)]) [X .s .t (light .lmp)] ) or - consider (light .lmp) as always occluded, technically speaking

Causation Sequences A:T, B:T -> A:F, B:F A:F, B:F -> A:T, B:F A:T, B:F -> A:F, B:T A:F, B:T -> A:F, B:T This is an example of a back-and-forth sequence The simple translation to causation axiom in logic does not work for such causation structures.

Endstate Description of Causation Basic idea: Characterize the stable states using stable-state axioms; combine them with indirect effect axioms that specify some of the indirect effects. Combine this with a principle of finding the “closest” stable state from the state capturing the stated indirect effects Often define “closest” as “minimal additional change” (called “minimization of change”)