Package Summary
Tags | No category tags. |
Version | 0.47.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-08-16 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Ahmed Ebrahim
- Tomoya Kimura
- Shumpei Wakabayashi
- Takamasa Horibe
- Takayuki Murooka
- Fumiya Watanabe
- Satoshi Ota
Authors
No Drivable Lane
Role
This module plans the velocity of the related part of the path in case there is a no drivable lane referring to it.
A no drivable lane is a lanelet or more that are out of operation design domain (ODD), i.e., the vehicle must not drive autonomously in this lanelet.
A lanelet can be no drivable (out of ODD) due to many reasons, either technical limitations of the SW and/or HW, business requirements, safety considerations, …. etc, or even a combination of those.
Some examples of No Drivable Lanes
- Closed road intentionally, due to construction work for example
- Underpass road that goes under a railway, for safety reasons
- Road with slope/inclination that the vehicle is not be able to drive autonomously due to technical limitations. And lots of other examples.
A lanelet becomes invalid by adding a new tag under the relevant lanelet in the map file <tag k="no_drivable_lane" v="yes"/>
.
The target of this module is to stop the vehicle before entering the no drivable lane (with configurable stop margin) or keep the vehicle stationary if autonomous mode started inside a no drivable lane. Then ask the human driver to take the responsibility of the driving task (Takeover Request / Request to Intervene)
Activation Timing
This function is activated when the lane id of the target path has an no drivable lane label (i.e. the no_drivable_lane
attribute is yes
).
Module Parameters
Parameter | Type | Description |
---|---|---|
stop_margin |
double | [m] margin for ego vehicle to stop before speed_bump |
print_debug_info |
bool | whether debug info will be printed or not |
Inner-workings / Algorithms
- Get no_drivable_lane attribute on the path from lanelet2 map
- The no drivable lane state machine starts in
INIT
state - Get the intersection points between path and no drivable lane polygon
- Assign the state to
APPROACHING
toward a no drivable lane if:- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
stop_margin
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
- Assign the state to
INSIDE_NO_DRIVABLE_LANE
if:- the first point of the ego path is inside the no drivable lane polygon, or
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is less than the
stop_margin
- Assign the state to
STOPPED
when the vehicle is completely stopped
Future Work
- As Request to Intervene API is not implemented yet, this will be handled to notify the driver to takeover the driving task responsibility after the vehicle stops due to
no_drivable_lane
- Handle the case when the vehicle stops before a no drivable lane but part of its footprint intersects with the no drivable lane polygon.
Changelog for package autoware_behavior_velocity_no_drivable_lane_module
0.47.0 (2025-08-11)
- style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- Contributors: Mete Fatih Cırıt
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
- Merge remote-tracking branch 'origin/main' into tmp/notbot/bump_version_base
- fix(behavior_velocity_planner): add missing header (#10561) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- feat(behavior_velocity_planner): only wait for the required subscriptions (#10546)
- Contributors: Masaki Baba, TaikiYamada4, Takayuki Murooka
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
-
Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
-
chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
-
fix(behavior_velocity_planner): planning factor integration (#10292)
- fix: blind_spot
- fix: crosswalk
- fix: detection_area
- fix: intersection
- fix: no_drivable_lane
- fix: no_stopping_area
- fix: run_out
- fix: stop_line
- fix: traffic_light
- fix: virtual_traffic_light
* fix: walk_way ---------
-
feat(Autoware_planning_factor_interface): replace tier4_msgs with autoware_internal_msgs (#10204)
-
Contributors: Hayato Mizushima, Satoshi OTA, Yutaka Kondo, 心刚
0.42.0 (2025-03-03)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat(autoware_utils): replace autoware_universe_utils with autoware_utils (#10191)
- fix: add missing includes to autoware_universe_utils (#10091)
- feat!: replace tier4_planning_msgs/PathWithLaneId with autoware_internal_planning_msgs/PathWithLaneId (#10023)
- Contributors: Fumiya Watanabe, Ryohsuke Mitsudome, 心刚
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
chore(planning): move package directory for planning factor interface (#9948)
- chore: add new package for planning factor interface
- chore(surround_obstacle_checker): update include file
- chore(obstacle_stop_planner): update include file
- chore(obstacle_cruise_planner): update include file
- chore(motion_velocity_planner): update include file
- chore(bpp): update include file
- chore(bvp-common): update include file
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
libboost-dev |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_behavior_velocity_no_drivable_lane_module at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.47.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-08-16 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Ahmed Ebrahim
- Tomoya Kimura
- Shumpei Wakabayashi
- Takamasa Horibe
- Takayuki Murooka
- Fumiya Watanabe
- Satoshi Ota
Authors
No Drivable Lane
Role
This module plans the velocity of the related part of the path in case there is a no drivable lane referring to it.
A no drivable lane is a lanelet or more that are out of operation design domain (ODD), i.e., the vehicle must not drive autonomously in this lanelet.
A lanelet can be no drivable (out of ODD) due to many reasons, either technical limitations of the SW and/or HW, business requirements, safety considerations, …. etc, or even a combination of those.
Some examples of No Drivable Lanes
- Closed road intentionally, due to construction work for example
- Underpass road that goes under a railway, for safety reasons
- Road with slope/inclination that the vehicle is not be able to drive autonomously due to technical limitations. And lots of other examples.
A lanelet becomes invalid by adding a new tag under the relevant lanelet in the map file <tag k="no_drivable_lane" v="yes"/>
.
The target of this module is to stop the vehicle before entering the no drivable lane (with configurable stop margin) or keep the vehicle stationary if autonomous mode started inside a no drivable lane. Then ask the human driver to take the responsibility of the driving task (Takeover Request / Request to Intervene)
Activation Timing
This function is activated when the lane id of the target path has an no drivable lane label (i.e. the no_drivable_lane
attribute is yes
).
Module Parameters
Parameter | Type | Description |
---|---|---|
stop_margin |
double | [m] margin for ego vehicle to stop before speed_bump |
print_debug_info |
bool | whether debug info will be printed or not |
Inner-workings / Algorithms
- Get no_drivable_lane attribute on the path from lanelet2 map
- The no drivable lane state machine starts in
INIT
state - Get the intersection points between path and no drivable lane polygon
- Assign the state to
APPROACHING
toward a no drivable lane if:- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
stop_margin
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
- Assign the state to
INSIDE_NO_DRIVABLE_LANE
if:- the first point of the ego path is inside the no drivable lane polygon, or
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is less than the
stop_margin
- Assign the state to
STOPPED
when the vehicle is completely stopped
Future Work
- As Request to Intervene API is not implemented yet, this will be handled to notify the driver to takeover the driving task responsibility after the vehicle stops due to
no_drivable_lane
- Handle the case when the vehicle stops before a no drivable lane but part of its footprint intersects with the no drivable lane polygon.
Changelog for package autoware_behavior_velocity_no_drivable_lane_module
0.47.0 (2025-08-11)
- style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- Contributors: Mete Fatih Cırıt
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
- Merge remote-tracking branch 'origin/main' into tmp/notbot/bump_version_base
- fix(behavior_velocity_planner): add missing header (#10561) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- feat(behavior_velocity_planner): only wait for the required subscriptions (#10546)
- Contributors: Masaki Baba, TaikiYamada4, Takayuki Murooka
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
-
Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
-
chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
-
fix(behavior_velocity_planner): planning factor integration (#10292)
- fix: blind_spot
- fix: crosswalk
- fix: detection_area
- fix: intersection
- fix: no_drivable_lane
- fix: no_stopping_area
- fix: run_out
- fix: stop_line
- fix: traffic_light
- fix: virtual_traffic_light
* fix: walk_way ---------
-
feat(Autoware_planning_factor_interface): replace tier4_msgs with autoware_internal_msgs (#10204)
-
Contributors: Hayato Mizushima, Satoshi OTA, Yutaka Kondo, 心刚
0.42.0 (2025-03-03)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat(autoware_utils): replace autoware_universe_utils with autoware_utils (#10191)
- fix: add missing includes to autoware_universe_utils (#10091)
- feat!: replace tier4_planning_msgs/PathWithLaneId with autoware_internal_planning_msgs/PathWithLaneId (#10023)
- Contributors: Fumiya Watanabe, Ryohsuke Mitsudome, 心刚
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
chore(planning): move package directory for planning factor interface (#9948)
- chore: add new package for planning factor interface
- chore(surround_obstacle_checker): update include file
- chore(obstacle_stop_planner): update include file
- chore(obstacle_cruise_planner): update include file
- chore(motion_velocity_planner): update include file
- chore(bpp): update include file
- chore(bvp-common): update include file
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
libboost-dev |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_behavior_velocity_no_drivable_lane_module at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.47.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-08-16 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Ahmed Ebrahim
- Tomoya Kimura
- Shumpei Wakabayashi
- Takamasa Horibe
- Takayuki Murooka
- Fumiya Watanabe
- Satoshi Ota
Authors
No Drivable Lane
Role
This module plans the velocity of the related part of the path in case there is a no drivable lane referring to it.
A no drivable lane is a lanelet or more that are out of operation design domain (ODD), i.e., the vehicle must not drive autonomously in this lanelet.
A lanelet can be no drivable (out of ODD) due to many reasons, either technical limitations of the SW and/or HW, business requirements, safety considerations, …. etc, or even a combination of those.
Some examples of No Drivable Lanes
- Closed road intentionally, due to construction work for example
- Underpass road that goes under a railway, for safety reasons
- Road with slope/inclination that the vehicle is not be able to drive autonomously due to technical limitations. And lots of other examples.
A lanelet becomes invalid by adding a new tag under the relevant lanelet in the map file <tag k="no_drivable_lane" v="yes"/>
.
The target of this module is to stop the vehicle before entering the no drivable lane (with configurable stop margin) or keep the vehicle stationary if autonomous mode started inside a no drivable lane. Then ask the human driver to take the responsibility of the driving task (Takeover Request / Request to Intervene)
Activation Timing
This function is activated when the lane id of the target path has an no drivable lane label (i.e. the no_drivable_lane
attribute is yes
).
Module Parameters
Parameter | Type | Description |
---|---|---|
stop_margin |
double | [m] margin for ego vehicle to stop before speed_bump |
print_debug_info |
bool | whether debug info will be printed or not |
Inner-workings / Algorithms
- Get no_drivable_lane attribute on the path from lanelet2 map
- The no drivable lane state machine starts in
INIT
state - Get the intersection points between path and no drivable lane polygon
- Assign the state to
APPROACHING
toward a no drivable lane if:- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
stop_margin
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
- Assign the state to
INSIDE_NO_DRIVABLE_LANE
if:- the first point of the ego path is inside the no drivable lane polygon, or
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is less than the
stop_margin
- Assign the state to
STOPPED
when the vehicle is completely stopped
Future Work
- As Request to Intervene API is not implemented yet, this will be handled to notify the driver to takeover the driving task responsibility after the vehicle stops due to
no_drivable_lane
- Handle the case when the vehicle stops before a no drivable lane but part of its footprint intersects with the no drivable lane polygon.
Changelog for package autoware_behavior_velocity_no_drivable_lane_module
0.47.0 (2025-08-11)
- style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- Contributors: Mete Fatih Cırıt
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
- Merge remote-tracking branch 'origin/main' into tmp/notbot/bump_version_base
- fix(behavior_velocity_planner): add missing header (#10561) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- feat(behavior_velocity_planner): only wait for the required subscriptions (#10546)
- Contributors: Masaki Baba, TaikiYamada4, Takayuki Murooka
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
-
Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
-
chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
-
fix(behavior_velocity_planner): planning factor integration (#10292)
- fix: blind_spot
- fix: crosswalk
- fix: detection_area
- fix: intersection
- fix: no_drivable_lane
- fix: no_stopping_area
- fix: run_out
- fix: stop_line
- fix: traffic_light
- fix: virtual_traffic_light
* fix: walk_way ---------
-
feat(Autoware_planning_factor_interface): replace tier4_msgs with autoware_internal_msgs (#10204)
-
Contributors: Hayato Mizushima, Satoshi OTA, Yutaka Kondo, 心刚
0.42.0 (2025-03-03)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat(autoware_utils): replace autoware_universe_utils with autoware_utils (#10191)
- fix: add missing includes to autoware_universe_utils (#10091)
- feat!: replace tier4_planning_msgs/PathWithLaneId with autoware_internal_planning_msgs/PathWithLaneId (#10023)
- Contributors: Fumiya Watanabe, Ryohsuke Mitsudome, 心刚
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
chore(planning): move package directory for planning factor interface (#9948)
- chore: add new package for planning factor interface
- chore(surround_obstacle_checker): update include file
- chore(obstacle_stop_planner): update include file
- chore(obstacle_cruise_planner): update include file
- chore(motion_velocity_planner): update include file
- chore(bpp): update include file
- chore(bvp-common): update include file
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
libboost-dev |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_behavior_velocity_no_drivable_lane_module at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.47.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-08-16 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Ahmed Ebrahim
- Tomoya Kimura
- Shumpei Wakabayashi
- Takamasa Horibe
- Takayuki Murooka
- Fumiya Watanabe
- Satoshi Ota
Authors
No Drivable Lane
Role
This module plans the velocity of the related part of the path in case there is a no drivable lane referring to it.
A no drivable lane is a lanelet or more that are out of operation design domain (ODD), i.e., the vehicle must not drive autonomously in this lanelet.
A lanelet can be no drivable (out of ODD) due to many reasons, either technical limitations of the SW and/or HW, business requirements, safety considerations, …. etc, or even a combination of those.
Some examples of No Drivable Lanes
- Closed road intentionally, due to construction work for example
- Underpass road that goes under a railway, for safety reasons
- Road with slope/inclination that the vehicle is not be able to drive autonomously due to technical limitations. And lots of other examples.
A lanelet becomes invalid by adding a new tag under the relevant lanelet in the map file <tag k="no_drivable_lane" v="yes"/>
.
The target of this module is to stop the vehicle before entering the no drivable lane (with configurable stop margin) or keep the vehicle stationary if autonomous mode started inside a no drivable lane. Then ask the human driver to take the responsibility of the driving task (Takeover Request / Request to Intervene)
Activation Timing
This function is activated when the lane id of the target path has an no drivable lane label (i.e. the no_drivable_lane
attribute is yes
).
Module Parameters
Parameter | Type | Description |
---|---|---|
stop_margin |
double | [m] margin for ego vehicle to stop before speed_bump |
print_debug_info |
bool | whether debug info will be printed or not |
Inner-workings / Algorithms
- Get no_drivable_lane attribute on the path from lanelet2 map
- The no drivable lane state machine starts in
INIT
state - Get the intersection points between path and no drivable lane polygon
- Assign the state to
APPROACHING
toward a no drivable lane if:- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
stop_margin
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
- Assign the state to
INSIDE_NO_DRIVABLE_LANE
if:- the first point of the ego path is inside the no drivable lane polygon, or
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is less than the
stop_margin
- Assign the state to
STOPPED
when the vehicle is completely stopped
Future Work
- As Request to Intervene API is not implemented yet, this will be handled to notify the driver to takeover the driving task responsibility after the vehicle stops due to
no_drivable_lane
- Handle the case when the vehicle stops before a no drivable lane but part of its footprint intersects with the no drivable lane polygon.
Changelog for package autoware_behavior_velocity_no_drivable_lane_module
0.47.0 (2025-08-11)
- style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- Contributors: Mete Fatih Cırıt
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
- Merge remote-tracking branch 'origin/main' into tmp/notbot/bump_version_base
- fix(behavior_velocity_planner): add missing header (#10561) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- feat(behavior_velocity_planner): only wait for the required subscriptions (#10546)
- Contributors: Masaki Baba, TaikiYamada4, Takayuki Murooka
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
-
Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
-
chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
-
fix(behavior_velocity_planner): planning factor integration (#10292)
- fix: blind_spot
- fix: crosswalk
- fix: detection_area
- fix: intersection
- fix: no_drivable_lane
- fix: no_stopping_area
- fix: run_out
- fix: stop_line
- fix: traffic_light
- fix: virtual_traffic_light
* fix: walk_way ---------
-
feat(Autoware_planning_factor_interface): replace tier4_msgs with autoware_internal_msgs (#10204)
-
Contributors: Hayato Mizushima, Satoshi OTA, Yutaka Kondo, 心刚
0.42.0 (2025-03-03)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat(autoware_utils): replace autoware_universe_utils with autoware_utils (#10191)
- fix: add missing includes to autoware_universe_utils (#10091)
- feat!: replace tier4_planning_msgs/PathWithLaneId with autoware_internal_planning_msgs/PathWithLaneId (#10023)
- Contributors: Fumiya Watanabe, Ryohsuke Mitsudome, 心刚
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
chore(planning): move package directory for planning factor interface (#9948)
- chore: add new package for planning factor interface
- chore(surround_obstacle_checker): update include file
- chore(obstacle_stop_planner): update include file
- chore(obstacle_cruise_planner): update include file
- chore(motion_velocity_planner): update include file
- chore(bpp): update include file
- chore(bvp-common): update include file
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
libboost-dev |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_behavior_velocity_no_drivable_lane_module at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.47.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-08-16 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Ahmed Ebrahim
- Tomoya Kimura
- Shumpei Wakabayashi
- Takamasa Horibe
- Takayuki Murooka
- Fumiya Watanabe
- Satoshi Ota
Authors
No Drivable Lane
Role
This module plans the velocity of the related part of the path in case there is a no drivable lane referring to it.
A no drivable lane is a lanelet or more that are out of operation design domain (ODD), i.e., the vehicle must not drive autonomously in this lanelet.
A lanelet can be no drivable (out of ODD) due to many reasons, either technical limitations of the SW and/or HW, business requirements, safety considerations, …. etc, or even a combination of those.
Some examples of No Drivable Lanes
- Closed road intentionally, due to construction work for example
- Underpass road that goes under a railway, for safety reasons
- Road with slope/inclination that the vehicle is not be able to drive autonomously due to technical limitations. And lots of other examples.
A lanelet becomes invalid by adding a new tag under the relevant lanelet in the map file <tag k="no_drivable_lane" v="yes"/>
.
The target of this module is to stop the vehicle before entering the no drivable lane (with configurable stop margin) or keep the vehicle stationary if autonomous mode started inside a no drivable lane. Then ask the human driver to take the responsibility of the driving task (Takeover Request / Request to Intervene)
Activation Timing
This function is activated when the lane id of the target path has an no drivable lane label (i.e. the no_drivable_lane
attribute is yes
).
Module Parameters
Parameter | Type | Description |
---|---|---|
stop_margin |
double | [m] margin for ego vehicle to stop before speed_bump |
print_debug_info |
bool | whether debug info will be printed or not |
Inner-workings / Algorithms
- Get no_drivable_lane attribute on the path from lanelet2 map
- The no drivable lane state machine starts in
INIT
state - Get the intersection points between path and no drivable lane polygon
- Assign the state to
APPROACHING
toward a no drivable lane if:- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
stop_margin
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
- Assign the state to
INSIDE_NO_DRIVABLE_LANE
if:- the first point of the ego path is inside the no drivable lane polygon, or
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is less than the
stop_margin
- Assign the state to
STOPPED
when the vehicle is completely stopped
Future Work
- As Request to Intervene API is not implemented yet, this will be handled to notify the driver to takeover the driving task responsibility after the vehicle stops due to
no_drivable_lane
- Handle the case when the vehicle stops before a no drivable lane but part of its footprint intersects with the no drivable lane polygon.
Changelog for package autoware_behavior_velocity_no_drivable_lane_module
0.47.0 (2025-08-11)
- style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- Contributors: Mete Fatih Cırıt
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
- Merge remote-tracking branch 'origin/main' into tmp/notbot/bump_version_base
- fix(behavior_velocity_planner): add missing header (#10561) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- feat(behavior_velocity_planner): only wait for the required subscriptions (#10546)
- Contributors: Masaki Baba, TaikiYamada4, Takayuki Murooka
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
-
Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
-
chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
-
fix(behavior_velocity_planner): planning factor integration (#10292)
- fix: blind_spot
- fix: crosswalk
- fix: detection_area
- fix: intersection
- fix: no_drivable_lane
- fix: no_stopping_area
- fix: run_out
- fix: stop_line
- fix: traffic_light
- fix: virtual_traffic_light
* fix: walk_way ---------
-
feat(Autoware_planning_factor_interface): replace tier4_msgs with autoware_internal_msgs (#10204)
-
Contributors: Hayato Mizushima, Satoshi OTA, Yutaka Kondo, 心刚
0.42.0 (2025-03-03)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat(autoware_utils): replace autoware_universe_utils with autoware_utils (#10191)
- fix: add missing includes to autoware_universe_utils (#10091)
- feat!: replace tier4_planning_msgs/PathWithLaneId with autoware_internal_planning_msgs/PathWithLaneId (#10023)
- Contributors: Fumiya Watanabe, Ryohsuke Mitsudome, 心刚
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
chore(planning): move package directory for planning factor interface (#9948)
- chore: add new package for planning factor interface
- chore(surround_obstacle_checker): update include file
- chore(obstacle_stop_planner): update include file
- chore(obstacle_cruise_planner): update include file
- chore(motion_velocity_planner): update include file
- chore(bpp): update include file
- chore(bvp-common): update include file
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
libboost-dev |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_behavior_velocity_no_drivable_lane_module at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.47.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-08-16 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Ahmed Ebrahim
- Tomoya Kimura
- Shumpei Wakabayashi
- Takamasa Horibe
- Takayuki Murooka
- Fumiya Watanabe
- Satoshi Ota
Authors
No Drivable Lane
Role
This module plans the velocity of the related part of the path in case there is a no drivable lane referring to it.
A no drivable lane is a lanelet or more that are out of operation design domain (ODD), i.e., the vehicle must not drive autonomously in this lanelet.
A lanelet can be no drivable (out of ODD) due to many reasons, either technical limitations of the SW and/or HW, business requirements, safety considerations, …. etc, or even a combination of those.
Some examples of No Drivable Lanes
- Closed road intentionally, due to construction work for example
- Underpass road that goes under a railway, for safety reasons
- Road with slope/inclination that the vehicle is not be able to drive autonomously due to technical limitations. And lots of other examples.
A lanelet becomes invalid by adding a new tag under the relevant lanelet in the map file <tag k="no_drivable_lane" v="yes"/>
.
The target of this module is to stop the vehicle before entering the no drivable lane (with configurable stop margin) or keep the vehicle stationary if autonomous mode started inside a no drivable lane. Then ask the human driver to take the responsibility of the driving task (Takeover Request / Request to Intervene)
Activation Timing
This function is activated when the lane id of the target path has an no drivable lane label (i.e. the no_drivable_lane
attribute is yes
).
Module Parameters
Parameter | Type | Description |
---|---|---|
stop_margin |
double | [m] margin for ego vehicle to stop before speed_bump |
print_debug_info |
bool | whether debug info will be printed or not |
Inner-workings / Algorithms
- Get no_drivable_lane attribute on the path from lanelet2 map
- The no drivable lane state machine starts in
INIT
state - Get the intersection points between path and no drivable lane polygon
- Assign the state to
APPROACHING
toward a no drivable lane if:- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
stop_margin
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
- Assign the state to
INSIDE_NO_DRIVABLE_LANE
if:- the first point of the ego path is inside the no drivable lane polygon, or
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is less than the
stop_margin
- Assign the state to
STOPPED
when the vehicle is completely stopped
Future Work
- As Request to Intervene API is not implemented yet, this will be handled to notify the driver to takeover the driving task responsibility after the vehicle stops due to
no_drivable_lane
- Handle the case when the vehicle stops before a no drivable lane but part of its footprint intersects with the no drivable lane polygon.
Changelog for package autoware_behavior_velocity_no_drivable_lane_module
0.47.0 (2025-08-11)
- style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- Contributors: Mete Fatih Cırıt
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
- Merge remote-tracking branch 'origin/main' into tmp/notbot/bump_version_base
- fix(behavior_velocity_planner): add missing header (#10561) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- feat(behavior_velocity_planner): only wait for the required subscriptions (#10546)
- Contributors: Masaki Baba, TaikiYamada4, Takayuki Murooka
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
-
Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
-
chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
-
fix(behavior_velocity_planner): planning factor integration (#10292)
- fix: blind_spot
- fix: crosswalk
- fix: detection_area
- fix: intersection
- fix: no_drivable_lane
- fix: no_stopping_area
- fix: run_out
- fix: stop_line
- fix: traffic_light
- fix: virtual_traffic_light
* fix: walk_way ---------
-
feat(Autoware_planning_factor_interface): replace tier4_msgs with autoware_internal_msgs (#10204)
-
Contributors: Hayato Mizushima, Satoshi OTA, Yutaka Kondo, 心刚
0.42.0 (2025-03-03)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat(autoware_utils): replace autoware_universe_utils with autoware_utils (#10191)
- fix: add missing includes to autoware_universe_utils (#10091)
- feat!: replace tier4_planning_msgs/PathWithLaneId with autoware_internal_planning_msgs/PathWithLaneId (#10023)
- Contributors: Fumiya Watanabe, Ryohsuke Mitsudome, 心刚
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
chore(planning): move package directory for planning factor interface (#9948)
- chore: add new package for planning factor interface
- chore(surround_obstacle_checker): update include file
- chore(obstacle_stop_planner): update include file
- chore(obstacle_cruise_planner): update include file
- chore(motion_velocity_planner): update include file
- chore(bpp): update include file
- chore(bvp-common): update include file
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
libboost-dev |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_behavior_velocity_no_drivable_lane_module at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.47.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-08-16 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Ahmed Ebrahim
- Tomoya Kimura
- Shumpei Wakabayashi
- Takamasa Horibe
- Takayuki Murooka
- Fumiya Watanabe
- Satoshi Ota
Authors
No Drivable Lane
Role
This module plans the velocity of the related part of the path in case there is a no drivable lane referring to it.
A no drivable lane is a lanelet or more that are out of operation design domain (ODD), i.e., the vehicle must not drive autonomously in this lanelet.
A lanelet can be no drivable (out of ODD) due to many reasons, either technical limitations of the SW and/or HW, business requirements, safety considerations, …. etc, or even a combination of those.
Some examples of No Drivable Lanes
- Closed road intentionally, due to construction work for example
- Underpass road that goes under a railway, for safety reasons
- Road with slope/inclination that the vehicle is not be able to drive autonomously due to technical limitations. And lots of other examples.
A lanelet becomes invalid by adding a new tag under the relevant lanelet in the map file <tag k="no_drivable_lane" v="yes"/>
.
The target of this module is to stop the vehicle before entering the no drivable lane (with configurable stop margin) or keep the vehicle stationary if autonomous mode started inside a no drivable lane. Then ask the human driver to take the responsibility of the driving task (Takeover Request / Request to Intervene)
Activation Timing
This function is activated when the lane id of the target path has an no drivable lane label (i.e. the no_drivable_lane
attribute is yes
).
Module Parameters
Parameter | Type | Description |
---|---|---|
stop_margin |
double | [m] margin for ego vehicle to stop before speed_bump |
print_debug_info |
bool | whether debug info will be printed or not |
Inner-workings / Algorithms
- Get no_drivable_lane attribute on the path from lanelet2 map
- The no drivable lane state machine starts in
INIT
state - Get the intersection points between path and no drivable lane polygon
- Assign the state to
APPROACHING
toward a no drivable lane if:- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
stop_margin
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
- Assign the state to
INSIDE_NO_DRIVABLE_LANE
if:- the first point of the ego path is inside the no drivable lane polygon, or
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is less than the
stop_margin
- Assign the state to
STOPPED
when the vehicle is completely stopped
Future Work
- As Request to Intervene API is not implemented yet, this will be handled to notify the driver to takeover the driving task responsibility after the vehicle stops due to
no_drivable_lane
- Handle the case when the vehicle stops before a no drivable lane but part of its footprint intersects with the no drivable lane polygon.
Changelog for package autoware_behavior_velocity_no_drivable_lane_module
0.47.0 (2025-08-11)
- style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- Contributors: Mete Fatih Cırıt
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
- Merge remote-tracking branch 'origin/main' into tmp/notbot/bump_version_base
- fix(behavior_velocity_planner): add missing header (#10561) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- feat(behavior_velocity_planner): only wait for the required subscriptions (#10546)
- Contributors: Masaki Baba, TaikiYamada4, Takayuki Murooka
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
-
Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
-
chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
-
fix(behavior_velocity_planner): planning factor integration (#10292)
- fix: blind_spot
- fix: crosswalk
- fix: detection_area
- fix: intersection
- fix: no_drivable_lane
- fix: no_stopping_area
- fix: run_out
- fix: stop_line
- fix: traffic_light
- fix: virtual_traffic_light
* fix: walk_way ---------
-
feat(Autoware_planning_factor_interface): replace tier4_msgs with autoware_internal_msgs (#10204)
-
Contributors: Hayato Mizushima, Satoshi OTA, Yutaka Kondo, 心刚
0.42.0 (2025-03-03)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat(autoware_utils): replace autoware_universe_utils with autoware_utils (#10191)
- fix: add missing includes to autoware_universe_utils (#10091)
- feat!: replace tier4_planning_msgs/PathWithLaneId with autoware_internal_planning_msgs/PathWithLaneId (#10023)
- Contributors: Fumiya Watanabe, Ryohsuke Mitsudome, 心刚
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
chore(planning): move package directory for planning factor interface (#9948)
- chore: add new package for planning factor interface
- chore(surround_obstacle_checker): update include file
- chore(obstacle_stop_planner): update include file
- chore(obstacle_cruise_planner): update include file
- chore(motion_velocity_planner): update include file
- chore(bpp): update include file
- chore(bvp-common): update include file
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
libboost-dev |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_behavior_velocity_no_drivable_lane_module at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.47.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-08-16 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Ahmed Ebrahim
- Tomoya Kimura
- Shumpei Wakabayashi
- Takamasa Horibe
- Takayuki Murooka
- Fumiya Watanabe
- Satoshi Ota
Authors
No Drivable Lane
Role
This module plans the velocity of the related part of the path in case there is a no drivable lane referring to it.
A no drivable lane is a lanelet or more that are out of operation design domain (ODD), i.e., the vehicle must not drive autonomously in this lanelet.
A lanelet can be no drivable (out of ODD) due to many reasons, either technical limitations of the SW and/or HW, business requirements, safety considerations, …. etc, or even a combination of those.
Some examples of No Drivable Lanes
- Closed road intentionally, due to construction work for example
- Underpass road that goes under a railway, for safety reasons
- Road with slope/inclination that the vehicle is not be able to drive autonomously due to technical limitations. And lots of other examples.
A lanelet becomes invalid by adding a new tag under the relevant lanelet in the map file <tag k="no_drivable_lane" v="yes"/>
.
The target of this module is to stop the vehicle before entering the no drivable lane (with configurable stop margin) or keep the vehicle stationary if autonomous mode started inside a no drivable lane. Then ask the human driver to take the responsibility of the driving task (Takeover Request / Request to Intervene)
Activation Timing
This function is activated when the lane id of the target path has an no drivable lane label (i.e. the no_drivable_lane
attribute is yes
).
Module Parameters
Parameter | Type | Description |
---|---|---|
stop_margin |
double | [m] margin for ego vehicle to stop before speed_bump |
print_debug_info |
bool | whether debug info will be printed or not |
Inner-workings / Algorithms
- Get no_drivable_lane attribute on the path from lanelet2 map
- The no drivable lane state machine starts in
INIT
state - Get the intersection points between path and no drivable lane polygon
- Assign the state to
APPROACHING
toward a no drivable lane if:- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
stop_margin
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
- Assign the state to
INSIDE_NO_DRIVABLE_LANE
if:- the first point of the ego path is inside the no drivable lane polygon, or
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is less than the
stop_margin
- Assign the state to
STOPPED
when the vehicle is completely stopped
Future Work
- As Request to Intervene API is not implemented yet, this will be handled to notify the driver to takeover the driving task responsibility after the vehicle stops due to
no_drivable_lane
- Handle the case when the vehicle stops before a no drivable lane but part of its footprint intersects with the no drivable lane polygon.
Changelog for package autoware_behavior_velocity_no_drivable_lane_module
0.47.0 (2025-08-11)
- style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- Contributors: Mete Fatih Cırıt
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
- Merge remote-tracking branch 'origin/main' into tmp/notbot/bump_version_base
- fix(behavior_velocity_planner): add missing header (#10561) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- feat(behavior_velocity_planner): only wait for the required subscriptions (#10546)
- Contributors: Masaki Baba, TaikiYamada4, Takayuki Murooka
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
-
Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
-
chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
-
fix(behavior_velocity_planner): planning factor integration (#10292)
- fix: blind_spot
- fix: crosswalk
- fix: detection_area
- fix: intersection
- fix: no_drivable_lane
- fix: no_stopping_area
- fix: run_out
- fix: stop_line
- fix: traffic_light
- fix: virtual_traffic_light
* fix: walk_way ---------
-
feat(Autoware_planning_factor_interface): replace tier4_msgs with autoware_internal_msgs (#10204)
-
Contributors: Hayato Mizushima, Satoshi OTA, Yutaka Kondo, 心刚
0.42.0 (2025-03-03)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat(autoware_utils): replace autoware_universe_utils with autoware_utils (#10191)
- fix: add missing includes to autoware_universe_utils (#10091)
- feat!: replace tier4_planning_msgs/PathWithLaneId with autoware_internal_planning_msgs/PathWithLaneId (#10023)
- Contributors: Fumiya Watanabe, Ryohsuke Mitsudome, 心刚
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
chore(planning): move package directory for planning factor interface (#9948)
- chore: add new package for planning factor interface
- chore(surround_obstacle_checker): update include file
- chore(obstacle_stop_planner): update include file
- chore(obstacle_cruise_planner): update include file
- chore(motion_velocity_planner): update include file
- chore(bpp): update include file
- chore(bvp-common): update include file
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
libboost-dev |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_behavior_velocity_no_drivable_lane_module at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.47.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-08-16 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Ahmed Ebrahim
- Tomoya Kimura
- Shumpei Wakabayashi
- Takamasa Horibe
- Takayuki Murooka
- Fumiya Watanabe
- Satoshi Ota
Authors
No Drivable Lane
Role
This module plans the velocity of the related part of the path in case there is a no drivable lane referring to it.
A no drivable lane is a lanelet or more that are out of operation design domain (ODD), i.e., the vehicle must not drive autonomously in this lanelet.
A lanelet can be no drivable (out of ODD) due to many reasons, either technical limitations of the SW and/or HW, business requirements, safety considerations, …. etc, or even a combination of those.
Some examples of No Drivable Lanes
- Closed road intentionally, due to construction work for example
- Underpass road that goes under a railway, for safety reasons
- Road with slope/inclination that the vehicle is not be able to drive autonomously due to technical limitations. And lots of other examples.
A lanelet becomes invalid by adding a new tag under the relevant lanelet in the map file <tag k="no_drivable_lane" v="yes"/>
.
The target of this module is to stop the vehicle before entering the no drivable lane (with configurable stop margin) or keep the vehicle stationary if autonomous mode started inside a no drivable lane. Then ask the human driver to take the responsibility of the driving task (Takeover Request / Request to Intervene)
Activation Timing
This function is activated when the lane id of the target path has an no drivable lane label (i.e. the no_drivable_lane
attribute is yes
).
Module Parameters
Parameter | Type | Description |
---|---|---|
stop_margin |
double | [m] margin for ego vehicle to stop before speed_bump |
print_debug_info |
bool | whether debug info will be printed or not |
Inner-workings / Algorithms
- Get no_drivable_lane attribute on the path from lanelet2 map
- The no drivable lane state machine starts in
INIT
state - Get the intersection points between path and no drivable lane polygon
- Assign the state to
APPROACHING
toward a no drivable lane if:- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
stop_margin
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is more than the
- Assign the state to
INSIDE_NO_DRIVABLE_LANE
if:- the first point of the ego path is inside the no drivable lane polygon, or
- the distance from front of the ego vehicle till the first intersection point between the ego path and the no drivable lane polygon is less than the
stop_margin
- Assign the state to
STOPPED
when the vehicle is completely stopped
Future Work
- As Request to Intervene API is not implemented yet, this will be handled to notify the driver to takeover the driving task responsibility after the vehicle stops due to
no_drivable_lane
- Handle the case when the vehicle stops before a no drivable lane but part of its footprint intersects with the no drivable lane polygon.
Changelog for package autoware_behavior_velocity_no_drivable_lane_module
0.47.0 (2025-08-11)
- style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- Contributors: Mete Fatih Cırıt
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
- Merge remote-tracking branch 'origin/main' into tmp/notbot/bump_version_base
- fix(behavior_velocity_planner): add missing header (#10561) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
- feat(behavior_velocity_planner): only wait for the required subscriptions (#10546)
- Contributors: Masaki Baba, TaikiYamada4, Takayuki Murooka
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
-
Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
-
chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
-
fix(behavior_velocity_planner): planning factor integration (#10292)
- fix: blind_spot
- fix: crosswalk
- fix: detection_area
- fix: intersection
- fix: no_drivable_lane
- fix: no_stopping_area
- fix: run_out
- fix: stop_line
- fix: traffic_light
- fix: virtual_traffic_light
* fix: walk_way ---------
-
feat(Autoware_planning_factor_interface): replace tier4_msgs with autoware_internal_msgs (#10204)
-
Contributors: Hayato Mizushima, Satoshi OTA, Yutaka Kondo, 心刚
0.42.0 (2025-03-03)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat(autoware_utils): replace autoware_universe_utils with autoware_utils (#10191)
- fix: add missing includes to autoware_universe_utils (#10091)
- feat!: replace tier4_planning_msgs/PathWithLaneId with autoware_internal_planning_msgs/PathWithLaneId (#10023)
- Contributors: Fumiya Watanabe, Ryohsuke Mitsudome, 心刚
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
chore(planning): move package directory for planning factor interface (#9948)
- chore: add new package for planning factor interface
- chore(surround_obstacle_checker): update include file
- chore(obstacle_stop_planner): update include file
- chore(obstacle_cruise_planner): update include file
- chore(motion_velocity_planner): update include file
- chore(bpp): update include file
- chore(bvp-common): update include file
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
libboost-dev |