Antim/sim integration merged

[leshy]

No description provided.

[leshy]

@greptileai go for it

[greptile-apps]

Greptile Summary

Integrates Antim Labs DimSim simulator into dimos by adding a modular bridge architecture that manages a Deno subprocess for sensor data streaming and a lightweight TF publisher for coordinate transforms.

Key Changes:

• New DimSimBridge NativeModule wraps Deno CLI subprocess, auto-detects global/local installation
• DimSimTF module subscribes to odometry via LCM and publishes transform chain (world → base_link → sensors) plus camera intrinsics
• sim_basic blueprint provides visualization support (foxglove, rerun, websocket) with platform-specific transports
• sim_nav blueprint extends basic with full navigation stack (voxel mapping, cost mapping, A* planning, frontier exploration)
• Sensor data flows directly through LCM (no Python encode/decode), improving performance

Confidence Score: 4/5

• Safe to merge with one minor parameter usage suggestion
• Well-structured integration following existing patterns (NativeModule, Module base classes). Good error handling for missing dependencies. Only minor issue: unused duration parameter in move() method.
• No files require special attention - all changes are straightforward additions

Important Files Changed

Filename	Overview
dimos/robot/sim/blueprints/basic/sim_basic.py	Implements basic DimSim blueprint with visualization support (foxglove, rerun), platform-specific transports, and websocket visualization
dimos/robot/sim/blueprints/nav/sim_nav.py	Extends sim_basic with navigation capabilities: voxel mapping, cost mapping, A* planning, and frontier exploration
dimos/robot/sim/bridge.py	NativeModule wrapper managing DimSim bridge subprocess, auto-detects Deno/dimsim CLI, publishes sensor data to LCM
dimos/robot/sim/tf_module.py	TF publisher for DimSim: subscribes to odom, publishes transform chain, camera info at 1Hz; move() method has unused duration parameter

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[DimSim Bridge<br/>Deno Subprocess] -->|publishes to LCM| B[LCM Bus]
    B -->|odom, lidar, images| C[TF Module]
    B -->|sensor data| D[Visualization<br/>foxglove/rerun/websocket]
    C -->|publishes| E[Transform Chain<br/>world → base_link → sensors]
    C -->|publishes| F[Camera Info<br/>1 Hz]
    G[Navigation Stack<br/>mapping, planning, exploration] -->|cmd_vel| B
    B -->|cmd_vel| A
    
    H[sim_basic Blueprint] -.includes.- A
    H -.includes.- C
    H -.includes.- D
    I[sim_nav Blueprint] -.extends.- H
    I -.includes.- G

Loading

_{Last reviewed commit: 15526d4}

[greptile-apps]

_{9 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

duration parameter is unused. Other move() implementations in the codebase (unitree, drone) use this to execute timed movements.