-
Notifications
You must be signed in to change notification settings - Fork 531
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
Deduplicate joint trajectory points in Pilz Move Group Sequence capability #2943
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.
I don't entirely agree that we should fix this at this level, but I'd be loathe to let perfect be the enemy of the good here, and a band aid fix is better than broken.
Could you add a comment or a TODO note specifically calling this out, though, such that in the future, if the duplicate points issue is "properly" addressed, it's clear that this de-duplicate step can be removed?
moveit_planners/pilz_industrial_motion_planner/src/command_list_manager.cpp
Show resolved
Hide resolved
…ility (#2943) * Deduplicate joint trajectory points before sending them to controllers * Fix max loop value * Move deduplication code to Pilz * Clean up * Add todo
Description
I was unable to test moveit/moveit2_tutorials#917 successfully on Rolling/main because there was an issue with sending duplicate time points to joint trajectory controllers with the Pilz move group sequence capability.
This PR fixes that, but I am not entirely sure this is the most efficient fix, as it would be preferable to package the trajectory correctly in the first place. But... this works.
Checklist
Closes #2741