Lagrange v0.3.0: arms, electrical and thermal (release notes)¶
v0.2 was the simulation core and the AMR. v0.3 adds the electrical and thermal domains, a robot arm with MoveIt 2, a raster camera, a second physics engine, and replay in the C++ server. The AMR now drives on its own power system: a battery, a DC bus and two motor drives at 100 µs.
Status: released on 2026-10-25 as v0.3.0, at the owner’s request, after v0.2.0.
Highlights¶
Electrical.
Six USD schemas (
ElectricalMotorAPI_1,BatteryAPI_1,PortAPI_1, bus, load, converter), with ports on the same prims as the 3D parts.A network module: DC bus with capacitor, battery equivalent circuit, averaged dq motor drives with current loops, regeneration, brake resistor and trips, DC-DC converters between buses.
Controllers command torque; the electrical domain delivers it, or its ideal substitute does.
Overlay files give an imported robot motors, a battery and a bus without editing its URDF.
Export to an ngspice netlist or a Modelica model (
lagrange export).An FMI 3.0 co-simulation host, with a reference FMU (
lagrange_models/dc_drive).
Thermal.
Lumped thermal networks (
ThermalAPI_1,ThermalLinkAPI_1) heated by the electrical losses, with derating.The network runs when the site’s ambient temperature is given.
Coupling. Stability checks across the electrical, thermal and physics rates at start-up; physics reports each joint’s effective inertia for the motor models.
Bench mode.
--bench run.mcapreplaces physics by a recorded run; electrical, thermal and sensors run live, at 10 kHz electrical, about 59× real time.Replay.
lagrange_server --replay run.mcapreplays a recording to the viewer, with seeking. The Python mock server is now a test tool (Q15).Arm. The sample 6-DoF arm
arm6in a workcell; MoveIt 2 pick-and-place throughjoint_trajectory_controllerat 1 kHz; a wrist camera.Camera. A raster camera sensor (colour, depth, instance ids) on the same mesh pipeline as the viewer’s viewport, published as ROS
ImageandCameraInfoand shown in the viewer.Physics.
Jolt Physics 5.6 as a complete second backend (
--physics jolt, or the profile’srigid_body.backend), checked against MuJoCo by an agreement suite.Convex hull colliders in the world, in USD, in both backends and in the lidar (CPU and GPU).
collision_bakemakes them from render meshes with CoACD.
Schemas and profiles.
migrate_schemaandmigrate_profilebring old files up to date; the stage loader names the command when it meets an older schema version.Viewer.
Scene editing: schema values change in a running simulation from the inspector.
The Electrical workspace runs on the simulator’s power system.
Thermal false-colour and unlit shading in the viewport.
The camera view in the Sensors workspace.
Acceptance (roadmap §4)¶
Epic |
Acceptance |
Status |
Evidence |
|---|---|---|---|
Electrical network |
|
met, with owed items |
|
Coupling stability |
|
met |
|
Thermal |
|
met, with owed items |
|
FMU host |
A reference FMU runs in place of the built-in motor model; Q8 closed |
met; Q8 partly open |
|
Bench mode |
|
met |
About 59× real time on the development laptop |
Arm integration |
Scenario in |
met |
|
Camera sensor (raster) |
Projection tests; the viewer shows the sensor view |
met |
OpenCV finds checkerboard corners within 0.066 px mean of the pinhole model; calibration recovers fx, fy, cx, cy with RMS 0.07 px; Sensors workspace camera view |
Schema migration tooling |
Round-trip tests |
met |
|
Exports |
Netlist runs in ngspice |
met |
|
Second rigid-body backend |
Backend-agreement tests |
met, with a known issue |
|
Viewer additions |
Golden images |
met |
|
v0.2 items that moved here are done: G2 overlay files, B8 collision bake, E6 scene editing, E8 replay in the C++ server. H7 (a thin electrical slice) was replaced by the full domain. C5 (runtime rebase) stays deferred to v0.7.
Known issues¶
Jolt: drive wheels slip while ramping up. On Jolt’s rigid contacts the sample AMR’s casters take most of the load; after the 6 s demo drive Jolt is about 0.4 m behind MuJoCo. MuJoCo stays the default.
Nav2 start-up (from v0.2): some launches have one ROS process never discover another’s endpoint. Mitigated by retries; root cause not found.
Not run while GitHub Actions are disabled: the sanitizer builds of the USD packages and the nightly jobs. Everything else was verified locally with colcon.
Release checklist¶
[x] Every v0.3 epic done, with evidence above
[x] Release notes drafted
[x] Gated changes merged under the autonomous mandate listed for review (
progress.md)[ ] Owner review of those merges (the electrical, thermal and camera schemas, the C ABI)
[x] The v0.2.0 release published first (2026-10-25)
[ ] GitHub Actions re-enabled and green on
dev[x] Released:
devmerged intomainand taggedv0.3.0on 2026-10-25 at the owner’s request (release-please could not run with GitHub Actions disabled)