Replies: 1 comment
|
CARLA 1.0 (tag The CARLA team ported the Autoware layer of TIER IV's fork into CARLA, on top of its ROS 2 middleware abstraction. The source is the CARLA 1.0 provides:
The main goal of the first milestone is met without a plugin. With the CARLA 1.0 package, Autoware (classical mode) drives to a goal in Town10HD with no build of Unreal Engine or CARLA. We tested this with Fast DDS and with CycloneDDS on the simulator side. Documentation: https://carla-ue5.readthedocs.io/en/latest/autoware/ The Autoware-side work continues in #7385 (which CARLA version and integration path to use for Autoware) and #7277 (the closed-loop evaluation architecture). |
Uh oh!
There was an error while loading. Please reload this page.
Summary
We (TIER IV) propose to make CARLA a first-class, direct DDS peer for Autoware — the same relationship Autoware already has with AWSIM — by delivering the Autoware integration as an out-of-tree CARLA extension plugin rather than as in-tree modifications to the simulator. CARLA's core stays Autoware-agnostic (only a generic ROS 2 extension API is added upstream); all Autoware-specific mapping lives in a separately released plugin (
libcarla-autoware-extension.so) that runs in-process with native DDS performance and requires no rebuild of CARLA or Unreal Engine.We call this "semi-native": native in-process performance, but cleanly outside the simulator core. This proposal asks for feedback from the Autoware community on the approach and on the Autoware-side artifacts (launch/config and
autoware_carla_interface).Background: why not in-tree native
TIER IV today maintains a working native CARLA ↔ Autoware integration. However, it currently lives as direct modifications inside a private CARLA fork, and that shape has two structural problems:
The consequence is that, in its current form, the integration cannot become a shared community asset — every external user would have to reproduce a private, Autoware-coupled fork of the simulator.
The plugin-based "semi-native" architecture below is designed specifically to remove both blockers at once.
The AWSIM precedent
Autoware already treats AWSIM as a direct DDS peer:
autoware_launch/launch/e2e_simulator.launch.xmlbranches onsimulator_type:=awsim|carla, and AWSIM does not require a simulator interface package because it publishesautoware_msgsdirectly. The only Autoware-side artifacts for AWSIM are a sensor kit, a vehicle launch, a diagnostics profile, and maps.CARLA 0.10.x (UE 5.5) now ships a native, in-process ROS 2 stack in a runtime-loaded shared library, and official packages are built with ROS 2 enabled. This finally makes the same "direct DDS peer, no interface package in the data path" status reachable for CARLA. Our proposal is to get CARLA to AWSIM-equivalent integration status, without putting any Autoware code into the CARLA core.
Proposal: "semi-native" defined symmetrically
--ros2-extension=<path.so>dlopens an extension after ROS 2 startup; absent the flag, behavior is unchanged. The extension registers sensor-data observers, creates publishers through the existing DDS participant (under whichever--rmw=backend is selected), and feeds a control sink — with no Autoware vocabulary in the core. Any stack (Autoware, Nav2, Apollo, …) can use the same socket.Performance is not sacrificed: the extension runs in the simulator process with direct callbacks (no IPC, no re-serialization), identical to a compiled-in implementation. The LiDAR hot path (full configured rate, e.g. 20 Hz) and async camera publishing are explicit acceptance criteria, all on native CycloneDDS — no bridge, no republishing.
Architecture (three tiers + Autoware side)
libcarla-autoware-extension.so(out-of-tree, separately released). Autoware/tier4message types (hand-written PODs + CDR + REP-2011 type hashes for Humble and Jazzy),/vehicle/status/*publishers, MGRS-offset GNSS pose,/control/command/*+/vehicle/engagesubscribers mapped into the core control sink, thePointXYZIRCAEDTpoint layout, and Autoware QoS profiles. Built against released CARLA package headers and shipped as a prebuilt.soper CARLA × ROS distro. No conditional compilation ever enters the CARLA core.sensor_kit_calibration.yamlas the single source of truth for sensor placement, owns the synchronous tick loop and ego/NPC spawn, plus a single authoritative per-map metadata record (MGRS origin / geo-reference) and demo/docs.autoware_launch: refreshcarla_sensor_kit_launchfor the native topic set, add acarla_vehicle_launch, keep theautoware-carla.yamldiagnostics.autoware_universe/simulator/autoware_carla_interface: add a native mode that launches nothing in the data path (AWSIM-style), shrinking the package toward configuration; the existing 0.9.15 Python-bridge mode is kept during a deprecation window.First milestone (success criterion)
An Autoware developer can, without building Unreal Engine or CARLA: (1) download an official CARLA 0.10.x package, (2) drop in
libcarla-autoware-extension.so, (3) spawn ego + sensors with the companion runner, (4) runros2 launch autoware_launch e2e_simulator.launch.xml simulator_type:=carla, and drive a planned route in a stock CARLA town (Town10) with the entire data path on native CycloneDDS — no bridge, no republishing.Roadmap
ue5-devue5-dev.so: opens with a CycloneDDS ↔rmw_cycloneddsinterop spike (REP-2011 type hashes, QoS), then messages → publishers/subscribers → MGRS /PointXYZIRCAEDT/ steeringautoware_launchkit/vehicle/diagnostics +autoware_carla_interfacenative mode, with the working demo as evidenceautoware_launch,autoware_universeStatus of the CARLA-side preconditions
The CARLA development branches
ue4-devandue5-devhad drifted apart, and the native ROS 2 / DDS work we depend on originated onue4-dev. That divergence is actively being closed:ue4-devfeatures and fixes toue5-dev. The native ROS 2 publisher series under it is well advanced.--rmw=) toue5-dev. This is the remaining key precondition: CycloneDDS onue5-devis what makes the native-performance Autoware path possible.Once #9762 lands on
ue5-dev, the rest of the roadmap can proceed in order on top of the upstream native ROS 2 stack.What we are asking for
Feedback from the Autoware community on:
carla_sensor_kit_launch+ acarla_vehicle_launchinautoware_launch, and adding a native mode toautoware_carla_interface(the maintainers are TIER IV, so we would co-design this).All reactions