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

Deduplicate joint trajectory points in Pilz Move Group Sequence capability #2943

Merged
merged 6 commits into from
Aug 2, 2024

Conversation

sea-bass
Copy link
Contributor

@sea-bass sea-bass commented Aug 1, 2024

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

  • Required by CI: Code is auto formatted using clang-format
  • Extend the tutorials / documentation reference
  • Document API changes relevant to the user in the MIGRATION.md notes
  • Create tests, which fail without this PR reference
  • Include a screenshot if changing a GUI
  • While waiting for someone to review your request, please help review another open pull request to support the maintainers

Closes #2741

@sea-bass sea-bass changed the title Deduplicate joint trajectory points before sending them to controllers Deduplicate joint trajectory points in Pilz Move Group Sequence capability Aug 1, 2024
Copy link
Contributor

@stephanie-eng stephanie-eng left a 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?

@sjahr sjahr merged commit 955f308 into main Aug 2, 2024
8 of 12 checks passed
@sjahr sjahr deleted the deduplicate-traj-points branch August 2, 2024 14:26
sjahr pushed a commit that referenced this pull request Aug 2, 2024
…ility (#2943)

* Deduplicate joint trajectory points before sending them to controllers

* Fix max loop value

* Move deduplication code to Pilz

* Clean up

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

Successfully merging this pull request may close these issues.

Pilz Industrial Motion Planner blend generates points with same time_from_start
3 participants