Lagrange v0.6.0: cars and autonomous cars (release notes)

v0.5 added the world around the robot. v0.6 adds road vehicles and the world they drive in:

  • cars with tyres, suspension, brakes, steering and a powertrain;

  • road networks from OpenDRIVE, with traffic and pedestrians on them;

  • OpenSCENARIO scenarios;

  • the sensors of an automated car: radar and a camera sensor model;

  • interfaces for autonomy stacks, Autoware’s included.

Status: released on 2026-10-25 as v0.6.0, at the owner’s request.

Highlights

  • Vehicle dynamics (lagrange_vehicle_dynamics, domains/vehicle_dynamics.md §8).

    • A raycast vehicle on top of either physics backend, at 1 ms.

    • Suspension preloaded at the ride height, with anti-roll bars.

    • MF-Tyre 5.2 tyres from .tir files (pure and combined slip), or linear tyres, with relaxation lengths.

    • Brakes with bias and ABS. Ackermann steering with a rate limit and lag.

    • Electric or engine-map powertrains with an automatic gearbox.

    • The ideal substitute, a kinematic bicycle.

  • Road networks (lagrange_opendrive, formats.md §3.11).

    • Its own OpenDRIVE reader: lines, arcs, spirals, cubic polynomials, elevation, lane sections and offsets, marks, links and junctions.

    • lagrange_opendrive_import writes road surfaces, road marks and RoadLaneAPI_1 lanes.

  • Traffic (lagrange_traffic, domains/traffic.md §8).

    • Kinematic agents, moved by MuJoCo as mocap bodies and by Jolt as kinematic bodies.

    • IDM cars on the lanes, fixed-cycle lights, first-come right of way at junctions.

    • Social-force pedestrians on the sidewalks.

    • --traffic vehicles=N,pedestrians=M,seed=S; the zero substitute.

  • Scenarios (lagrange_openscenario, traffic.md §8.1).

    • Its own runner for a subset of OpenSCENARIO 1.x: parameters, entities, Init, speed and lane-change actions, and time, position, distance, speed and travelled conditions.

    • --scenario FILE.xosc: the scenario’s roads are the world unless --world is given.

  • Sensors (domains/sensors.md §2).

    • Radar by ray launching (RadarAPI_1): echoes from the bodies’ radar cross-section density, one detection per object and range cell, Doppler, SNR by the radar equation.

    • The camera’s sensor model: lens distortion (plumb_bob, equidistant), vignetting, a rotational rolling shutter, exposure with shot and read noise, and auto exposure. camera_info carries the lens.

  • Driving a car over ROS 2. /ackermann_cmd (steering angle and speed) for any road vehicle, beside /cmd_vel.

  • Autoware (lagrange_autoware, docs/guide/autoware.md).

    • A vehicle interface: Autoware’s control, gear and indicator commands and its control-mode request in; velocity, steering, gear and control-mode reports and a ground-truth kinematic state out.

    • It builds only when the Autoware messages are found, since autoware_vehicle_msgs has no Lyrical binary.

  • Schemas.

    • New libraries: vehicle (VehicleAPI_1, WheelAPI_1) and road (RoadLaneAPI_1).

    • New: RadarAPI_1.

    • CameraSensorAPI_1 gains electronRate and vignetting.

    • Robots are named by their top prim, and kinematic bodies are part of the world tables.

  • Samples.

    • The sedan: a URDF, with a USD layer for its vehicle schemas, radar and camera model.

    • The city block: buildings, and OpenDRIVE roads written by city_block_xodr.py.

    • The tyre file generic_205_55R16.tir, the scenario cut_in.xosc, and the profile sedan_city.yaml.

  • Docs.

    • The cars tutorial (docs/guide/tutorial-cars.md, run by tools/ci/tutorial_cars.sh).

    • The Autoware guide.

Acceptance (roadmap §7)

Epic

Acceptance

