Skip to content
This repository has been archived by the owner on Nov 13, 2017. It is now read-only.

Add capability of execute known trajectory with a ROS action #719

Closed
wants to merge 16 commits into from

Conversation

wkentaro
Copy link
Contributor

@wkentaro wkentaro commented Jul 18, 2016

@davetcoleman
Copy link
Member

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.
Copy link
Member

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 ;-)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

@rhaschke
Copy link
Contributor

rhaschke commented Jul 18, 2016

@wkentaro I started to work along that direction too. In my comment for #717 I wrote:

An alternative, IMHO even better approach is to turn the service into an action, which provides feedback and can be explicitly interrupted. I did that, but it requires several changes to existing moveit_config packages: as the service capability would be renamed (from MoveGroupExecuteService to MoveGroupExecuteAction all move_group.launch files would need an update.

I pushed two new branches:

What is missing is the following:

However, I could think of a slow transition, adding the new capability in Kinetic and loading both the old and new capability in newly created move_config packages (needs an adaption in setup assistant). In some later release we could remove the old service capability, hoping that meanwhile everybody has adapted their move configs.

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.

@wkentaro wkentaro force-pushed the feature/execute-action branch 3 times, most recently from 15352f0 to 16bc593 Compare July 19, 2016 05:30
@wkentaro
Copy link
Contributor Author

Consider merging your implementation and mine from new-traj-exec-action. I provide feedback about the finished trajectory segment.

Ok, I will do this tomorrow.

@v4hn
Copy link
Contributor

v4hn commented Jul 29, 2016 via email

@rhaschke
Copy link
Contributor

I handed over to @wkentaro. Did you have time to work on it?

@wkentaro
Copy link
Contributor Author

wkentaro commented Aug 9, 2016

@v4hn @rhaschke Sorry for late reply. I tried to merge the implementation in new-traje-action branch, and I think I've done. Could you please review?

@v4hn
Copy link
Contributor

v4hn commented Aug 9, 2016

@wkentaro Could you port this request to https://github.com/ros-planning/moveit ?
We are not going to merge anything into this repository anymore.

@wkentaro
Copy link
Contributor Author

Oh, moveit is being consolidated! Alright, I will do it.

@v4hn
Copy link
Contributor

v4hn commented Aug 10, 2016

On Tue, Aug 09, 2016 at 11:49:04PM -0700, Kentaro Wada wrote:

Oh, moveit is being consolidated!

has been :)

@wkentaro
Copy link
Contributor Author

Ported this PR to moveit/moveit#60.

@wkentaro wkentaro closed this Aug 17, 2016
@wkentaro wkentaro deleted the feature/execute-action branch August 17, 2016 04:45
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants