Industry · 03 / Autonomous vehicles

Reconstruct every mile, frame by frame

LiDAR, camera, IMU and brake-by-wire on one timeline — replayable against ground truth, from test track to public road.

100 Hzvehicle bus beside 10 Hz lidar, in sync
Scene-trueevery disengagement replayable as recorded
Road → simone pipeline from log to simulation
01 / Phloem for autonomy

Every disengagement, explained

When the scene, the signals and the stack’s decisions live on one playhead, triage stops being archaeology.

C/01

Scrub the whole scene

Point cloud, camera, IMU and actuation snap to the same instant — with detections and masks overlaid on the frame.

C/02

Replay the road into sim

Feed the exact recorded scene into simulation and run the new stack against it before it drives again.

C/03

Mine the fleet for edge cases

Query every mile for the same scenario signature and turn one incident into a coverage set.

02 / Lifecycle

One platform, first prototype to fleet

The record built in development carries into validation and operations — nothing starts from scratch.

S/01

Develop

  • Stream track testing and shadow-mode logs into one timeline.
  • Compare stack versions on identical scenes, decision by decision.
  • Keep sim runs and road data in the same record.
S/02

Validate

  • Run scenario suites against every release candidate.
  • Codify safety criteria once; every mile is scored against them.
  • Build regression libraries from real disengagements.
S/03

Operate

  • Capture the deployed fleet continuously, within bandwidth budgets.
  • Surface off-nominal behaviour as it happens, fleet-wide.
  • Trend sensor degradation before it becomes a fault.
03 / One timeline

What a run looks like in Phloem

A shadow-mode drive as it lands: point cloud, forward camera, IMU and the vehicle bus, already on one playhead.

Route 12 · Shadow vehicle · recordingcloud · in sync VEH-07 · Live
41:05elapsed
5,412Kmessages
9streams
12.6 GBon disk
lidar/lidar/points10 Hz
video/cam/front30 fps
imu/imu/accel_z9.81 m/s²
bus/can/brake_bar34 bar

The scene, reconstructedThe point cloud, the camera frame, and what the stack believed — detections and masks overlaid — scrubbed together at the moment of disengagement.

04 / Ecosystem

Native to the AV stack

First-class ingest for the formats, protocols and buses this work already runs on — and the wider ecosystem behind them.

+ anything else with an SDK, a topic, or a recorded log.

05 / Outcomes

What teams get back

Minutes
Per disengagement

Triage opens on the reconstructed scene, not on a directory of logs from three recorders.

1 pipeline
Road to sim

The same recording that explains an incident becomes the scenario that prevents the next one.

06 / End of run

Miles that make the stack smarter

Every mile driven is training signal. Keep all of it, in sync, in one place.

← PrevRockets & launch Next →Drones & UAS