fix(boundary_departure): disable when autoware disengaged (#10962)#2210
Merged
TaikiYamada4 merged 1 commit intobeta/v0.48from Jul 14, 2025
Merged
Conversation
…undation#10962) fix(boundary_departure): disable when ego is not in autonomous mode Signed-off-by: Zulfaqar Azmi <zulfaqar.azmi@tier4.jp>
|
Thank you for contributing to the Autoware project! 🚧 If your pull request is in progress, switch it to draft mode. Please ensure:
|
|
TaikiYamada4
approved these changes
Jul 14, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When autoware is disengaged, the ego's predicted path behavior is undefined. As shown in the following video. This has caused boundary departure to produce false positive results.
cap-.2025-07-10-22-16-01.mp4
This PR aims to disable boundary departure during autonomous mode.