The impact of adversarial knowledge on adversarial planning in perimeter patrol

Research output: Contribution to journalArticlepeer-review

78 Scopus citations

Abstract

This paper considers the problem of multi-robot patrolling around a closed area, in the presence of an adversary trying to penetrate the area. Previous work on planning in similar adversarial environments addressed worst-case set- tings, in which the adversary has full knowledge of the de- fending robots. It was shown that non deterministic algorithms may be effectively used to maximize the chances of blocking such a full-knowledge opponent, and such algorithms guarantee a "lower bound" to the performance of the team. However, an open question remains as to the impact of the knowledge of the opponent on the performance of the robots. This paper explores this question in depth and provides theoretical results, supported by extensive experiments with 68 human subjects concerning the compatibility of algorithms to the extent of information possessed by the subjects. First, we analytically examine the case of a zero-knowledge opponent-a different extreme-and show that surprisingly, this seemingly best-case scenario (from the point of view of defending robots) is optimally addressed by a deterministic, non-randomizing patrol. Moreover, we show empirically that an optimal algorithm for the full-knowledge opponent fails miserably in this case. We then address the case in which the adversary gained partial information, pro- pose the Combine algorithm that maximizes the expected probability of penetration detection along with minimizing the deviation between the probabilities of penetration detection along the perimeter, and support the performance of this algorithm in the experiments. Copyright © 2008, Intemational Foundation for Autonomous Agents and Multiagent Systems. All rights reserved.

Fingerprint

Dive into the research topics of 'The impact of adversarial knowledge on adversarial planning in perimeter patrol'. Together they form a unique fingerprint.

Cite this