Support physical worlds when launching robots - #302
Merged
Merged
Conversation
javizqh
approved these changes
Sep 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Physical worlds could not be launched through RAM.
physicalentry inworlds, so a robot in ascene of type
physicalraised a KeyError. It now uses the samerobot_ros2_apilauncher asgz, which runsros2 launchon the robotlaunch file without spawning anything in the simulator.
wait_robot_spawnwhilethe scene launcher calls
wait_robots_spawn, so launching a physical worldraised an AttributeError after the robot had started. Renamed to match.
Tested with a physical MiR100 world in a local RADI, the robot launches and
its topics are available. No change for existing gz worlds.