-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not the exact same implementation as the original LBC code ? #15
Comments
Correct! The conditional command here is a "target heatmap", which is the target point projected into the camera view. I found this to work a little better, but have yet to evaluate this quantitatively |
Thanks. Interesting result. I think there is less ambiguity when one use the target heatmap instead of the high level command. That may explain the performance gain if validated. |
Hi @bradyz can you explain a bit more about this target heatmap? I am really interested in knowing a bit more about it. |
So instead of using discrete commands, we render the project the future waypoint (this is typically pretty far, maybe 50 meters or so) into the first person view as a heatmap, then concatenate this to the RGB image. |
I see. This makes sense. Thank you for the quick response! |
Hi,
I wondering whether this base code implements exactly the original LBC algorithm. When I look at it closely
it seems that it doesn't use the branch selection based on command (follow lane, turn left, ...)
Instead it seems to use the target points coordinates.
Am I correct ?
The text was updated successfully, but these errors were encountered: