open-rmf / open-rmf/rmf_simulation
[slotcar] Improve collision detection
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 21
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Right now the slotcar is requested to stop if the distance between its world pose and that of a non-static obstacles is less than a threshold. This is not very robust as two obstacles can have the same world pose but one with a larger geometry than the other. The slotcar will drive closer to the larger obstacle or worse might even collide. Hence, setting the threshold parameter is not very intuitive.
We should instead store AABBs of obstacles and then do a simple broadphase collision check between the robot AABB and that of the obstacle.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the slotcar collision handling and the code that tracks non-static obstacles. Read how world poses and the threshold parameter are currently used, then trace how robot and obstacle geometry can be represented as AABBs. Done means the slotcar performs a broadphase check against obstacle AABBs instead of relying on a pose-distance threshold, with collision behavior covering differently sized obstacles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- robotics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100