-
Notifications
You must be signed in to change notification settings - Fork 5
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
About the switch between stubborn and peanut #7
Comments
That's right, it always uses the prediction. We thought that it might be interesting to switch between the two policies, but we found it doesn't really help. Maybe it is worth exploring further though! |
Thanks for the reply. |
Hmm it should not stop. Can you show the error message? |
Oh that's a normal failure case, it will happen if there is a false positive detection and the agent calls "stop" as it thinks it reached the target. |
Yeah, I see. |
Currently it is set that way, but maybe that is actually a mistake -- if you try 960 during inference, let me know what happens! It is better to predict using global map than only using local map. See the ablation study in our paper for comparison |
I thought the performance might not be significantly impacted. But actually, a 1% decrease in success rate on the validation set when using the map size 960, which is perplexing to me. |
I believe only very few episodes need the agent to go outside of the 720 size map, so there is not much benefit to predicting out there. And then the new predictions causes some slightly different behavior sometimes which leads to 1% decrease in success (not really significant). |
Hi, I see there is implementation for switching between corner goal and prediction goal, but seems that the switch step is set to 0.
Does peanut just rely on the prediction model for deciding the long-term goal at a frequency?
Thanks for your interesting and inspiring work!
The text was updated successfully, but these errors were encountered: