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

Split collision proximity threshold #2008

Merged

Conversation

JStech
Copy link
Contributor

@JStech JStech commented Apr 2, 2020

Description

Replaces collision_proximity_threshold config parameter with self_collision_proximity_threshoold and scene_collision_proximity_threshold, so that a lower self-collision threshold can be used. This helps handle near-collisions we suspect are from links that are always near to each other, although unlikely to collide.

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

Copy link
Member

@henningkayser henningkayser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good in general, I'll stress test this a bit. Please rebase and then lgtm after #1982

@AndyZe
Copy link
Member

AndyZe commented Apr 2, 2020

Did you test it? Maybe on the UR5 simulation? I can do that, if you want

@JStech JStech force-pushed the split-collision-proximity-threshold branch from a5c0bad to dce6344 Compare April 3, 2020 21:13
@JStech
Copy link
Contributor Author

JStech commented Apr 3, 2020

I did test it with the UR5 simulation on our current project.

@AndyZe
Copy link
Member

AndyZe commented Apr 4, 2020

Looks good to me!

@henningkayser
Copy link
Member

Looks good in general, Travis CI seems to require another rebase. Please consider the alternative implementation I suggested.

@JStech JStech force-pushed the split-collision-proximity-threshold branch from 3aaaa5f to 357052e Compare April 8, 2020 20:38
@JStech JStech force-pushed the split-collision-proximity-threshold branch from 619fdc7 to 91b989e Compare April 8, 2020 23:38
Copy link
Member

@henningkayser henningkayser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work! Could you take care about the last comment I have? Then lgtm

@henningkayser henningkayser merged commit 3be547d into moveit:master Apr 13, 2020
@welcome
Copy link

welcome bot commented Apr 13, 2020

Congrats on getting your first MoveIt pull request merged and improving open source robotics!

@tylerjw tylerjw mentioned this pull request May 8, 2020
20 tasks
tylerjw pushed a commit to PickNikRobotics/moveit that referenced this pull request May 12, 2020
* separate proximity threshold values for self-collisions and scene collisions
* increase default value of scene collision proximity threshold
* deprecate old parameters
tylerjw pushed a commit to PickNikRobotics/moveit that referenced this pull request May 12, 2020
* separate proximity threshold values for self-collisions and scene collisions
* increase default value of scene collision proximity threshold
* deprecate old parameters
tylerjw pushed a commit to PickNikRobotics/moveit that referenced this pull request May 20, 2020
* separate proximity threshold values for self-collisions and scene collisions
* increase default value of scene collision proximity threshold
* deprecate old parameters
sjahr pushed a commit to sjahr/moveit that referenced this pull request Jun 21, 2024
Co-authored-by: Henning Kayser <henningkayser@picknik.ai>
Co-authored-by: Tyler Weaver <maybe@tylerjw.dev>
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.

None yet

3 participants