Add lane speed limits to the graph and factor them into the planning #44
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces the ability to (optionally) set speed limits on nav graph lanes. These speed limits will be respected by the planner.
For the initial implementation if there are multiple speed limits along one continuous stretch (collinear lanes that have different speed limits), then the planner will use the lowest speed limit along the entire stretch (or possibly come to a stop at the point where the lanes change and then switch speeds, if that would be faster). This approach does not provide optimal trajectories. We should instead have the robot accelerate/decelerate at each lane intersection in compliance with the changes in speed limits, but that will take considerably more effort to work out, so we'll start with this and improve the implementation in a future PR.