You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 20, 2020. It is now read-only.
We need to figure out how to use the translate the output from sign detection (left, right, or straight) to the correct path output from the path planner.
Some notes from me and Andrew's discussions:
Have sign detection publish the output as an enum to a topic (eg 0: no sign, 1: left, 2: right, 3: straight) @MartinEthier , and setup a callback in path planner to it
In the sign detection callback, we can set internal flags to tell us when each sign has been detected, and keep checking the topic until the sign is gone, so the sign we were looking at it is no longer visible, and we need to now change the path to obey what the sign said
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Port over last year's path planner code
The text was updated successfully, but these errors were encountered: