Agent Surgery: Controlled Mutations in Multi-Agent Systems, Slides of Multiagent Systems

The concept of agent surgery, a controlled mutation process for multi-agent systems. It explores the limitations of randomly mutating agents and introduces the concept of agent surgery as a solution. Problems related to agent surgery, primitive operations, invariants, and properties. It also mentions applications such as step-by-step agent build-up, achieving larger agendas, and garbage collection.

Typology: Slides

2012/2013

Uploaded on 04/30/2013

aradhana
aradhana 🇮🇳

4.6

(8)

119 documents

1 / 12

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Managing mutability in agents
Docsity.com
pf3
pf4
pf5
pf8
pf9
pfa

Partial preview of the text

Download Agent Surgery: Controlled Mutations in Multi-Agent Systems and more Slides Multiagent Systems in PDF only on Docsity!

Managing mutability in agents

Randomly mutating agents

  • While randomly mutating agents are possible, their applications are limited.
  • It is difficult to make them follow their original agenda.
  • Limited random mutation, however, can lead to interesting possibilities: - Genetic algorithms and evolutionary programming - Tabu search
  • Problems:
    • Compiled code does not make a good chromosome (in the genetic algorithms sense). Crossover and mutation in compiled code usually lead to gibberish.
    • The agents fitness in a multiagent system is a complex parameter depending on the other agents. It is very difficult to set up good training runs.

Agent surgery in Bond

  • Agent surgery in Bond are essentially operations performed on the multi-agent plane.
  • Surgical operations are performed by “surgical blueprint scripts”.
  • The agent (usually) does not have to be stopped.

Problems in agent surgery

  • When do we need to perform a surgical operation on the agent?
  • What kind of operation do we need to perform?
  • What kind of guarantees can we offer about the agent after the surgical operation?
  • How can the surgical operation be embedded in the specification?

Invariants

  • Invariants are properties of agents which are maintained across surgical operations.
  • Our analysis technique will be to prove invariants for primitive operations, and then prove invariants for larger surgical operations by decomposing them into primitive operations.
  • Example of invariants:
    • Being successful.
    • Achieving some subset of the agenda.
    • Having the agenda achievable.

Successful and failed runs

  • We will distinguish between SUCCESS, FAILURE and other transitions in the multiplane state machine - We assume SUCCESS means that local goal of the strategy was achieved - We assume that FAILURE means that the local goal failed (but the agenda may be still achievable, for instance, by retrying) - Other transitions mean “choices” or “decisions”.
  • A run of the agent is an ordered series of events and actions
    • At a courser granularity level, we can see the run as a series of states and transitions.
  • A successful run is a run without a FAILURE transition.
  • A failed run involves at least one FAILURE transition or an exit code for which there was no transition in the state machine.

Reasoning about agent

surgery

  • Property 1:
    • Adding a new state to the agent does not change the behaviour of the agent.
  • Property 2:
    • Adding a new transition to the agent does not change the behaviour of the agent in successful runs.
    • It might turn some failed runs into successful runs.
  • Property 3:
    • If we add a new plane to an agent and the output set of the strategies in the new plane is disjoint from the input set of the existing strategies, for all cases where the agent achieved its agenda in its original state will achieve it in its modified state as well (maintains the achievability of the agenda)
  • Corrolary 3.
    • Adding a plane with a single dummy strategy maintains the achievability of the agenda.

Reasoning about agent surgery

(cont’d)

  • Property 4:
    • Removing FAILURE transitions does not affect successful runs.
  • Property 5:
    • Removing states unreachable from the current state of the agent, or removing transitions going to and from these states does not affect the behaviour of the agent.