-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor ROS2SpawnerComponent #26
base: forward_branch_wp2
Are you sure you want to change the base?
Conversation
{ | ||
for (auto spawnPoint : GetSpawnPoints()) | ||
for (const auto& [name, info] : GetSpawnPoints()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GetSpawnPoints is currently checking only children for SpawnPointComponent, what do you think about changing it to all descendants? Use case I have in mind: AMR docking station as a prefab - it could provide a spawning point right off the shelf
652b3e9
to
ceb071c
Compare
I am converting to draft due to the major changes in the Spawner's design in the upstream. I will reevaluate on top of those |
ceb071c
to
eeef000
Compare
* Add spawner interface to allow selection of spawn points Signed-off-by: Artur Kamieniecki <[email protected]>
* add m_namespace so multiple Spawners can be defined without collisions * treat typo in spawn point name as error instead of creating in initial_pose * make code more idiomatic - use ROS2Conversion utils, structured bindings, avoid map double-lookups Signed-off-by: Mateusz Żak <[email protected]>
Signed-off-by: Mateusz Żak <[email protected]>
Signed-off-by: Mateusz Żak <[email protected]>
* allow spawning non-ROS prefabs in the scene e.g. parts of envirionment * use robot_namespace request field to customize name of the spawnable Signed-off-by: Mateusz Żak <[email protected]>
Signed-off-by: Mateusz Żak <[email protected]>
fe20b0b
to
c1b4fd8
Compare
fix device no found
This is an enabler for further work on forward_branch. However, enhancements are generic enough so it should be suitable for development after rebase
Changes: