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

[Python] Added Allowed Collision Matrix to planning scene and optional planning scene during planning #2387

Conversation

JensVanhooydonck
Copy link
Contributor

@JensVanhooydonck JensVanhooydonck commented Sep 26, 2023

Description

Added the ACM to the planning scene object. This allows setting the Allowed Collision Object Matrix.
Also added an optional planning_scene in the Plan function so another planning can be used then the current planning scene. (Can be used as a base for a basic python Task manager)

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

@codecov
Copy link

codecov bot commented Sep 26, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (3ba9d9d) 50.44% compared to head (975b79d) 50.35%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2387      +/-   ##
==========================================
- Coverage   50.44%   50.35%   -0.08%     
==========================================
  Files         390      390              
  Lines       31954    31956       +2     
==========================================
- Hits        16115    16089      -26     
- Misses      15839    15867      +28     
Files Coverage Δ
...veit/moveit_core/planning_scene/planning_scene.cpp 82.83% <100.00%> (+0.36%) ⬆️

... and 3 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@peterdavidfagan peterdavidfagan left a comment

Choose a reason for hiding this comment

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

These changes need to be tested but on a high-level the changes look good to me. Once I have patched the issue with parameters in the tutorials I'll look to test and approve changes.

@JensVanhooydonck
Copy link
Contributor Author

@peterdavidfagan I've added the return policy and the planning scene argument to line 81.

@peterdavidfagan
Copy link
Member

Thanks @JensVanhooydonck, looks good to me. Will test on a robot later today.

@henningkayser henningkayser added the backport-iron Mergify label that triggers a PR backport to Iron label Oct 24, 2023
@henningkayser henningkayser merged commit 7b621d7 into moveit:main Oct 24, 2023
12 checks passed
mergify bot pushed a commit that referenced this pull request Oct 24, 2023
…planning scene during planning (#2387)

(cherry picked from commit 7b621d7)
henningkayser pushed a commit that referenced this pull request Jan 23, 2024
…planning scene during planning (backport #2387) (#2479)

(cherry picked from commit 7b621d7)

Co-authored-by: Jens Vanhooydonck <[email protected]>
Co-authored-by: Sebastian Jahr <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-iron Mergify label that triggers a PR backport to Iron
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants