Add new option to MoveGroupInterface to specify move group node's namespace#533
Conversation
...ng_interface/move_group_interface/include/moveit/move_group_interface/move_group_interface.h
Outdated
Show resolved
Hide resolved
Codecov Report
@@ Coverage Diff @@
## main #533 +/- ##
==========================================
- Coverage 54.23% 54.23% -0.00%
==========================================
Files 192 192
Lines 20224 20224
==========================================
- Hits 10967 10966 -1
- Misses 9257 9258 +1
Continue to review full report at Codecov.
|
|
@JafarAbdi your link to the tutorials implies this is for multi-arm support. But I think we should be clear whether this is for:
For the former, users should be using one unified URDF and one MoveGroup, IMHO. Which use case is this for? |
@davetcoleman This's for the second case, I agree that having one MoveGroup node is what we should do in the first case |
davetcoleman
left a comment
There was a problem hiding this comment.
Joe and I reviewed this together and like this change. However we think a unit test should be written to demonstrate that everything loads up correctly with and without the namespace. Could you set this up?
moveit_ros/planning_interface/move_group_interface/src/move_group_interface.cpp
Show resolved
Hide resolved
|
Reported from discord
|
f601eef to
22f1906
Compare
Description
Currently, it's not possible to specify the move group node's namespace in the move group interface, which makes it not possible to have different motion planning displays that connect to different move groups, could be tested with https://github.com/JafarAbdi/moveit2_tutorials/tree/pr-multi_arm
Fix: https://answers.ros.org/question/381276/ros2-rviz-node-two-robots-with-different-namespaces/
Checklist