-
Notifications
You must be signed in to change notification settings - Fork 3
Added support for baked collision checking. #27
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
Why do the internal methods all pass
robot_checker
, but the public methods all use theself
reference?Uh oh!
There was an error while loading. Please reload this page.
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.
self.robot_collision_checker
is a factory that creates arobot_checker
context manager. This additional level of indirection allows us to do baking in__enter__
and cleanup baking in__exit__
. It also lets us wrap the__enter__
and__exit__
methods of aCollisionOptionsStateSaver
to enableCollisionOptions.ActiveDOFs
.All of the internal methods take
robot_checker
so we only do the baking once per query. The usage looks pattern looks like this:The name
robot_collision_checker
androbot_checker
is confusing, but is chosen to be consistent with the other planners in PrPy. @cdellin and I discussed this in personalrobotics/prpy#343, but did not come up with a better name. I would prefer to stick with these names for now and refactor everything (including all of the planners in PrPy) at once.