-
Notifications
You must be signed in to change notification settings - Fork 682
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
fix(behavior_path_planner): add function to check the shift points in avoidance module #794
fix(behavior_path_planner): add function to check the shift points in avoidance module #794
Conversation
Codecov Report
@@ Coverage Diff @@
## main #794 +/- ##
========================================
- Coverage 9.55% 9.44% -0.12%
========================================
Files 935 935
Lines 57795 58488 +693
Branches 10430 10430
========================================
Hits 5522 5522
- Misses 47734 48427 +693
Partials 4539 4539
*This pull request uses carry forward flags. Click here to find out more.
Continue to review full report at Codecov.
|
@takayuki5168 @rej55 Can you review this PR? |
I guess it's better to be reviewed by @TakaHoribe @zulfaqar-azmi-t4 🙏 |
@shulanbushangshu |
Thank you.I will fix the DCO |
Signed-off-by: jack.song <jack.song@autocore.ai>
Signed-off-by: jack.song <jack.song@autocore.ai>
@shulanbushangshu
For single obstacle case, the solution works. review_after2.mp4Let me illustrate the acceptable result first, as 1m36s: if furthest obstacle was ignored (path not shifted) but if we place an obstacle ahead, the path will still remain shifted if the condition is acceptable. Then in your proposed solution, when the furthest obstacle near the discontinued path was ignore, when we place the obstacle ahead (0m24s), the new obstacle is also ignored. |
Thank you for checking. I have seen what you mean in the example.I will continue to improve related features.
…________________________________
发件人: Zulfaqar Azmi ***@***.***>
发送时间: 2022年5月25日 13:22
收件人: autowarefoundation/autoware.universe ***@***.***>
抄送: Song Shaojie ***@***.***>; Mention ***@***.***>
主题: Re: [autowarefoundation/autoware.universe] fix(behavior_path_planner): add function to check the shift points in avoidance module (PR #794)
@shulanbushangshu<https://github.com/shulanbushangshu>
I deeply apologize for the delay.
I've checked your solution using
1. single obstacle
2. dual obstacles
For single obstacle case, the solution works.
But when dual obstacle situation, the solution might be off.
Please refer to the following videos for example. (sorry again due to some technical issue, the video doesn't show full frame, but i think it should be sufficient)
https://user-images.githubusercontent.com/93502286/170184933-0ef57c32-7ab9-4f19-97bd-8902cb8e4670.mp4
Let me illustrate the acceptable result first, as 1m36s: if furthest obstacle was ignored (path not shifted) but if we place an obstacle ahead, the path will still remain shifted if the condition is acceptable.
Then in your proposed solution, when the furthest obstacle near the discontinued path was ignore, when we place the obstacle ahead (0m24s), the new obstacle is also ignored.
―
Reply to this email directly, view it on GitHub<#794 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AYQTU2VRPTGJGQPW4SN2IWLVLW2LBANCNFSM5UHOAQYQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
This pull request has been automatically marked as stale because it has not had recent activity. |
I close this pr and will test this issue in the newest code. |
…0/update-start-goal-planner Feat/beta/v0.10.0/update start goal planner
…ndation#794) Signed-off-by: Takayuki Murooka <takayuki5168@gmail.com>
Description
To solve #706
We can add function to detect points with offset distance to make sure they are within the drivable zone.
We can determine whether the offset points are all in the driveable lane in the generateAvoidancePath of avoidance module(Consider the width of the vehicle when detecting),otherwise we use reference_path as the obstacle avoidance path(No obstacle avoidance behavior)
Related links
Wrong path planned by avoidance module in a special case #706
Tests performed
Case1:
![2022-04-25 11-19-01](https://user-images.githubusercontent.com/102840938/165015981-863c9a67-aabb-494b-bb54-b27f53d8cd24.png)
![2022-04-25 11-25-21](https://user-images.githubusercontent.com/102840938/165016090-adf663e5-952b-41fc-b67c-e2f3cea84217.png)
1.Run planning_simulator.
2.place ego position and goal
3. Set a obstacle near discontinuous adjacent lanes
4. result -- ego vehicle stops
Case2:
1.Run planning_simulator.
2.place ego position and goal
3. Set a obstacle in continuous adjacent lanes
4. result-- ego vehicle bypasses obstacle
Notes for reviewers
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.
In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.
Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.
After all checkboxes are checked, anyone who has write access can merge the PR.