[Won't merge] Add ROS-I Cartesian Planner sample launch. #48
Conversation
This file contains 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
130s
force-pushed
the
add/cartesian_planner
branch
from
51af606
to
9fa38e4
Compare
|
I'm very sorry that i have updated to indigo-devel, please rebase against indigo-devel. Sorry to bother you. |
|
This PR isn't intended to be merged as mentioned so it's ok.
|
130s
changed the title
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.
Adding .launch and .rviz files to utilize moveit_cartesian_plan_plugin from ROS-Industrial.
Result looks like this video.
http://wiki.ros.org/denso?distro=hydro#denso_launch.Using_Cartesian_Path_Planner_Plug-In
From my experience, moveit_cartesian_plan_plugin so far seems to require more development to become a standardized tool, e.g. with this PR RViz loses its window frame (it's also possible that my PR isn't sufficient, but then how to add
cartesian_plan_pluginto your robot isn't documented AFAIK). That said, this PReq may stay un-merged, just remain as a reference purpose at least for now.