-
Notifications
You must be signed in to change notification settings - Fork 115
RSDK-10392 remove magic numbers from point cloud collision check #4896
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
base: main
Are you sure you want to change the base?
Conversation
case *point: | ||
return pt.almostEqual(other), nil | ||
return pt.position.Sub(other.position).Norm() <= collisionBufferMM, nil |
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.
Oops discovered some bugs
motionplan/constraint.go
Outdated
@@ -414,27 +414,6 @@ func NewLineConstraint(pt1, pt2 r3.Vector, tolerance float64) (StateConstraint, | |||
return validFunc, gradFunc | |||
} | |||
|
|||
// NewOctreeCollisionConstraint takes an octree and will return a constraint that checks whether any geometries |
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.
This just isn't used anymore. Would like to cut down on the LOC
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.
LGTM
We already expose a buffer variable this just makes it so there aren't two variables, one of which cannot be changed
Edit: I should note that getting rid of this does have implications for collisions for 2D motion. We should probably be updating the collisionBuffer for that case along with the rest of the changes here