Package Summary
| Tags | No category tags. |
| Version | 1.4.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_core.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-10-23 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| 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
- Satoshi Ota
- Mamoru Sobue
Authors
- Satoshi Ota
autoware_planning_factor_interface
Overview
The PlanningFactorInterface is a C++ class designed to facilitate the addition and publication of planning factors.
Design
The PlanningFactorInterface class is designed to be lightweight and efficient, with the following key components:
-
Add: Methods to add planning factors to the interface.
-
Publisher: The class includes a publisher for
PlanningFactorArraymessages, which are used to distribute planning factors to other nodes in the system.
The design emphasizes flexibility and ease of use, allowing developers to quickly integrate new planning factors into autoware.
Usage
Including the Header
To use the PlanningFactorInterface, include the header file in your code:
#include <autoware/planning_factor_interface/planning_factor_interface.hpp>
Creating an Instance
Instantiate the PlanningFactorInterface by providing a node and a name for the factor module:
class AvoidancePlanner
{
public:
AvoidancePlanner(rclcpp::Node & node)
: planning_factor_interface_{std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner")}
You can also enable console output for debugging by setting the appropriate parameters:
// Enable console output with a 1000ms throttle duration
planning_factor_interface_ = std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner", true, 1000);
Adding Planning Factors
planning_factor_interface_->add(
traj_points, ego_pose, stop_pose,
autoware_internal_planning_msgs::msg::PlanningFactor::NONE,
autoware_internal_planning_msgs::msg::SafetyFactorArray{});
Publishing Factors
After adding planning factors, you can publish them by calling the publish method:
// Publish the added factors
planning_factor_interface_->publish();
Changelog for package autoware_planning_factor_interface
1.1.0 (2025-05-01)
1.4.0 (2025-08-11)
- chore: bump version to 1.3.0 (#554)
- Contributors: Ryohsuke Mitsudome
1.3.0 (2025-06-23)
- fix: to be consistent version in all package.xml(s)
- feat(planning_factor): add console output option (#513) fix param json fix param json snake_case set default
- feat!: remove obstacle_stop_planner and obstacle_cruise_planner
(#495)
- feat: remove obstacle_stop_planner and obstacle_cruise_planner
- update
* fix
- fix(autoware_planning_factor_interface): removed unused autoware_utils (#440) removed unused autoware_utils Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
- chore: bump up version to 1.1.0 (#462) (#464)
- Contributors: Kosuke Takeuchi, Masaki Baba, Takayuki Murooka, Yutaka Kondo, github-actions
1.0.0 (2025-03-31)
-
fix(planning_factor_interface): set control point data independently (#291)
- fix(planning_factor_interface): set shift length properly
* chore: add comment ---------
-
Contributors: Satoshi OTA
0.3.0 (2025-03-21)
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake_auto | |
| autoware_cmake | |
| ament_cmake_ros | |
| ament_lint_auto | |
| autoware_lint_common | |
| autoware_internal_planning_msgs | |
| autoware_motion_utils | |
| autoware_planning_msgs | |
| rclcpp |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_planning_factor_interface at Robotics Stack Exchange
Package Summary
| Tags | No category tags. |
| Version | 1.4.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_core.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-10-23 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| 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
- Satoshi Ota
- Mamoru Sobue
Authors
- Satoshi Ota
autoware_planning_factor_interface
Overview
The PlanningFactorInterface is a C++ class designed to facilitate the addition and publication of planning factors.
Design
The PlanningFactorInterface class is designed to be lightweight and efficient, with the following key components:
-
Add: Methods to add planning factors to the interface.
-
Publisher: The class includes a publisher for
PlanningFactorArraymessages, which are used to distribute planning factors to other nodes in the system.
The design emphasizes flexibility and ease of use, allowing developers to quickly integrate new planning factors into autoware.
Usage
Including the Header
To use the PlanningFactorInterface, include the header file in your code:
#include <autoware/planning_factor_interface/planning_factor_interface.hpp>
Creating an Instance
Instantiate the PlanningFactorInterface by providing a node and a name for the factor module:
class AvoidancePlanner
{
public:
AvoidancePlanner(rclcpp::Node & node)
: planning_factor_interface_{std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner")}
You can also enable console output for debugging by setting the appropriate parameters:
// Enable console output with a 1000ms throttle duration
planning_factor_interface_ = std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner", true, 1000);
Adding Planning Factors
planning_factor_interface_->add(
traj_points, ego_pose, stop_pose,
autoware_internal_planning_msgs::msg::PlanningFactor::NONE,
autoware_internal_planning_msgs::msg::SafetyFactorArray{});
Publishing Factors
After adding planning factors, you can publish them by calling the publish method:
// Publish the added factors
planning_factor_interface_->publish();
Changelog for package autoware_planning_factor_interface
1.1.0 (2025-05-01)
1.4.0 (2025-08-11)
- chore: bump version to 1.3.0 (#554)
- Contributors: Ryohsuke Mitsudome
1.3.0 (2025-06-23)
- fix: to be consistent version in all package.xml(s)
- feat(planning_factor): add console output option (#513) fix param json fix param json snake_case set default
- feat!: remove obstacle_stop_planner and obstacle_cruise_planner
(#495)
- feat: remove obstacle_stop_planner and obstacle_cruise_planner
- update
* fix
- fix(autoware_planning_factor_interface): removed unused autoware_utils (#440) removed unused autoware_utils Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
- chore: bump up version to 1.1.0 (#462) (#464)
- Contributors: Kosuke Takeuchi, Masaki Baba, Takayuki Murooka, Yutaka Kondo, github-actions
1.0.0 (2025-03-31)
-
fix(planning_factor_interface): set control point data independently (#291)
- fix(planning_factor_interface): set shift length properly
* chore: add comment ---------
-
Contributors: Satoshi OTA
0.3.0 (2025-03-21)
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake_auto | |
| autoware_cmake | |
| ament_cmake_ros | |
| ament_lint_auto | |
| autoware_lint_common | |
| autoware_internal_planning_msgs | |
| autoware_motion_utils | |
| autoware_planning_msgs | |
| rclcpp |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_planning_factor_interface at Robotics Stack Exchange
Package Summary
| Tags | No category tags. |
| Version | 1.4.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_core.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-10-23 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| 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
- Satoshi Ota
- Mamoru Sobue
Authors
- Satoshi Ota
autoware_planning_factor_interface
Overview
The PlanningFactorInterface is a C++ class designed to facilitate the addition and publication of planning factors.
Design
The PlanningFactorInterface class is designed to be lightweight and efficient, with the following key components:
-
Add: Methods to add planning factors to the interface.
-
Publisher: The class includes a publisher for
PlanningFactorArraymessages, which are used to distribute planning factors to other nodes in the system.
The design emphasizes flexibility and ease of use, allowing developers to quickly integrate new planning factors into autoware.
Usage
Including the Header
To use the PlanningFactorInterface, include the header file in your code:
#include <autoware/planning_factor_interface/planning_factor_interface.hpp>
Creating an Instance
Instantiate the PlanningFactorInterface by providing a node and a name for the factor module:
class AvoidancePlanner
{
public:
AvoidancePlanner(rclcpp::Node & node)
: planning_factor_interface_{std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner")}
You can also enable console output for debugging by setting the appropriate parameters:
// Enable console output with a 1000ms throttle duration
planning_factor_interface_ = std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner", true, 1000);
Adding Planning Factors
planning_factor_interface_->add(
traj_points, ego_pose, stop_pose,
autoware_internal_planning_msgs::msg::PlanningFactor::NONE,
autoware_internal_planning_msgs::msg::SafetyFactorArray{});
Publishing Factors
After adding planning factors, you can publish them by calling the publish method:
// Publish the added factors
planning_factor_interface_->publish();
Changelog for package autoware_planning_factor_interface
1.1.0 (2025-05-01)
1.4.0 (2025-08-11)
- chore: bump version to 1.3.0 (#554)
- Contributors: Ryohsuke Mitsudome
1.3.0 (2025-06-23)
- fix: to be consistent version in all package.xml(s)
- feat(planning_factor): add console output option (#513) fix param json fix param json snake_case set default
- feat!: remove obstacle_stop_planner and obstacle_cruise_planner
(#495)
- feat: remove obstacle_stop_planner and obstacle_cruise_planner
- update
* fix
- fix(autoware_planning_factor_interface): removed unused autoware_utils (#440) removed unused autoware_utils Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
- chore: bump up version to 1.1.0 (#462) (#464)
- Contributors: Kosuke Takeuchi, Masaki Baba, Takayuki Murooka, Yutaka Kondo, github-actions
1.0.0 (2025-03-31)
-
fix(planning_factor_interface): set control point data independently (#291)
- fix(planning_factor_interface): set shift length properly
* chore: add comment ---------
-
Contributors: Satoshi OTA
0.3.0 (2025-03-21)
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake_auto | |
| autoware_cmake | |
| ament_cmake_ros | |
| ament_lint_auto | |
| autoware_lint_common | |
| autoware_internal_planning_msgs | |
| autoware_motion_utils | |
| autoware_planning_msgs | |
| rclcpp |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_planning_factor_interface at Robotics Stack Exchange
Package Summary
| Tags | No category tags. |
| Version | 1.4.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_core.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-10-23 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| 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
- Satoshi Ota
- Mamoru Sobue
Authors
- Satoshi Ota
autoware_planning_factor_interface
Overview
The PlanningFactorInterface is a C++ class designed to facilitate the addition and publication of planning factors.
Design
The PlanningFactorInterface class is designed to be lightweight and efficient, with the following key components:
-
Add: Methods to add planning factors to the interface.
-
Publisher: The class includes a publisher for
PlanningFactorArraymessages, which are used to distribute planning factors to other nodes in the system.
The design emphasizes flexibility and ease of use, allowing developers to quickly integrate new planning factors into autoware.
Usage
Including the Header
To use the PlanningFactorInterface, include the header file in your code:
#include <autoware/planning_factor_interface/planning_factor_interface.hpp>
Creating an Instance
Instantiate the PlanningFactorInterface by providing a node and a name for the factor module:
class AvoidancePlanner
{
public:
AvoidancePlanner(rclcpp::Node & node)
: planning_factor_interface_{std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner")}
You can also enable console output for debugging by setting the appropriate parameters:
// Enable console output with a 1000ms throttle duration
planning_factor_interface_ = std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner", true, 1000);
Adding Planning Factors
planning_factor_interface_->add(
traj_points, ego_pose, stop_pose,
autoware_internal_planning_msgs::msg::PlanningFactor::NONE,
autoware_internal_planning_msgs::msg::SafetyFactorArray{});
Publishing Factors
After adding planning factors, you can publish them by calling the publish method:
// Publish the added factors
planning_factor_interface_->publish();
Changelog for package autoware_planning_factor_interface
1.1.0 (2025-05-01)
1.4.0 (2025-08-11)
- chore: bump version to 1.3.0 (#554)
- Contributors: Ryohsuke Mitsudome
1.3.0 (2025-06-23)
- fix: to be consistent version in all package.xml(s)
- feat(planning_factor): add console output option (#513) fix param json fix param json snake_case set default
- feat!: remove obstacle_stop_planner and obstacle_cruise_planner
(#495)
- feat: remove obstacle_stop_planner and obstacle_cruise_planner
- update
* fix
- fix(autoware_planning_factor_interface): removed unused autoware_utils (#440) removed unused autoware_utils Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
- chore: bump up version to 1.1.0 (#462) (#464)
- Contributors: Kosuke Takeuchi, Masaki Baba, Takayuki Murooka, Yutaka Kondo, github-actions
1.0.0 (2025-03-31)
-
fix(planning_factor_interface): set control point data independently (#291)
- fix(planning_factor_interface): set shift length properly
* chore: add comment ---------
-
Contributors: Satoshi OTA
0.3.0 (2025-03-21)
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake_auto | |
| autoware_cmake | |
| ament_cmake_ros | |
| ament_lint_auto | |
| autoware_lint_common | |
| autoware_internal_planning_msgs | |
| autoware_motion_utils | |
| autoware_planning_msgs | |
| rclcpp |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_planning_factor_interface at Robotics Stack Exchange
Package Summary
| Tags | No category tags. |
| Version | 1.4.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_core.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-10-23 |
| Dev Status | DEVELOPED |
| 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
- Satoshi Ota
- Mamoru Sobue
Authors
- Satoshi Ota
autoware_planning_factor_interface
Overview
The PlanningFactorInterface is a C++ class designed to facilitate the addition and publication of planning factors.
Design
The PlanningFactorInterface class is designed to be lightweight and efficient, with the following key components:
-
Add: Methods to add planning factors to the interface.
-
Publisher: The class includes a publisher for
PlanningFactorArraymessages, which are used to distribute planning factors to other nodes in the system.
The design emphasizes flexibility and ease of use, allowing developers to quickly integrate new planning factors into autoware.
Usage
Including the Header
To use the PlanningFactorInterface, include the header file in your code:
#include <autoware/planning_factor_interface/planning_factor_interface.hpp>
Creating an Instance
Instantiate the PlanningFactorInterface by providing a node and a name for the factor module:
class AvoidancePlanner
{
public:
AvoidancePlanner(rclcpp::Node & node)
: planning_factor_interface_{std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner")}
You can also enable console output for debugging by setting the appropriate parameters:
// Enable console output with a 1000ms throttle duration
planning_factor_interface_ = std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner", true, 1000);
Adding Planning Factors
planning_factor_interface_->add(
traj_points, ego_pose, stop_pose,
autoware_internal_planning_msgs::msg::PlanningFactor::NONE,
autoware_internal_planning_msgs::msg::SafetyFactorArray{});
Publishing Factors
After adding planning factors, you can publish them by calling the publish method:
// Publish the added factors
planning_factor_interface_->publish();
Changelog for package autoware_planning_factor_interface
1.1.0 (2025-05-01)
1.4.0 (2025-08-11)
- chore: bump version to 1.3.0 (#554)
- Contributors: Ryohsuke Mitsudome
1.3.0 (2025-06-23)
- fix: to be consistent version in all package.xml(s)
- feat(planning_factor): add console output option (#513) fix param json fix param json snake_case set default
- feat!: remove obstacle_stop_planner and obstacle_cruise_planner
(#495)
- feat: remove obstacle_stop_planner and obstacle_cruise_planner
- update
* fix
- fix(autoware_planning_factor_interface): removed unused autoware_utils (#440) removed unused autoware_utils Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
- chore: bump up version to 1.1.0 (#462) (#464)
- Contributors: Kosuke Takeuchi, Masaki Baba, Takayuki Murooka, Yutaka Kondo, github-actions
1.0.0 (2025-03-31)
-
fix(planning_factor_interface): set control point data independently (#291)
- fix(planning_factor_interface): set shift length properly
* chore: add comment ---------
-
Contributors: Satoshi OTA
0.3.0 (2025-03-21)
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake_auto | |
| autoware_cmake | |
| ament_cmake_ros | |
| ament_lint_auto | |
| autoware_lint_common | |
| autoware_internal_planning_msgs | |
| autoware_motion_utils | |
| autoware_planning_msgs | |
| rclcpp |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_planning_factor_interface at Robotics Stack Exchange
Package Summary
| Tags | No category tags. |
| Version | 1.4.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_core.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-10-23 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| 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
- Satoshi Ota
- Mamoru Sobue
Authors
- Satoshi Ota
autoware_planning_factor_interface
Overview
The PlanningFactorInterface is a C++ class designed to facilitate the addition and publication of planning factors.
Design
The PlanningFactorInterface class is designed to be lightweight and efficient, with the following key components:
-
Add: Methods to add planning factors to the interface.
-
Publisher: The class includes a publisher for
PlanningFactorArraymessages, which are used to distribute planning factors to other nodes in the system.
The design emphasizes flexibility and ease of use, allowing developers to quickly integrate new planning factors into autoware.
Usage
Including the Header
To use the PlanningFactorInterface, include the header file in your code:
#include <autoware/planning_factor_interface/planning_factor_interface.hpp>
Creating an Instance
Instantiate the PlanningFactorInterface by providing a node and a name for the factor module:
class AvoidancePlanner
{
public:
AvoidancePlanner(rclcpp::Node & node)
: planning_factor_interface_{std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner")}
You can also enable console output for debugging by setting the appropriate parameters:
// Enable console output with a 1000ms throttle duration
planning_factor_interface_ = std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner", true, 1000);
Adding Planning Factors
planning_factor_interface_->add(
traj_points, ego_pose, stop_pose,
autoware_internal_planning_msgs::msg::PlanningFactor::NONE,
autoware_internal_planning_msgs::msg::SafetyFactorArray{});
Publishing Factors
After adding planning factors, you can publish them by calling the publish method:
// Publish the added factors
planning_factor_interface_->publish();
Changelog for package autoware_planning_factor_interface
1.1.0 (2025-05-01)
1.4.0 (2025-08-11)
- chore: bump version to 1.3.0 (#554)
- Contributors: Ryohsuke Mitsudome
1.3.0 (2025-06-23)
- fix: to be consistent version in all package.xml(s)
- feat(planning_factor): add console output option (#513) fix param json fix param json snake_case set default
- feat!: remove obstacle_stop_planner and obstacle_cruise_planner
(#495)
- feat: remove obstacle_stop_planner and obstacle_cruise_planner
- update
* fix
- fix(autoware_planning_factor_interface): removed unused autoware_utils (#440) removed unused autoware_utils Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
- chore: bump up version to 1.1.0 (#462) (#464)
- Contributors: Kosuke Takeuchi, Masaki Baba, Takayuki Murooka, Yutaka Kondo, github-actions
1.0.0 (2025-03-31)
-
fix(planning_factor_interface): set control point data independently (#291)
- fix(planning_factor_interface): set shift length properly
* chore: add comment ---------
-
Contributors: Satoshi OTA
0.3.0 (2025-03-21)
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake_auto | |
| autoware_cmake | |
| ament_cmake_ros | |
| ament_lint_auto | |
| autoware_lint_common | |
| autoware_internal_planning_msgs | |
| autoware_motion_utils | |
| autoware_planning_msgs | |
| rclcpp |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_planning_factor_interface at Robotics Stack Exchange
Package Summary
| Tags | No category tags. |
| Version | 1.4.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_core.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-10-23 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| 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
- Satoshi Ota
- Mamoru Sobue
Authors
- Satoshi Ota
autoware_planning_factor_interface
Overview
The PlanningFactorInterface is a C++ class designed to facilitate the addition and publication of planning factors.
Design
The PlanningFactorInterface class is designed to be lightweight and efficient, with the following key components:
-
Add: Methods to add planning factors to the interface.
-
Publisher: The class includes a publisher for
PlanningFactorArraymessages, which are used to distribute planning factors to other nodes in the system.
The design emphasizes flexibility and ease of use, allowing developers to quickly integrate new planning factors into autoware.
Usage
Including the Header
To use the PlanningFactorInterface, include the header file in your code:
#include <autoware/planning_factor_interface/planning_factor_interface.hpp>
Creating an Instance
Instantiate the PlanningFactorInterface by providing a node and a name for the factor module:
class AvoidancePlanner
{
public:
AvoidancePlanner(rclcpp::Node & node)
: planning_factor_interface_{std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner")}
You can also enable console output for debugging by setting the appropriate parameters:
// Enable console output with a 1000ms throttle duration
planning_factor_interface_ = std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner", true, 1000);
Adding Planning Factors
planning_factor_interface_->add(
traj_points, ego_pose, stop_pose,
autoware_internal_planning_msgs::msg::PlanningFactor::NONE,
autoware_internal_planning_msgs::msg::SafetyFactorArray{});
Publishing Factors
After adding planning factors, you can publish them by calling the publish method:
// Publish the added factors
planning_factor_interface_->publish();
Changelog for package autoware_planning_factor_interface
1.1.0 (2025-05-01)
1.4.0 (2025-08-11)
- chore: bump version to 1.3.0 (#554)
- Contributors: Ryohsuke Mitsudome
1.3.0 (2025-06-23)
- fix: to be consistent version in all package.xml(s)
- feat(planning_factor): add console output option (#513) fix param json fix param json snake_case set default
- feat!: remove obstacle_stop_planner and obstacle_cruise_planner
(#495)
- feat: remove obstacle_stop_planner and obstacle_cruise_planner
- update
* fix
- fix(autoware_planning_factor_interface): removed unused autoware_utils (#440) removed unused autoware_utils Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
- chore: bump up version to 1.1.0 (#462) (#464)
- Contributors: Kosuke Takeuchi, Masaki Baba, Takayuki Murooka, Yutaka Kondo, github-actions
1.0.0 (2025-03-31)
-
fix(planning_factor_interface): set control point data independently (#291)
- fix(planning_factor_interface): set shift length properly
* chore: add comment ---------
-
Contributors: Satoshi OTA
0.3.0 (2025-03-21)
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake_auto | |
| autoware_cmake | |
| ament_cmake_ros | |
| ament_lint_auto | |
| autoware_lint_common | |
| autoware_internal_planning_msgs | |
| autoware_motion_utils | |
| autoware_planning_msgs | |
| rclcpp |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_planning_factor_interface at Robotics Stack Exchange
Package Summary
| Tags | No category tags. |
| Version | 1.4.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_core.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-10-23 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| 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
- Satoshi Ota
- Mamoru Sobue
Authors
- Satoshi Ota
autoware_planning_factor_interface
Overview
The PlanningFactorInterface is a C++ class designed to facilitate the addition and publication of planning factors.
Design
The PlanningFactorInterface class is designed to be lightweight and efficient, with the following key components:
-
Add: Methods to add planning factors to the interface.
-
Publisher: The class includes a publisher for
PlanningFactorArraymessages, which are used to distribute planning factors to other nodes in the system.
The design emphasizes flexibility and ease of use, allowing developers to quickly integrate new planning factors into autoware.
Usage
Including the Header
To use the PlanningFactorInterface, include the header file in your code:
#include <autoware/planning_factor_interface/planning_factor_interface.hpp>
Creating an Instance
Instantiate the PlanningFactorInterface by providing a node and a name for the factor module:
class AvoidancePlanner
{
public:
AvoidancePlanner(rclcpp::Node & node)
: planning_factor_interface_{std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner")}
You can also enable console output for debugging by setting the appropriate parameters:
// Enable console output with a 1000ms throttle duration
planning_factor_interface_ = std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner", true, 1000);
Adding Planning Factors
planning_factor_interface_->add(
traj_points, ego_pose, stop_pose,
autoware_internal_planning_msgs::msg::PlanningFactor::NONE,
autoware_internal_planning_msgs::msg::SafetyFactorArray{});
Publishing Factors
After adding planning factors, you can publish them by calling the publish method:
// Publish the added factors
planning_factor_interface_->publish();
Changelog for package autoware_planning_factor_interface
1.1.0 (2025-05-01)
1.4.0 (2025-08-11)
- chore: bump version to 1.3.0 (#554)
- Contributors: Ryohsuke Mitsudome
1.3.0 (2025-06-23)
- fix: to be consistent version in all package.xml(s)
- feat(planning_factor): add console output option (#513) fix param json fix param json snake_case set default
- feat!: remove obstacle_stop_planner and obstacle_cruise_planner
(#495)
- feat: remove obstacle_stop_planner and obstacle_cruise_planner
- update
* fix
- fix(autoware_planning_factor_interface): removed unused autoware_utils (#440) removed unused autoware_utils Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
- chore: bump up version to 1.1.0 (#462) (#464)
- Contributors: Kosuke Takeuchi, Masaki Baba, Takayuki Murooka, Yutaka Kondo, github-actions
1.0.0 (2025-03-31)
-
fix(planning_factor_interface): set control point data independently (#291)
- fix(planning_factor_interface): set shift length properly
* chore: add comment ---------
-
Contributors: Satoshi OTA
0.3.0 (2025-03-21)
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake_auto | |
| autoware_cmake | |
| ament_cmake_ros | |
| ament_lint_auto | |
| autoware_lint_common | |
| autoware_internal_planning_msgs | |
| autoware_motion_utils | |
| autoware_planning_msgs | |
| rclcpp |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_planning_factor_interface at Robotics Stack Exchange
Package Summary
| Tags | No category tags. |
| Version | 1.4.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_core.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-10-23 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| 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
- Satoshi Ota
- Mamoru Sobue
Authors
- Satoshi Ota
autoware_planning_factor_interface
Overview
The PlanningFactorInterface is a C++ class designed to facilitate the addition and publication of planning factors.
Design
The PlanningFactorInterface class is designed to be lightweight and efficient, with the following key components:
-
Add: Methods to add planning factors to the interface.
-
Publisher: The class includes a publisher for
PlanningFactorArraymessages, which are used to distribute planning factors to other nodes in the system.
The design emphasizes flexibility and ease of use, allowing developers to quickly integrate new planning factors into autoware.
Usage
Including the Header
To use the PlanningFactorInterface, include the header file in your code:
#include <autoware/planning_factor_interface/planning_factor_interface.hpp>
Creating an Instance
Instantiate the PlanningFactorInterface by providing a node and a name for the factor module:
class AvoidancePlanner
{
public:
AvoidancePlanner(rclcpp::Node & node)
: planning_factor_interface_{std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner")}
You can also enable console output for debugging by setting the appropriate parameters:
// Enable console output with a 1000ms throttle duration
planning_factor_interface_ = std::make_unique<
autoware::planning_factor_interface::PlanningFactorInterface>(
&node, "avoidance_planner", true, 1000);
Adding Planning Factors
planning_factor_interface_->add(
traj_points, ego_pose, stop_pose,
autoware_internal_planning_msgs::msg::PlanningFactor::NONE,
autoware_internal_planning_msgs::msg::SafetyFactorArray{});
Publishing Factors
After adding planning factors, you can publish them by calling the publish method:
// Publish the added factors
planning_factor_interface_->publish();
Changelog for package autoware_planning_factor_interface
1.1.0 (2025-05-01)
1.4.0 (2025-08-11)
- chore: bump version to 1.3.0 (#554)
- Contributors: Ryohsuke Mitsudome
1.3.0 (2025-06-23)
- fix: to be consistent version in all package.xml(s)
- feat(planning_factor): add console output option (#513) fix param json fix param json snake_case set default
- feat!: remove obstacle_stop_planner and obstacle_cruise_planner
(#495)
- feat: remove obstacle_stop_planner and obstacle_cruise_planner
- update
* fix
- fix(autoware_planning_factor_interface): removed unused autoware_utils (#440) removed unused autoware_utils Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
- chore: bump up version to 1.1.0 (#462) (#464)
- Contributors: Kosuke Takeuchi, Masaki Baba, Takayuki Murooka, Yutaka Kondo, github-actions
1.0.0 (2025-03-31)
-
fix(planning_factor_interface): set control point data independently (#291)
- fix(planning_factor_interface): set shift length properly
* chore: add comment ---------
-
Contributors: Satoshi OTA
0.3.0 (2025-03-21)
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake_auto | |
| autoware_cmake | |
| ament_cmake_ros | |
| ament_lint_auto | |
| autoware_lint_common | |
| autoware_internal_planning_msgs | |
| autoware_motion_utils | |
| autoware_planning_msgs | |
| rclcpp |