-
Notifications
You must be signed in to change notification settings - Fork 7
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
[Bug] Replan not triggered if the current rollouts reach the goal #9
Comments
Thank you for contributing to OpenPlanner. |
Thanks for your reply ! I will try to find a better solution. |
@blabla-my |
Thanks! This is a very nice case to understand why you say that no replan in last section is a design choice. |
However, I think it's better for ego to still have some lightly ability to avoid, but not too strong ability. For your example, I think the second bus should preserve its ability to slightly adjust its pose for avoidance, but not go over the first bus to reach goal. |
It is an application dependent feature. So everyone can customize accordingly |
|
Describtion
If the current rollouts can reach the goal, replanning will not be triggered. Thus some collision will happen while there are obstacles between ego and goal.
Required infomation:
Possible Root Cause and Solution
Root Cause
In
src/autoware/common/op_planner/src/DecisionMaker.cpp
,preCalcPrams->bFinalLocalTrajectory
is used to judge if current local path can reach the goal, and whilepreCalcPrams->bFinalLocalTrajectory
is true, replan won't be triggered.Possible Solution
Disable preCalcPrams->bFinalLocalTrajectory, making the replan continue to be triggered after the point where the local path could reach the goal.
To be specific, update line 380-387 in DecisionMaker.cpp to:
Demostration Video
Video to demonstrate this hazard: https://youtu.be/F5UjRHmLVUE
In this scenario, ego won't select a better trajectory to avoid the truck since the replan is not triggered. This scenario was tested more than 10 times and the collision always happened.
After applying the patch above, the collision won't happend (tested more than 10 times and none of them involved the collision). Video: https://youtu.be/6uezdQ3w2FU
@hatem-darweesh
The text was updated successfully, but these errors were encountered: