Laelaps AI

PRoMiSe: Persistent Multi-Robot Monitoring
Sim-to-Real-to-Field

Alessio Salvatore · Juan de los Rios · David Rytz · Maria Stamatopoulou

Laelaps AI · Zürich

Abstract

Persistent multi-robot patrolling is a complex real-world problem, requiring repeated observation of an environment while adapting to changes in layout and team composition. We present PRoMiSe, a multi-agent reinforcement learning policy for visibility-based persistent monitoring that commands body-frame velocities, with no patrol graph, task allocation or planner in the control loop. It combines a compact egocentric idleness summary and lidar ranges with attention over a variable number of teammates and recurrent temporal reasoning. A single policy transfers without fine-tuning to unseen simulated maps and teams of up to sixteen robots, and runs unmodified on Unitree Go2 quadrupeds at three physical sites. Matched indoor experiments with one to four robots show cumulative coverage within 0.6 percentage points of simulation. Outdoor deployments with two robots demonstrate coordinated patrolling in previously unseen environments, including an industrial site eight times the average training-map area. These results provide evidence of sim-to-real-to-field transfer for persistent multi-robot monitoring across layouts, scales, and team sizes.

Method

Approach

PRoMiSe architecture: local observation and team tokens feed an MLP, GRU and actor head; a centralized critic is used only during training
Every robot runs the same recurrent actor on its own lidar scan, an egocentric idleness summary and a token per teammate, and outputs body-frame velocities directly. The centralized critic is used during training only and discarded at deployment, so execution is fully decentralized.
Observation

One shared policy, local inputs

Every robot runs the same weights on its own pose and heading, a sixteen-ray lidar scan, and an eight-sector histogram of how stale the space around it is, in its own body frame. No patrol graph, no task allocation, no assigned region.

Team encoder

Attention over a variable-size team

Teammates arrive as an unordered set of tokens carrying distance, bearing and relative heading. Cross-attention pools them into a fixed-width embedding, invariant to team size and ordering. That is what lets a policy trained with four robots run with sixteen.

Memory

Recurrence for what is already covered

A GRU carries what one observation cannot: where the robot came from and which regions it has already refreshed. Ablating it costs nothing at one robot and costs at every larger team, so the gain is coordination, not capacity.

Training

Centralized critic, decentralized execution

The critic sees the full team state during training only. Each robot then acts on what it senses and on the tokens its teammates broadcast, so a lost robot or a delayed message degrades the team gradually instead of breaking an assignment.

Rollouts

PRoMiSe in action

Every clip below plays at ten times real speed.

Training in simulation

Training runs on procedurally generated room layouts with one to four robots. Cells darken as they are observed and pale out as they go stale; the trail behind each robot is its recent path.

1 robot
Training rollout, one robot
2 robots
Training rollout, two robots
3 robots
Training rollout, three robots
4 robots
Training rollout, four robots
The training range, one to four robots on the same procedural layout. Mean idleness is reported live in each panel header.

Generalization across team size

Training only ever sees one to four robots. The same checkpoint then runs with eight, twelve and sixteen without retraining, re-tuning or any reassignment: the team simply re-partitions the floor. Going from one to sixteen robots cuts average idleness from 304.3 s to 25.8 s and raises final coverage from 91.6% to 99.7%, so performance keeps improving beyond the training range.

8 robots
Eight robots on the procedural layout
12 robots
Twelve robots on the procedural layout
16 robots
Sixteen robots on the procedural layout
Every team size here is beyond anything seen in training, on the same layout as the row above.

Generalization across layouts

A single set of weights runs on layouts that share no structure with one another: open atria, rings, corridors, spokes, warehouse aisles, a parking lot, and real customer sites. All twelve are held out from training, all are patrolled by the same four-robot checkpoint.

Atrium layout
Office layout
Warehouse layout
Parking lot layout
Circular ring layout
Rectangular ring layout
Half ring layout
Spokes layout
Circular layout with obstacles
Barbell layout
Rotated layout
Customer site layout
Twelve held-out layouts, four robots each. Difficulty is visible in the reported idleness: a ring closes in 7.4 s, a long thin site takes 74.0 s with the same policy.

On the field: the office, one team at a time

The same checkpoint drives physical Go2 quadrupeds in an office it has never seen. Nothing changes between these runs except how many robots are switched on.

3 robots
Office patrol, three robots
3 robots · recorded idleness
Recorded idleness map of the three-robot office deployment
4 robots
Office patrol, four robots
4 robots · recorded idleness
Recorded idleness map of the four-robot office deployment
Across one to four robots in the laboratory, final coverage on hardware stays within one percentage point of matched simulation.

Real-world deployments

The same checkpoint runs on physical Go2 quadrupeds at two outdoor sites, neither of them seen in training. The industrial test site is eight times the average training map.

Industrial test site
Two quadrupeds patrolling an industrial test site
Industrial test site · recorded idleness
Recorded idleness map of the industrial site deployment
Parking lot
Two quadrupeds patrolling a parking lot, seen from above
Parking lot · recorded idleness
Recorded idleness map of the parking lot deployment
Camera on the left, the idleness field rebuilt from the recorded poses on the right, cell by cell as the two robots sweep the site. Top: a seven-minute patrol of the industrial site. Bottom: the parking lot, where coverage rises from 70.0% to 95.4% and mean idleness falls from 155.3 s to 69.0 s over four minutes.
Results

Key results

91.5%idleness drop from one to sixteen robots
99.7%final coverage at sixteen robots
16robots at deployment, four in training
0.6 ppcoverage gap, hardware against simulation
Cite

BibTeX

@inproceedings{promise2027,
  title     = {PRoMiSe: Persistent Multi-Robot Monitoring Sim-to-Real-to-Field},
  author    = {Salvatore, Alessio and de los Rios, Juan and Rytz, David and Stamatopoulou, Maria},
  booktitle = {Under review},
  year      = {2027}
}