Status

Evidence

Vehicle dynamics

domains/vehicle_dynamics.md §7

partly met

Braking from 20 m/s within 5 % of v²/(2μg) (3.2 %), steady-state yaw rate within 3 % of the linear bicycle model (1.4 %), gear shifting, ride height (test_vehicle_dynamics); the Magic Formula’s peak, slope and asymptote exact (test_tyre). Owed: a published MF parameter set (no openly licensed one found), the ISO manoeuvres, sloped ground, sim-vs-real

PhysX backend

Backend-agreement tests

not done

Left out by the owner’s v0.6 decision (no new external engines). Vehicles run on MuJoCo and Jolt

OpenDRIVE

Alignment tests

met

Geometry of each road type against closed forms, lanes meeting end to start through links and junctions (test_opendrive). Owed: superelevation, lane heights, objects and signals

OpenSCENARIO

Conformance subset

partly met

The sample cut-in runs to its stop trigger with its events at the times and places its triggers say (test_openscenario, and in the server). Not built: esmini (the owner’s decision), catalogs, the ASAM example scenarios

Traffic

domains/traffic.md §7

partly met

IDM equilibrium, light cycle, flowing traffic with no entry on red, pedestrians on their sidewalks, same seed same tracks (test_traffic). Not built: SUMO (the owner’s decision). Owed: the pedestrian fundamental diagram

Tier 2 sensors

Tier-agreement and camera tests; RTF metric

partly met

Radar: a plate’s RCS within 3 %, Doppler, the detection range by the radar equation (test_radar). Camera model: OpenCV’s lens formulas, the photon-transfer variance within 3 % (EMVA 1288), cos⁴θ, rolling-shutter skew, auto exposure (test_camera_model). Both run on the CPU on every tier; hardware ray-query versions and an RTF metric are owed

Zero-copy ROS output

Copy-count measurement

not done

Owed

Autoware bridge

Demo or documented fallback

met (fallback)

The interface tested against a stand-in for Autoware and the simulator (test_autoware_interface); the documented fallback in docs/guide/autoware.md. Autoware itself is not released for Lyrical and was not run

Sample sedan, city block, tutorials

Tutorials run in CI where no external stack is needed

met, locally

tools/ci/tutorial_cars.sh runs every step; it passes locally (GitHub Actions are disabled)

Known issues

  • Not built, by the owner’s v0.6 decision: the PhysX backend, SUMO co-simulation and esmini.

  • Traffic: the lights are not drawn, pedestrians do not cross roads, no lane changes or priority rules.

  • Radar: no rain attenuation, multipath or ghosts. Ground-plane echoes are dropped as clutter.

  • Camera: no motion blur, no absolute light level (the scene’s brightness is the camera’s electronRate), no colour filter array. SDFormat’s <distortion> and <noise> are not imported.

  • Autoware: the /sensing/... remaps in the launch file follow Autoware’s sample sensor kit and need checking against the kit in use.

  • Scenarios: editing the scene after a scenario has ended logs its end a second time.

  • From earlier releases: Jolt’s drive-wheel slip, Nav2’s occasional start-up discovery failure, rotor strobing in the viewer.

  • Not run while GitHub Actions are disabled: the sanitizer builds and the nightly jobs. Everything else was verified locally with colcon: 882 tests above lagrange_core (with the Autoware messages underlay), 0 failures.

Release checklist

  • [x] Every v0.6 epic done, partly done or left out by the owner’s decision, with evidence above

  • [x] Release notes drafted

  • [x] Gated changes merged under the v0.6 mandate listed for review (progress.md)

  • [ ] Owner review of those merges (the vehicle, road, radar and camera schema changes)

  • [ ] GitHub Actions re-enabled and green on dev

  • [x] Released: dev merged into main and tagged v0.6.0 on 2026-10-25 at the owner’s request (release-please could not run with GitHub Actions disabled)