-
Notifications
You must be signed in to change notification settings - Fork 334
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 trajectory end time validation fix #1090
JTC trajectory end time validation fix #1090
Conversation
Could you please check the docs if this is clearly documented how to fill the |
@christophfroehlich |
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.
LGTM. Just one request: Could you please add checks for the end time to invalid_message
test?
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.
LGTM, thanks!
@christophfroehlich is there anything I can do to help get this across the finish line? |
(cherry picked from commit b51e4c2)
(cherry picked from commit b51e4c2)
(cherry picked from commit b51e4c2)
(cherry picked from commit b51e4c2)
(cherry picked from commit b51e4c2) Co-authored-by: Henry Moore <[email protected]>
(cherry picked from commit b51e4c2) Co-authored-by: Henry Moore <[email protected]>
The
time_from_start
member for aJointTrajectoryPoint
is monotonically increasing, not a delta time, so I think we can just use the last one in the vector; summing them up seems incorrect. I also moved the points empty check earlier because.back().time_from_start
would seg fault with an empty points vector.