-
Notifications
You must be signed in to change notification settings - Fork 683
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
BlindSpotModule setStopLineInx fail #6204
Labels
type:new-feature
New functionalities or additions, feature requests.
Comments
8 tasks
I fixed the blind_spot module in #6405 and confirmed
|
7 tasks
@ahmeddesokyebrahim Could you please confirm if the issue is resolved with @soblin 's PR so that we could close the issue. |
I confirm that the warning message is no longer logged using planning simulator. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Description
Fixes #5539
Currently, we are working on a task for fixing and improving Autoware logging system as Autoware creates a noisy debugging environment, making it challenging to identify and address genuine issues.
For more details about the issue, plan how to tackle it, and linked PR, please have a look here.
For this bug, when using planning simulator, blind spot module throws a warning that is not able to set stop index by the stop pose.
This video demonstrates the issue.
Expected behavior
Blind spot module should be able to set stop line index by stop pose
Actual behavior
Blind spot module is not able to set stop line index by stop pose
Steps to reproduce
You may use the PRs mentioned here for having more comfortable logging messages, if you want.
Versions
No response
Possible causes
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: