We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
At least that is what I observed testing the joint_trajectory_controller.
joint_trajectory_controller
Eventhough the goal is aborted, the trajectory stays and the controller tries to execute it. Imho this can lead to unpredictable behaviour.
if (!checkStateTolerancePerJoint(state_joint_error_, joint_tolerances.state_tolerance)) { if (verbose_) { ROS_ERROR_STREAM_NAMED(name_,"Path tolerances failed for joint: " << joint_names_[i]); checkStateTolerancePerJoint(state_joint_error_, joint_tolerances.state_tolerance, true); } rt_segment_goal->preallocated_result_->error_code = control_msgs::FollowJointTrajectoryResult::PATH_TOLERANCE_VIOLATED; rt_segment_goal->setAborted(rt_segment_goal->preallocated_result_); rt_active_goal_.reset(); successful_joint_traj_.reset(); }
The text was updated successfully, but these errors were encountered:
Same as #48
Sorry, something went wrong.
No branches or pull requests
At least that is what I observed testing the
joint_trajectory_controller
.Eventhough the goal is aborted, the trajectory stays and the controller tries to execute it. Imho this can lead to unpredictable behaviour.
The text was updated successfully, but these errors were encountered: