Signal

MERIDIAN / LIVE TRAFFIC

Market rush

Paused

Traffic corridorChoose a vehicle to inspect its latest decision. Cyan outlines indicate a request in flight.

Cars

Scooters

Rickshaws

Buses

On the road

27vehicles

Driver choices

00.0 per second

Lane changes

00 vehicles through

API latency

—average round trip

Cyan outline = deciding

Choose a vehicle to inspect

Inside Signal

Each vehicle has its own view of the road: nearby drivers, available gaps, and the next lane closure.

  1. Decisions chooses. While playing, Signal targets two real API requests per second, with up to four drivers per request. Each driver gets an independent choice.
  2. The street responds. Returned choices control acceleration, yielding, and lane changes. Local physics checks the current gap before moving a vehicle.
  3. The feed keeps the receipt. Inspect request IDs, timings, model outputs, and whether each choice could be applied. A request can return several driver choices; the counters show both.

Each run ends after two minutes of playing time. Pausing stops requests and preserves the remaining time. Traffic also pauses when this tab is hidden. This is a stylized traffic simulation; pedestrians and buildings are scenery.

Explore the original signal controller