Skip to content
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

JTC computes wrong trajectory_end_time during validate_trajectory_msg #1138

Closed
KolinGuo opened this issue May 21, 2024 · 3 comments · Fixed by #1090
Closed

JTC computes wrong trajectory_end_time during validate_trajectory_msg #1138

KolinGuo opened this issue May 21, 2024 · 3 comments · Fixed by #1090
Labels

Comments

@KolinGuo
Copy link

Describe the bug
joint_trajectory_controller computes wrong trajectory_end_time during validate_trajectory_msg.

In JointTrajectoryController::validate_trajectory_msg() method, the trajectory_end_time is computed by adding the time_from_start of all trajectory points to trajectory_start_time.

However, if I understand correctly, the time_from_start values are all referenced from the header.stamp and are not accumulated (delta time between two trajectory points).

Expected behavior
Correctly compute trajectory_end_time as
trajectory_end_time = trajectory_start_time + trajectory.points.back().time_from_start

Environment (please complete the following information):

  • OS: Ubuntu 22.04
  • Version: Humble & Rolling
@KolinGuo KolinGuo added the bug label May 21, 2024
@christophfroehlich christophfroehlich linked a pull request May 22, 2024 that will close this issue
@christophfroehlich
Copy link
Contributor

There is already a PR fixing this, see #1090

@KolinGuo
Copy link
Author

Ahh I see, didn't notice the PR previously. Thanks for the pointer!

@christophfroehlich
Copy link
Contributor

No problem at all, thanks for reporting ;) But you could have a look at the PR and give your approval if this works for you (Files changed -> Review Changes)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants