-
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
Fix floating point comparison in JTC #879
Fix floating point comparison in JTC #879
Conversation
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.
Thank you!
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, only one small fix in the format.
joint_trajectory_controller/src/joint_trajectory_controller.cpp
Outdated
Show resolved
Hide resolved
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
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #879 +/- ##
==========================================
+ Coverage 46.73% 47.33% +0.60%
==========================================
Files 40 40
Lines 3640 3640
Branches 1718 1718
==========================================
+ Hits 1701 1723 +22
+ Misses 749 725 -24
- Partials 1190 1192 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
|
71b06d0
into
ros-controls:master
* Fix floating point comparison in JTC * Fix format --------- Co-authored-by: Christoph Fröhlich <[email protected]> (cherry picked from commit 71b06d0)
* Fix floating point comparison in JTC * Fix format --------- Co-authored-by: Christoph Fröhlich <[email protected]>
Thanks for fixing this up and merging! Can this be backported to humble as well? |
I included this in #801 to avoid any conflicts on JTC. I hope it get merged soon, if you prefer you can use the branch and build it from source in the meantime (and give feedback/approval to the PR if you tested it successfully). |
* Fix floating point comparison in JTC * Fix format --------- Co-authored-by: Christoph Fröhlich <[email protected]>
* Fix floating point comparison in JTC * Fix format --------- Co-authored-by: Christoph Fröhlich <[email protected]>
Co-authored-by: Bence Magyar <[email protected]> Co-authored-by: Denis Štogl <[email protected]>
I was going through the MoveIt tutorials and there were instances where motion planning succeeded but execution failed with the error
Changing the comparison to use an epsilon fixed it locally for me.