-
Notifications
You must be signed in to change notification settings - Fork 676
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(no_stopping_area): skip drawing a stop line in the case where the detected stop lines are goals #7280
Merged
kosuke55
merged 5 commits into
autowarefoundation:main
from
kaigohirao:revert-no-stopping-area-module
Jun 14, 2024
Merged
fix(no_stopping_area): skip drawing a stop line in the case where the detected stop lines are goals #7280
kosuke55
merged 5 commits into
autowarefoundation:main
from
kaigohirao:revert-no-stopping-area-module
Jun 14, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
component:planning
Route planning, decision-making, and navigation. (auto-assigned)
label
Jun 5, 2024
kaigohirao
changed the title
fix(no_stopping_area): Incorrect implementation in
fix(no_stopping_area): skip drawing a stop line in the case where the detected stop lines are goals
Jun 5, 2024
planning/behavior_velocity_no_stopping_area_module
shmpwk
added
the
run:build-and-test-differential
Mark to enable build-and-test-differential workflow. (used-by-ci)
label
Jun 5, 2024
shmpwk
reviewed
Jun 5, 2024
planning/behavior_velocity_no_stopping_area_module/src/scene_no_stopping_area.cpp
Outdated
Show resolved
Hide resolved
kosuke55
force-pushed
the
revert-no-stopping-area-module
branch
2 times, most recently
from
June 11, 2024 01:20
b27d0aa
to
97ac113
Compare
sorry to be late. I'm checking with tier4 internal scenario tests. |
… area in parking on the shoulder (autowarefoundation#6517)" This reverts commit 144b9c7.
…e does not insert stop line
…o_stopping_area.cpp
kosuke55
force-pushed
the
revert-no-stopping-area-module
branch
from
June 13, 2024 13:43
97ac113
to
5acb6d7
Compare
kosuke55
approved these changes
Jun 14, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
3 tasks
shmpwk
added a commit
to tier4/autoware.universe
that referenced
this pull request
Jun 25, 2024
… detected stop lines are goals (autowarefoundation#7280) * Revert "fix(no_stopping_area): fix stopping in front of a no stopping area in parking on the shoulder (autowarefoundation#6517)" This reverts commit 144b9c7. * if the stop point is near goal(distance < 1m), no stopping area module does not insert stop line * style(pre-commit): autofix * Update planning/behavior_velocity_no_stopping_area_module/src/scene_no_stopping_area.cpp --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Shumpei Wakabayashi <[email protected]> Co-authored-by: kosuke55 <[email protected]>
simon-eisenmann-driveblocks
pushed a commit
to simon-eisenmann-driveblocks/autoware.universe
that referenced
this pull request
Jun 26, 2024
… detected stop lines are goals (autowarefoundation#7280) * Revert "fix(no_stopping_area): fix stopping in front of a no stopping area in parking on the shoulder (autowarefoundation#6517)" This reverts commit 144b9c7. * if the stop point is near goal(distance < 1m), no stopping area module does not insert stop line * style(pre-commit): autofix * Update planning/behavior_velocity_no_stopping_area_module/src/scene_no_stopping_area.cpp --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Shumpei Wakabayashi <[email protected]> Co-authored-by: kosuke55 <[email protected]> Signed-off-by: Simon Eisenmann <[email protected]>
KhalilSelyan
pushed a commit
that referenced
this pull request
Jul 22, 2024
… detected stop lines are goals (#7280) * Revert "fix(no_stopping_area): fix stopping in front of a no stopping area in parking on the shoulder (#6517)" This reverts commit 144b9c7. * if the stop point is near goal(distance < 1m), no stopping area module does not insert stop line * style(pre-commit): autofix * Update planning/behavior_velocity_no_stopping_area_module/src/scene_no_stopping_area.cpp --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Shumpei Wakabayashi <[email protected]> Co-authored-by: kosuke55 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
component:planning
Route planning, decision-making, and navigation. (auto-assigned)
run:build-and-test-differential
Mark to enable build-and-test-differential workflow. (used-by-ci)
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Related PR: #6517
Related Issue: #7081
Related JIRA Tickets: https://tier4.atlassian.net/browse/RT1-6419, https://tier4.atlassian.net/browse/RT1-5039
In the previous PR #6517, I changed source code in the no stopping area module as a temporal solution
to the problem reported and it resulted in the wrong implementation of the module as pointed out in the issue #7081.
For the current PR, I reverted the change of pull/6517 and gave another solution to the original problem.
Detail of the change to solve the problem of PR #6517.
I consulted with @kosuke55 san and gave another solution to the problem of not being able to
enter into the no stopping area when the goal is right behind the no stopping areas.
In
checkStopLinesInNoStoppingArea
ofscene_no_stopping_area_module.cpp
,I inserted the lines of checking if the stop line detected is near 1m of goal or not.
If the first stop line detected inside the predicted path is near goal, then the no stopping area after this change
skips its own process and does not draw a stop line before the no stopping area.
Tests performed
I confirmed the bug reported in JIRA Ticket https://tier4.atlassian.net/browse/RT1-5039 is resolved, using current version of Autoware.
2024/06/11 https://evaluation.tier4.jp/evaluation/reports/0f925436-b286-5c9d-b72d-6977817653c7/?project_id=prd_jt
Effects on system behavior
Before this change and after the change in #6517,
No stopping area module had not distinguished the two cases of stop lines and stuck vehicles beyond the no stopping area,
and also had not took into account the module margin parameters,
stop_line_margin
,stop_margin
andstuck_vehicle_front_margin
.After this change, the module handles the three cases of goals, stop lines other than goals, and stuck vehicles beyond the no stopping area. These behavior for the latter two cases other than goals is compatible with the current documentation for the no stopping area module.
Interface changes
No Interface changed with this PR.
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.