-
Notifications
You must be signed in to change notification settings - Fork 118
Add capability of execute known trajectory with a ROS action #719
Conversation
84c40f3
to
4d93afd
Compare
The background for why we need this: "In order to allow stopping of a trajectory, the service should be turned into an action as well." |
/********************************************************************* | ||
* Software License Agreement (BSD License) | ||
* | ||
* Copyright (c) 2016, Willow Garage, Inc. |
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.
i think you could change the company name to your university or something. WG is not writing code in 2016 ;-)
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.
Fixed.
@wkentaro I started to work along that direction too. In my comment for #717 I wrote:
I pushed two new branches:
What is missing is the following:
If you could work along this direction, that would be indeed great. Consider merging your implementation and mine from new-traj-exec-action. I provide feedback about the finished trajectory segment. |
15352f0
to
16bc593
Compare
Ok, I will do this tomorrow. |
What's the state of this request?
|
I handed over to @wkentaro. Did you have time to work on it? |
eb7195a
to
f0a5ac7
Compare
@wkentaro Could you port this request to https://github.com/ros-planning/moveit ? |
Oh, moveit is being consolidated! Alright, I will do it. |
On Tue, Aug 09, 2016 at 11:49:04PM -0700, Kentaro Wada wrote:
has been :) |
Ported this PR to moveit/moveit#60. |
Proposed at #709 (comment) #713 (comment)
Depends on moveit/moveit_msgs#23