-
Notifications
You must be signed in to change notification settings - Fork 69
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
A suggestion on the threshold for brake prediction #25
Comments
Thanks for the suggestion! The rationale behind such a low threshold is that the v1 leaderboard penalizes false negatives much more than false positives (which we can even get away with the creep forward hack). However, writing the threshold to be positively correlated with controller throttle is definitely an interesting idea as it exploits disagreements between the two networks, please let me know if that yields better results on your end! |
Hello, I am wondering if you see better numbers with using throttle as the brake threshold? Also I went back and checked my old eval video logs: https://wandb.ai/trilobita/carla_temporal_lidar_rgb_eval?workspace=user-trilobita, 0.1 threshold works well and I rarely see it stops in the middle of the road. If you see the model stops often (other than some occasions in Town1/2) there might have been some other issues going, and I would love to investigate more. Thanks! |
Sorry for the late reply, being busy writting manuscripts.. I encounter the model stop problem when I try to evaluate it in some emergency braking scenarios, the predicted braking is like |
Out of curiosity. For you 61 DS submission that already include the creeping hack + 0.1 brake threshold or did you add that later for the release? |
I found that in the previous V1 agent, the threshold for brake prediction is 0.3 in
lav_agent.py
However, the threshold changes to 0.1 in the V2 agent
This makes the car stop in the middle road in many scenarios.
I personally change the code to use the throttle as threshold to fix the problem.
The text was updated successfully, but these errors were encountered: