ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
Removing packages should not be necessary. If you overlay your catkin workspace properly, the 'originals' (from debs) are ignored.
Could you update your question with the following information:
2 | No.2 Revision |
Removing packages should not be necessary. If you overlay your catkin workspace properly, the 'originals' (from debs) are ignored.
Could you update your question with the following information:
Edit:
The instructions on the slides are not entirely correct. Specifically, the branch fix-84
command and similar don't actually checkout the branches, so you just end up building hydro-devel
. Obviously this doesn't result in binaries with the extended UI your after.
You could do this (in a new workspace, or just remove everything from your previous attempt):
mkdir -p ~/your_new_ws/src
cd ~/your_new_ws/src
wstool init .
wstool merge https://gist.githubusercontent.com/gavanderhoorn/1239f5b5ff3fd5915d7b/raw/35d56c311f515aa8fb4bf05e1156da80064eb0c0/moveit_swri.rosinstall
cd ..
catkin_make
source devel/setup.bash
If you now launch an RViz instance and add the MoveIt planning plugin, you should see the new UI.
PS: the moveit_swri.rosinstall
gist is just for convenience. You could have checked out everything by hand, and then do something like git checkout {fix-82, addFirFilter, FIR_filter}
. Now wstool
does this for you.
3 | No.3 Revision |
Removing packages should not be necessary. If you overlay your catkin workspace properly, the 'originals' (from debs) are ignored.
Could you update your question with the following information:
Edit:
The instructions on the slides are not entirely correct. Specifically, the branch fix-84
command and similar don't actually checkout the branches, so you just end up building hydro-devel
. Obviously this doesn't result in binaries with the extended UI your you're after.
You could do this (in a new workspace, or just remove everything from your previous attempt):
mkdir -p ~/your_new_ws/src
cd ~/your_new_ws/src
wstool init .
wstool merge https://gist.githubusercontent.com/gavanderhoorn/1239f5b5ff3fd5915d7b/raw/35d56c311f515aa8fb4bf05e1156da80064eb0c0/moveit_swri.rosinstall
cd ..
catkin_make
source devel/setup.bash
If you now launch an RViz instance and add the MoveIt planning plugin, you should see the new UI.
PS: the moveit_swri.rosinstall
gist is just for convenience. You could have checked out everything by hand, and then do something like git checkout {fix-82, addFirFilter, FIR_filter}
. Now wstool
does this for you.
4 | No.4 Revision |
Removing packages should not be necessary. If you overlay your catkin workspace properly, the 'originals' (from debs) are ignored.
Could you update your question with the following information:
Edit:
The instructions on the slides are not entirely correct. Specifically, the branch fix-84
command and similar don't actually checkout the branches, so you just end up building hydro-devel
. Obviously this doesn't result in binaries with the extended UI you're after.
You could do this (in a new workspace, or just remove everything from your previous attempt):
mkdir -p ~/your_new_ws/src
cd ~/your_new_ws/src
wstool init .
wstool merge https://gist.githubusercontent.com/gavanderhoorn/1239f5b5ff3fd5915d7b/raw/35d56c311f515aa8fb4bf05e1156da80064eb0c0/moveit_swri.rosinstall
cd ..
catkin_make
source devel/setup.bash
If you now launch an RViz instance and add the MoveIt planning plugin, you should see the new UI.
PS: the moveit_swri.rosinstall
gist is just for convenience. You could have checked out everything by hand, and then do something like git checkout {fix-82, addFirFilter, FIR_filter}
. Now wstool
does this for you.
PPS: just removing the ros-hydro-moveit-full
package will most likely not do what you want. As it is a top-level package, it will not remove any of its dependencies (among which are the ros-hydro-moveit-core
, ..-moveit-ros
and ..-moveit-setup-assistant
). You'll have to specify each package by name (but removing them should not be necessary, as the ones in your catkin ws will have higher priority).
5 | No.5 Revision |
Removing packages should not be necessary. If you overlay your catkin workspace properly, the 'originals' (from debs) are ignored.
Could you update your question with the following information:
Edit:
The instructions on the slides are not entirely correct. Specifically, the branch fix-84
command and similar don't actually checkout the branches, so you just end up building hydro-devel
. Obviously this doesn't result in binaries with the extended UI you're after.
You could do this (in a new workspace, or just remove everything from your previous attempt):
mkdir -p ~/your_new_ws/src
cd ~/your_new_ws/src
wstool init .
wstool merge https://gist.githubusercontent.com/gavanderhoorn/1239f5b5ff3fd5915d7b/raw/35d56c311f515aa8fb4bf05e1156da80064eb0c0/moveit_swri.rosinstall
wstool up
cd ..
catkin_make
source devel/setup.bash
If you now launch an RViz instance and add the MoveIt planning plugin, you should see the new UI.
PS: the moveit_swri.rosinstall
gist is just for convenience. You could have checked out everything by hand, and then do something like git checkout {fix-82, addFirFilter, FIR_filter}
. Now wstool
does this for you.
PPS: just removing the ros-hydro-moveit-full
package will most likely not do what you want. As it is a top-level package, it will not remove any of its dependencies (among which are the ros-hydro-moveit-core
, ..-moveit-ros
and ..-moveit-setup-assistant
). You'll have to specify each package by name (but removing them should not be necessary, as the ones in your catkin ws will have higher priority).
Edit 2: added wstool up
right after wstool merge ..
.