Flexible design for defining collision geometry
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Originally scoped in Milestone 3, see #372 for context. Define a design that scales across cars and that can be simply evolved from bounding boxes to more complex shapes. Most likely something similar to CarViz, but for geometries (see design doc on arch).
The idea is to be able to parametrize an agent with the collision geometry. We are currently hardcoding it to a bounding box tailor-made to the Prius visual geometry.
Contributor guide
No contributing guide indexed for this repository
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 with issue #372 and the linked design document, then review how the Prius-specific bounding box is currently hardcoded. Compare the proposed CarViz-like approach with the need to parameterize an agent's collision geometry. Done means a documented design that can evolve from bounding boxes to more complex shapes across cars.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- autonomous-driving
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100