Reinstate Humble Compatibility for GetCartesianPath & Expose planning_scene To User
#66
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AndrejOrsula
approved these changes
May 7, 2024
2 tasks
AndrejOrsula
pushed a commit
that referenced
this pull request
May 10, 2024
…ing_scene` To User (#66) * Reinstate Humble compatibility for GetCartesianPath * Expose planning scene to user
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes two small changes:
GetCartesianPathparameters added in Added setting of cartesian speed and acceleration #53 exist in Iron but not in Humble. This PR fixes that by checking if those attributes exist before assigning them.MoveIt2had the ability to get and access the latest planning scene, that was not exposed to users. this PR addresses that.(I'm happy to separate this into two PRs if you prefer -- I made it a joint PR for now given how small each change is.)