We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently Autoware is able to stop by no_drivable_lane(s) and handle routing to avoid them if they exist in the route. However, this routing is considered even if no_drivable_lane module is disabled.
no_drivable_lane(s)
no_drivable_lane
This task is to make the routing for no_drivable_labe considered only if the module is enabled
no_drivable_labe
Add a new parameter that indicates considering routing for no_drivable_lane(s) or not
By proper usage of the proposed parameter :
The text was updated successfully, but these errors were encountered:
ahmeddesokyebrahim
Successfully merging a pull request may close this issue.
Checklist
Description
Currently Autoware is able to stop by
no_drivable_lane(s)
and handle routing to avoid them if they exist in the route.However, this routing is considered even if
no_drivable_lane
module is disabled.Purpose
This task is to make the routing for
no_drivable_labe
considered only if the module is enabledPossible approaches
Add a new parameter that indicates considering routing for
no_drivable_lane(s)
or notDefinition of done
By proper usage of the proposed parameter :
no_drivable_lane
is enabled, the routing s considered to handle them if anyno_drivable_lane
is disabled, the normal shortest path is the only solution available.The text was updated successfully, but these errors were encountered: