CS344M Autonomous Multiagent Systems Patrick MacAlpine Department - - PowerPoint PPT Presentation

▶
cs344m autonomous multiagent systems
SMART_READER_LITE
LIVE PREVIEW

CS344M Autonomous Multiagent Systems Patrick MacAlpine Department - - PowerPoint PPT Presentation

Aug 27, 2023 35 likes •358 views

CS344M Autonomous Multiagent Systems Patrick MacAlpine Department or Computer Science The University of Texas at Austin Good Afternoon, Colleagues Are there any questions? Patrick MacAlpine Logistics Programming assignment 4 - any

slide-1
SLIDE 1

CS344M Autonomous Multiagent Systems

Patrick MacAlpine Department or Computer Science The University of Texas at Austin

slide-2
SLIDE 2

Good Afternoon, Colleagues

Are there any questions?

Patrick MacAlpine

slide-3
SLIDE 3

Logistics

  • Programming assignment 4 - any questions?

Patrick MacAlpine

slide-4
SLIDE 4

Logistics

  • Programming assignment 4 - any questions?

− 2D or 3D

  • Next week’s readings on RoboCup case studies

Patrick MacAlpine

slide-5
SLIDE 5

Logistics

  • Programming assignment 4 - any questions?

− 2D or 3D

  • Next week’s readings on RoboCup case studies
  • Talks in the department:

− Leif Johnson, PhD Defense, today at 4:30pm (GDC 4.518) − “Redundancy Reduction in Motor Control”

Patrick MacAlpine

slide-6
SLIDE 6

ACL Desiderata

Patrick MacAlpine

slide-7
SLIDE 7

ACL Desiderata

Form: simple, readable, concise, easy to parse and generate, extensible

Patrick MacAlpine

slide-8
SLIDE 8

ACL Desiderata

Form: simple, readable, concise, easy to parse and generate, extensible Content: well-defined primitives, flexible content

Patrick MacAlpine

slide-9
SLIDE 9

ACL Desiderata

Form: simple, readable, concise, easy to parse and generate, extensible Content: well-defined primitives, flexible content Semantics: unambiguous, address location and time

Patrick MacAlpine

slide-10
SLIDE 10

ACL Desiderata

Form: simple, readable, concise, easy to parse and generate, extensible Content: well-defined primitives, flexible content Semantics: unambiguous, address location and time Implementation: efficient, networking issues hidden, amenable to partial implementation

Patrick MacAlpine

slide-11
SLIDE 11

ACL Desiderata

Form: simple, readable, concise, easy to parse and generate, extensible Content: well-defined primitives, flexible content Semantics: unambiguous, address location and time Implementation: efficient, networking issues hidden, amenable to partial implementation Networking: usable on top of existing protocols

Patrick MacAlpine

slide-12
SLIDE 12

ACL Desiderata

Form: simple, readable, concise, easy to parse and generate, extensible Content: well-defined primitives, flexible content Semantics: unambiguous, address location and time Implementation: efficient, networking issues hidden, amenable to partial implementation Networking: usable on top of existing protocols Environment: interoperability with other languages

Patrick MacAlpine

slide-13
SLIDE 13

ACL Desiderata

Form: simple, readable, concise, easy to parse and generate, extensible Content: well-defined primitives, flexible content Semantics: unambiguous, address location and time Implementation: efficient, networking issues hidden, amenable to partial implementation Networking: usable on top of existing protocols Environment: interoperability with other languages Reliability: reliable, secure, authentication possible, error handling

Patrick MacAlpine

slide-14
SLIDE 14

Three-layer organization

  • Content: free-form (domain-dependent)

Patrick MacAlpine

slide-15
SLIDE 15

Three-layer organization

  • Content: free-form (domain-dependent)
  • Communication: who is sending, etc.

Patrick MacAlpine

slide-16
SLIDE 16

Three-layer organization

  • Content: free-form (domain-dependent)
  • Communication: who is sending, etc.
  • Message: performatives and fields (standard)

Patrick MacAlpine

slide-17
SLIDE 17

Three-layer organization

  • Content: free-form (domain-dependent)
  • Communication: who is sending, etc.
  • Message: performatives and fields (standard)

