maliput / maliput/maliput_multilane
Multilane Technical debt - RoadCurve validity
@agalbachicar is already working on this.
Since Jun 4, 2019.
- Dominant language
- C++
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
The following list summarizes technical debt / nice to haves / TODOs in multilane related to the RoadCurve validity.
- [ ] [arc_road_curve.cc:82](https://github.com/RobotLocomotion/drake/blob/master/automotive/maliput/multilane/arc_road_curve.cc#L82) --> it is complex to solve.
- [ ] [arc_road_curve.cc:126](https://github.com/RobotLocomotion/drake/blob/master/automotive/maliput/multilane/arc_road_curve.cc#L126) --> it involves solving several TODOs related to volume constraints.
- [ ] [connection.cc:67](https://github.com/RobotLocomotion/drake/blob/master/automotive/maliput/multilane/connection.cc#L64) and [connection.cc:107](https://github.com/RobotLocomotion/drake/blob/master/automotive/maliput/multilane/connection.cc#L104) --> trivially solved after the previous one is.
This ticket is a copy of: https://github.com/RobotLocomotion/drake/issues/8897
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.
Assessment
This issue has not been assessed yet.