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

Fix duplication of Pilz motion sequence trajectory points... the right way #2945

Closed
sea-bass opened this issue Aug 2, 2024 · 0 comments · Fixed by #2961
Closed

Fix duplication of Pilz motion sequence trajectory points... the right way #2945

sea-bass opened this issue Aug 2, 2024 · 0 comments · Fixed by #2961
Assignees

Comments

@sea-bass
Copy link
Contributor

sea-bass commented Aug 2, 2024

In #2943, I submitted a band-aid fix for the Pilz motion sequence action server to de-duplicate trajectory time points due to requirements on the ros2_controllers Joint Trajectory Controller.

I did this by looking at the final packaged up trajectory and deduplicating points there, whereas it would be better to resolve the issue as the blended trajectory segments are being built up.

@sea-bass sea-bass added the help wanted Extra attention is needed label Aug 2, 2024
@sea-bass sea-bass self-assigned this Aug 10, 2024
@sea-bass sea-bass removed the help wanted Extra attention is needed label Aug 10, 2024
@github-project-automation github-project-automation bot moved this to ✅ Done in MoveIt Aug 11, 2024
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 a pull request may close this issue.

1 participant