-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add error_string to FollowJointTrajectory response #4
Labels
Comments
+1 for adding an error_string member |
+1 this would be great |
adolfo-rt
pushed a commit
to pal-robotics-forks/control_msgs
that referenced
this issue
Feb 17, 2014
adolfo-rt
pushed a commit
to pal-robotics-forks/control_msgs
that referenced
this issue
Feb 17, 2014
You can find a patch with a proposed doc for the new field in PR #5. |
This was referenced Feb 26, 2014
Closed
The resolution of this issue seems to be blocking the release into Indigo, due to package version issues, see #6. |
Changes merged and released into indigo as control_msgs 1.3.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As of now, the result of a FollowJointTrajectory action is an error_code, which is partially informative. It lets you know whether execution was successful or not, and in case of failure, a general assessment of the failure type.
Still, I'd find it useful to have some additional information for at least user feedback.
Usecase
A motion fails because goal time constraints were violated for joint foo.
Current state
The error_code of the action result message states GOAL_TOLERANCE_VIOLATED. Assuming we're using the joint_trajectory_controller from ros_controllers in a realtime deployment, no log statements are issued, as currently there is no mechanism for logging from a realtime context.
Proposal
For most cases I think that it would suffice to create a complementary
error_string
member containing messages like:Although we could set up a mechanism for logging these messages from a realtime context, I think it's still relevant to add this to the action spec, so that the message can be used in the context of the client, like displaying it in a GUI.
The text was updated successfully, but these errors were encountered: