1. Rollerslam “Filtering” Mechanism

2. Main Idea Problem: Avoid network overload when agents need to receive excessive informations about the environment. Solution: –The agents decides which flux object is he aware of. –“A voluntarily partially observable world”

3. Old Top Level Component Realization Service View > Simulation Infrastructure > Display > GameDisplay > SimulationAdmin > ControlPanel > Agent * > Player > Referee > GamePhysics > agents

4. New Top Level Component Realization Service View > Simulation Infrastructure > Display > GameDisplay > SimulationAdmin > ControlPanel > Agent * > Player > Referee > GamePhysics > agents > Agent > PercepFilter > Filter >

5. Filter Component

6. Specification Service View > Agent > Filter > Agent -------------------------------------------------------- + getAgentID() : Integer + sendActions(p:Message[0..*]) + receivePercepts() : Message[0..*] + getSimulationState() : SimulationState > PerceptFilter -------------------------------------------------------- + setDesiredFluxObjects(fo : FluxObject[*])

7. Details The “Agent” interface just delegates the implementation of its method to the interface realized by the infrastructure –Exception: The “receivePercepts” strips down the messages sent by the infrastructure, removing the unwanted objects How does this solve the problem? –If the “Filter” component resides on the same machine as the Infrastructure and the agents reside on their machines, the complete model is just transfered between component in the same machine, whereas just the desired subset of the world needs to be transfered between different machines.