-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add .action file for execution trajectory in a ROS action #24
Add .action file for execution trajectory in a ROS action #24
Conversation
-1 on the name. |
fd41eeb
to
5e694f7
Compare
5e694f7
to
ce3fdd3
Compare
Fixed. |
# The full starting state of the robot at the start of the trajectory | ||
moveit_msgs/RobotState trajectory_start | ||
|
||
# The trace of the trajectory recorded during execution |
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.
could you explain "trace" better... in what cases would it differ from the input trajectory
and at what discretization level are you expecting this returned trajectory to be at?
@davetcoleman |
I'm not sure if they are useful or not, but it wasn't obvious to me what they would be used for. Seeing how the old |
I agree. I think the results can be added afterward when it is required. |
cherry-picked to J |
Thanks! |
Hm. Even better would have been @v4hn @davetcoleman: What do you think? Should we also rename the existing |
I see your point, trajectory makes more sense than path. +1 I don't see nearly enough advantage to change the long existing service On Aug 19, 2016 12:45 PM, "Robert Haschke" notifications@github.com wrote:
|
Are we going to make a change discussed after this PR was merged any sooner? |
For moveit/moveit_ros#719
Being moved from #24