Lab D: Safe Multi-Embodied Agents
Agent type: Multiple embodied agents — three connected vehicles and a roadside coordinator
Goal
Coordinate three simulated vehicles approaching a shared intersection from different directions. A Roadside Unit (RSU) acts as the intersection’s coordinator and grants permission to enter, while SUMO simulates the motion and a Python message network introduces delay, loss, and duplication.
The central question is when the next car may enter if the previous car has not confirmed that it is clear. A timer expiring is not evidence that the physical intersection is empty. You compare independent driving, a timer-based lease policy, and a reservation protocol that waits for a matching release.
Coordination architecture
RSU stands for Roadside Unit: the simulated roadside infrastructure agent that queues vehicles’ crossing requests, issues grants, and tracks the active reservation. It relies on delivered messages and its reservation state; it cannot see the road. Each car observes its own state. The evaluation monitor sees all vehicle positions for metrics only and never influences a decision. Adapted from the project’s coordination protocol.
Focus
- Exclusive reservations for a shared physical conflict zone
- Grant identity, request IDs, reservation epochs, and entry deadlines
- Retransmission and duplicate handling under communication failures
- Separate measures of exclusion violations, collisions, waiting, and completion
What you will do
- Run the supplied
independentandleasebaselines and inspect their browser replays, event logs, and occupancy timelines. - Complete
choose_request,grant_is_usable, andrelease_matchesincavlab/policies.pyto implement therobustprotocol checks. - Compare the three policies across
nominal,slow_car,delayed_grant, andlossy: twelve controlled runs in total. - Trace a failure from message timing to entry decisions and vehicle motion. Explain why permanent loss of a release can prevent progress even while the coordinator preserves the reservation.
- For the CSE 598 extension, vary the grant’s start window under a fixed message delay and analyze expired grants, waiting, and completion.
Learning outcomes
By the end of this lab, you should be able to:
- explain why an entry deadline does not end an occupied reservation;
- validate grants and releases while rejecting stale or mismatched messages;
- distinguish a conservative exclusion violation from a geometric collision;
- assess progress together with safety observations; and
- state the assumptions behind the protocol, including truthful clearance reports, trusted message identities, and a shared simulation clock.
Message identities are trusted simulation labels, not cryptographic
authentication. The default planner is a replaceable rule-based component;
live model inference is outside the graded workflow. All experiments run on a
CPU, and each run produces a self-contained replay.html that opens directly
in a browser.
Project repository
Use the public embodied-ai-lab/safe-multi-embodied-agents template to create your group’s private repository. Choose native Ubuntu, native macOS, or ASU Sol with Apptainer; no GPU or model download is required.