(tell :sender stock-server :content (PRICE IBM 14) :receiver joe :in-reply-to ibm-stock :language LPROLOG :ontology NYSE-TICKS)

Patrick MacAlpine

slide-18
SLIDE 18

Three-layer organization

  • Content: free-form (domain-dependent)
  • Communication: who is sending, etc.
  • Message: performatives and fields (standard)

(tell :sender stock-server :content (PRICE IBM 14) :receiver joe :in-reply-to ibm-stock :language LPROLOG :ontology NYSE-TICKS)

Patrick MacAlpine

slide-19
SLIDE 19

ACLs – Current Landscape

“Languages exist to serve a purpose, namely the communication between willing—and

  • ccasionally

unwilling—participants”

Patrick MacAlpine

slide-20
SLIDE 20

ACLs – Current Landscape

“Languages exist to serve a purpose, namely the communication between willing—and

  • ccasionally

unwilling—participants”

  • There are different options
  • Subtle differences

Patrick MacAlpine

slide-21
SLIDE 21

ACLs – Current Landscape

“Languages exist to serve a purpose, namely the communication between willing—and

  • ccasionally

unwilling—participants”

  • There are different options
  • Subtle differences
  • Why a standard?

− What are the pros and cons?

Patrick MacAlpine

slide-22
SLIDE 22

ACLs – Current Landscape

“Languages exist to serve a purpose, namely the communication between willing—and

  • ccasionally

unwilling—participants”

  • There are different options
  • Subtle differences
  • Why a standard?

− What are the pros and cons?

  • How are they created?

Patrick MacAlpine

slide-23
SLIDE 23

ACLs – Current Landscape

“Languages exist to serve a purpose, namely the communication between willing—and

  • ccasionally

unwilling—participants”

  • There are different options
  • Subtle differences
  • Why a standard?

− What are the pros and cons?

  • How are they created?
  • Sample FIPA applications on resources page

Patrick MacAlpine

slide-24
SLIDE 24

Soccer server communication

  • What is the soccer server communication protocol?

Patrick MacAlpine

slide-25
SLIDE 25

Soccer server communication

  • What is the soccer server communication protocol?

− Only one agent from a team can speak at a time (or at least be heard at a time) − Communication limited to 50 meters − Limited bandwidth

  • How does it relate?

Patrick MacAlpine

slide-26
SLIDE 26

Soccer server communication

  • What is the soccer server communication protocol?

− Only one agent from a team can speak at a time (or at least be heard at a time) − Communication limited to 50 meters − Limited bandwidth

  • How does it relate?
  • Does an ACL make sense in the soccer server? If so, under

what circumstances?

Patrick MacAlpine

slide-27
SLIDE 27

Soccer server communication

  • What is the soccer server communication protocol?

− Only one agent from a team can speak at a time (or at least be heard at a time) − Communication limited to 50 meters − Limited bandwidth

  • How does it relate?
  • Does an ACL make sense in the soccer server? If so, under

what circumstances?

Patrick MacAlpine

slide-28
SLIDE 28

Soccer server communication questions

  • How to have only one agent to speak at a time?

Patrick MacAlpine

slide-29
SLIDE 29

Soccer server communication questions

  • How to have only one agent to speak at a time?
  • How to get the most from limited bandwidth?

Patrick MacAlpine

slide-30
SLIDE 30

Soccer server communication questions

  • How to have only one agent to speak at a time?
  • How to get the most from limited bandwidth?
  • Can opponent agents interfere with messages and if so

how to prevent this?

Patrick MacAlpine

slide-31
SLIDE 31

Soccer server communication questions

  • How to have only one agent to speak at a time?
  • How to get the most from limited bandwidth?
  • Can opponent agents interfere with messages and if so

how to prevent this?

  • What should be communicated?

Patrick MacAlpine

slide-32
SLIDE 32

Soccer server communication questions

  • How to have only one agent to speak at a time?
  • How to get the most from limited bandwidth?
  • Can opponent agents interfere with messages and if so

how to prevent this?

  • What should be communicated?

An example protocol

Patrick MacAlpine