Package Summary
Tags | No category tags. |
Version | 1.0.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Yukihiro Saito
- Yoshi Ri
Authors
multi_object_tracker
Purpose
The results of the detection are processed by a time series. The main purpose is to give ID and estimate velocity.
Inner-workings / Algorithms
This multi object tracker consists of data association and EKF.
Data association
The data association performs maximum score matching, called min cost max flow problem. In this package, mussp[1] is used as solver. In addition, when associating observations to tracers, data association have gates such as the area of the object from the BEV, Mahalanobis distance, and maximum distance, depending on the class label.
EKF Tracker
Models for pedestrians, bicycles (motorcycles), cars and unknown are available. The pedestrian or bicycle tracker is running at the same time as the respective EKF model in order to enable the transition between pedestrian and bicycle tracking. For big vehicles such as trucks and buses, we have separate models for passenger cars and large vehicles because they are difficult to distinguish from passenger cars and are not stable. Therefore, separate models are prepared for passenger cars and big vehicles, and these models are run at the same time as the respective EKF models to ensure stability.
Inputs / Outputs
Input
Name | Type | Description |
---|---|---|
~/input |
autoware_auto_perception_msgs::msg::DetectedObjects |
obstacles |
Output
Name | Type | Description |
---|---|---|
~/output |
autoware_auto_perception_msgs::msg::TrackedObjects |
modified obstacles |
Parameters
Core Parameters
Node parameters are defined in multi_object_tracker.param.yaml and association parameters are defined in data_association.param.yaml.
Node parameters
Name | Type | Description |
---|---|---|
***_tracker |
string | EKF tracker name for each class |
world_frame_id |
double | object kinematics definition frame |
enable_delay_compensation |
bool | if True, tracker use timers to schedule publishers and use prediction step to extrapolate object state at desired timestamp |
publish_rate |
double | Timer frequency to output with delay compensation |
Association parameters
Name | Type | Description |
---|---|---|
can_assign_matrix |
double | Assignment table for data association |
max_dist_matrix |
double | Maximum distance table for data association |
max_area_matrix |
double | Maximum area table for data association |
min_area_matrix |
double | Minimum area table for data association |
max_rad_matrix |
double | Maximum angle table for data association |
Assumptions / Known limits
<!– Write assumptions and limitations of your implementation.
Example: This algorithm assumes obstacles are not moving, so if they rapidly move after the vehicle started to avoid them, it might collide with them. Also, this algorithm doesn’t care about blind spots. In general, since too close obstacles aren’t visible due to the sensing performance limit, please take enough margin to obstacles.
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
Dependant Packages
Launch files
- launch/multi_object_tracker.launch.xml
-
- input [default: /perception/object_recognition/detection/objects]
- output [default: objects]
- tracker_setting_path [default: $(find-pkg-share multi_object_tracker)/config/multi_object_tracker_node.param.yaml]
- data_association_matrix_path [default: $(find-pkg-share multi_object_tracker)/config/data_association_matrix.param.yaml]
Messages
Services
Plugins
Recent questions tagged multi_object_tracker at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 1.0.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Yukihiro Saito
- Yoshi Ri
Authors
multi_object_tracker
Purpose
The results of the detection are processed by a time series. The main purpose is to give ID and estimate velocity.
Inner-workings / Algorithms
This multi object tracker consists of data association and EKF.
Data association
The data association performs maximum score matching, called min cost max flow problem. In this package, mussp[1] is used as solver. In addition, when associating observations to tracers, data association have gates such as the area of the object from the BEV, Mahalanobis distance, and maximum distance, depending on the class label.
EKF Tracker
Models for pedestrians, bicycles (motorcycles), cars and unknown are available. The pedestrian or bicycle tracker is running at the same time as the respective EKF model in order to enable the transition between pedestrian and bicycle tracking. For big vehicles such as trucks and buses, we have separate models for passenger cars and large vehicles because they are difficult to distinguish from passenger cars and are not stable. Therefore, separate models are prepared for passenger cars and big vehicles, and these models are run at the same time as the respective EKF models to ensure stability.
Inputs / Outputs
Input
Name | Type | Description |
---|---|---|
~/input |
autoware_auto_perception_msgs::msg::DetectedObjects |
obstacles |
Output
Name | Type | Description |
---|---|---|
~/output |
autoware_auto_perception_msgs::msg::TrackedObjects |
modified obstacles |
Parameters
Core Parameters
Node parameters are defined in multi_object_tracker.param.yaml and association parameters are defined in data_association.param.yaml.
Node parameters
Name | Type | Description |
---|---|---|
***_tracker |
string | EKF tracker name for each class |
world_frame_id |
double | object kinematics definition frame |
enable_delay_compensation |
bool | if True, tracker use timers to schedule publishers and use prediction step to extrapolate object state at desired timestamp |
publish_rate |
double | Timer frequency to output with delay compensation |
Association parameters
Name | Type | Description |
---|---|---|
can_assign_matrix |
double | Assignment table for data association |
max_dist_matrix |
double | Maximum distance table for data association |
max_area_matrix |
double | Maximum area table for data association |
min_area_matrix |
double | Minimum area table for data association |
max_rad_matrix |
double | Maximum angle table for data association |
Assumptions / Known limits
<!– Write assumptions and limitations of your implementation.
Example: This algorithm assumes obstacles are not moving, so if they rapidly move after the vehicle started to avoid them, it might collide with them. Also, this algorithm doesn’t care about blind spots. In general, since too close obstacles aren’t visible due to the sensing performance limit, please take enough margin to obstacles.
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
Dependant Packages
Launch files
- launch/multi_object_tracker.launch.xml
-
- input [default: /perception/object_recognition/detection/objects]
- output [default: objects]
- tracker_setting_path [default: $(find-pkg-share multi_object_tracker)/config/multi_object_tracker_node.param.yaml]
- data_association_matrix_path [default: $(find-pkg-share multi_object_tracker)/config/data_association_matrix.param.yaml]
Messages
Services
Plugins
Recent questions tagged multi_object_tracker at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 1.0.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Yukihiro Saito
- Yoshi Ri
Authors
multi_object_tracker
Purpose
The results of the detection are processed by a time series. The main purpose is to give ID and estimate velocity.
Inner-workings / Algorithms
This multi object tracker consists of data association and EKF.
Data association
The data association performs maximum score matching, called min cost max flow problem. In this package, mussp[1] is used as solver. In addition, when associating observations to tracers, data association have gates such as the area of the object from the BEV, Mahalanobis distance, and maximum distance, depending on the class label.
EKF Tracker
Models for pedestrians, bicycles (motorcycles), cars and unknown are available. The pedestrian or bicycle tracker is running at the same time as the respective EKF model in order to enable the transition between pedestrian and bicycle tracking. For big vehicles such as trucks and buses, we have separate models for passenger cars and large vehicles because they are difficult to distinguish from passenger cars and are not stable. Therefore, separate models are prepared for passenger cars and big vehicles, and these models are run at the same time as the respective EKF models to ensure stability.
Inputs / Outputs
Input
Name | Type | Description |
---|---|---|
~/input |
autoware_auto_perception_msgs::msg::DetectedObjects |
obstacles |
Output
Name | Type | Description |
---|---|---|
~/output |
autoware_auto_perception_msgs::msg::TrackedObjects |
modified obstacles |
Parameters
Core Parameters
Node parameters are defined in multi_object_tracker.param.yaml and association parameters are defined in data_association.param.yaml.
Node parameters
Name | Type | Description |
---|---|---|
***_tracker |
string | EKF tracker name for each class |
world_frame_id |
double | object kinematics definition frame |
enable_delay_compensation |
bool | if True, tracker use timers to schedule publishers and use prediction step to extrapolate object state at desired timestamp |
publish_rate |
double | Timer frequency to output with delay compensation |
Association parameters
Name | Type | Description |
---|---|---|
can_assign_matrix |
double | Assignment table for data association |
max_dist_matrix |
double | Maximum distance table for data association |
max_area_matrix |
double | Maximum area table for data association |
min_area_matrix |
double | Minimum area table for data association |
max_rad_matrix |
double | Maximum angle table for data association |
Assumptions / Known limits
<!– Write assumptions and limitations of your implementation.
Example: This algorithm assumes obstacles are not moving, so if they rapidly move after the vehicle started to avoid them, it might collide with them. Also, this algorithm doesn’t care about blind spots. In general, since too close obstacles aren’t visible due to the sensing performance limit, please take enough margin to obstacles.
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
Dependant Packages
Launch files
- launch/multi_object_tracker.launch.xml
-
- input [default: /perception/object_recognition/detection/objects]
- output [default: objects]
- tracker_setting_path [default: $(find-pkg-share multi_object_tracker)/config/multi_object_tracker_node.param.yaml]
- data_association_matrix_path [default: $(find-pkg-share multi_object_tracker)/config/data_association_matrix.param.yaml]
Messages
Services
Plugins
Recent questions tagged multi_object_tracker at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 1.0.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Yukihiro Saito
- Yoshi Ri
Authors
multi_object_tracker
Purpose
The results of the detection are processed by a time series. The main purpose is to give ID and estimate velocity.
Inner-workings / Algorithms
This multi object tracker consists of data association and EKF.
Data association
The data association performs maximum score matching, called min cost max flow problem. In this package, mussp[1] is used as solver. In addition, when associating observations to tracers, data association have gates such as the area of the object from the BEV, Mahalanobis distance, and maximum distance, depending on the class label.
EKF Tracker
Models for pedestrians, bicycles (motorcycles), cars and unknown are available. The pedestrian or bicycle tracker is running at the same time as the respective EKF model in order to enable the transition between pedestrian and bicycle tracking. For big vehicles such as trucks and buses, we have separate models for passenger cars and large vehicles because they are difficult to distinguish from passenger cars and are not stable. Therefore, separate models are prepared for passenger cars and big vehicles, and these models are run at the same time as the respective EKF models to ensure stability.
Inputs / Outputs
Input
Name | Type | Description |
---|---|---|
~/input |
autoware_auto_perception_msgs::msg::DetectedObjects |
obstacles |
Output
Name | Type | Description |
---|---|---|
~/output |
autoware_auto_perception_msgs::msg::TrackedObjects |
modified obstacles |
Parameters
Core Parameters
Node parameters are defined in multi_object_tracker.param.yaml and association parameters are defined in data_association.param.yaml.
Node parameters
Name | Type | Description |
---|---|---|
***_tracker |
string | EKF tracker name for each class |
world_frame_id |
double | object kinematics definition frame |
enable_delay_compensation |
bool | if True, tracker use timers to schedule publishers and use prediction step to extrapolate object state at desired timestamp |
publish_rate |
double | Timer frequency to output with delay compensation |
Association parameters
Name | Type | Description |
---|---|---|
can_assign_matrix |
double | Assignment table for data association |
max_dist_matrix |
double | Maximum distance table for data association |
max_area_matrix |
double | Maximum area table for data association |
min_area_matrix |
double | Minimum area table for data association |
max_rad_matrix |
double | Maximum angle table for data association |
Assumptions / Known limits
<!– Write assumptions and limitations of your implementation.
Example: This algorithm assumes obstacles are not moving, so if they rapidly move after the vehicle started to avoid them, it might collide with them. Also, this algorithm doesn’t care about blind spots. In general, since too close obstacles aren’t visible due to the sensing performance limit, please take enough margin to obstacles.
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
Dependant Packages
Launch files
- launch/multi_object_tracker.launch.xml
-
- input [default: /perception/object_recognition/detection/objects]
- output [default: objects]
- tracker_setting_path [default: $(find-pkg-share multi_object_tracker)/config/multi_object_tracker_node.param.yaml]
- data_association_matrix_path [default: $(find-pkg-share multi_object_tracker)/config/data_association_matrix.param.yaml]
Messages
Services
Plugins
Recent questions tagged multi_object_tracker at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 1.0.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Yukihiro Saito
- Yoshi Ri
Authors
multi_object_tracker
Purpose
The results of the detection are processed by a time series. The main purpose is to give ID and estimate velocity.
Inner-workings / Algorithms
This multi object tracker consists of data association and EKF.
Data association
The data association performs maximum score matching, called min cost max flow problem. In this package, mussp[1] is used as solver. In addition, when associating observations to tracers, data association have gates such as the area of the object from the BEV, Mahalanobis distance, and maximum distance, depending on the class label.
EKF Tracker
Models for pedestrians, bicycles (motorcycles), cars and unknown are available. The pedestrian or bicycle tracker is running at the same time as the respective EKF model in order to enable the transition between pedestrian and bicycle tracking. For big vehicles such as trucks and buses, we have separate models for passenger cars and large vehicles because they are difficult to distinguish from passenger cars and are not stable. Therefore, separate models are prepared for passenger cars and big vehicles, and these models are run at the same time as the respective EKF models to ensure stability.
Inputs / Outputs
Input
Name | Type | Description |
---|---|---|
~/input |
autoware_auto_perception_msgs::msg::DetectedObjects |
obstacles |
Output
Name | Type | Description |
---|---|---|
~/output |
autoware_auto_perception_msgs::msg::TrackedObjects |
modified obstacles |
Parameters
Core Parameters
Node parameters are defined in multi_object_tracker.param.yaml and association parameters are defined in data_association.param.yaml.
Node parameters
Name | Type | Description |
---|---|---|
***_tracker |
string | EKF tracker name for each class |
world_frame_id |
double | object kinematics definition frame |
enable_delay_compensation |
bool | if True, tracker use timers to schedule publishers and use prediction step to extrapolate object state at desired timestamp |
publish_rate |
double | Timer frequency to output with delay compensation |
Association parameters
Name | Type | Description |
---|---|---|
can_assign_matrix |
double | Assignment table for data association |
max_dist_matrix |
double | Maximum distance table for data association |
max_area_matrix |
double | Maximum area table for data association |
min_area_matrix |
double | Minimum area table for data association |
max_rad_matrix |
double | Maximum angle table for data association |
Assumptions / Known limits
<!– Write assumptions and limitations of your implementation.
Example: This algorithm assumes obstacles are not moving, so if they rapidly move after the vehicle started to avoid them, it might collide with them. Also, this algorithm doesn’t care about blind spots. In general, since too close obstacles aren’t visible due to the sensing performance limit, please take enough margin to obstacles.
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
Dependant Packages
Launch files
- launch/multi_object_tracker.launch.xml
-
- input [default: /perception/object_recognition/detection/objects]
- output [default: objects]
- tracker_setting_path [default: $(find-pkg-share multi_object_tracker)/config/multi_object_tracker_node.param.yaml]
- data_association_matrix_path [default: $(find-pkg-share multi_object_tracker)/config/data_association_matrix.param.yaml]
Messages
Services
Plugins
Recent questions tagged multi_object_tracker at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 1.0.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Yukihiro Saito
- Yoshi Ri
Authors
multi_object_tracker
Purpose
The results of the detection are processed by a time series. The main purpose is to give ID and estimate velocity.
Inner-workings / Algorithms
This multi object tracker consists of data association and EKF.
Data association
The data association performs maximum score matching, called min cost max flow problem. In this package, mussp[1] is used as solver. In addition, when associating observations to tracers, data association have gates such as the area of the object from the BEV, Mahalanobis distance, and maximum distance, depending on the class label.
EKF Tracker
Models for pedestrians, bicycles (motorcycles), cars and unknown are available. The pedestrian or bicycle tracker is running at the same time as the respective EKF model in order to enable the transition between pedestrian and bicycle tracking. For big vehicles such as trucks and buses, we have separate models for passenger cars and large vehicles because they are difficult to distinguish from passenger cars and are not stable. Therefore, separate models are prepared for passenger cars and big vehicles, and these models are run at the same time as the respective EKF models to ensure stability.
Inputs / Outputs
Input
Name | Type | Description |
---|---|---|
~/input |
autoware_auto_perception_msgs::msg::DetectedObjects |
obstacles |
Output
Name | Type | Description |
---|---|---|
~/output |
autoware_auto_perception_msgs::msg::TrackedObjects |
modified obstacles |
Parameters
Core Parameters
Node parameters are defined in multi_object_tracker.param.yaml and association parameters are defined in data_association.param.yaml.
Node parameters
Name | Type | Description |
---|---|---|
***_tracker |
string | EKF tracker name for each class |
world_frame_id |
double | object kinematics definition frame |
enable_delay_compensation |
bool | if True, tracker use timers to schedule publishers and use prediction step to extrapolate object state at desired timestamp |
publish_rate |
double | Timer frequency to output with delay compensation |
Association parameters
Name | Type | Description |
---|---|---|
can_assign_matrix |
double | Assignment table for data association |
max_dist_matrix |
double | Maximum distance table for data association |
max_area_matrix |
double | Maximum area table for data association |
min_area_matrix |
double | Minimum area table for data association |
max_rad_matrix |
double | Maximum angle table for data association |
Assumptions / Known limits
<!– Write assumptions and limitations of your implementation.
Example: This algorithm assumes obstacles are not moving, so if they rapidly move after the vehicle started to avoid them, it might collide with them. Also, this algorithm doesn’t care about blind spots. In general, since too close obstacles aren’t visible due to the sensing performance limit, please take enough margin to obstacles.
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
Dependant Packages
Launch files
- launch/multi_object_tracker.launch.xml
-
- input [default: /perception/object_recognition/detection/objects]
- output [default: objects]
- tracker_setting_path [default: $(find-pkg-share multi_object_tracker)/config/multi_object_tracker_node.param.yaml]
- data_association_matrix_path [default: $(find-pkg-share multi_object_tracker)/config/data_association_matrix.param.yaml]
Messages
Services
Plugins
Recent questions tagged multi_object_tracker at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 1.0.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Yukihiro Saito
- Yoshi Ri
Authors
multi_object_tracker
Purpose
The results of the detection are processed by a time series. The main purpose is to give ID and estimate velocity.
Inner-workings / Algorithms
This multi object tracker consists of data association and EKF.
Data association
The data association performs maximum score matching, called min cost max flow problem. In this package, mussp[1] is used as solver. In addition, when associating observations to tracers, data association have gates such as the area of the object from the BEV, Mahalanobis distance, and maximum distance, depending on the class label.
EKF Tracker
Models for pedestrians, bicycles (motorcycles), cars and unknown are available. The pedestrian or bicycle tracker is running at the same time as the respective EKF model in order to enable the transition between pedestrian and bicycle tracking. For big vehicles such as trucks and buses, we have separate models for passenger cars and large vehicles because they are difficult to distinguish from passenger cars and are not stable. Therefore, separate models are prepared for passenger cars and big vehicles, and these models are run at the same time as the respective EKF models to ensure stability.
Inputs / Outputs
Input
Name | Type | Description |
---|---|---|
~/input |
autoware_auto_perception_msgs::msg::DetectedObjects |
obstacles |
Output
Name | Type | Description |
---|---|---|
~/output |
autoware_auto_perception_msgs::msg::TrackedObjects |
modified obstacles |
Parameters
Core Parameters
Node parameters are defined in multi_object_tracker.param.yaml and association parameters are defined in data_association.param.yaml.
Node parameters
Name | Type | Description |
---|---|---|
***_tracker |
string | EKF tracker name for each class |
world_frame_id |
double | object kinematics definition frame |
enable_delay_compensation |
bool | if True, tracker use timers to schedule publishers and use prediction step to extrapolate object state at desired timestamp |
publish_rate |
double | Timer frequency to output with delay compensation |
Association parameters
Name | Type | Description |
---|---|---|
can_assign_matrix |
double | Assignment table for data association |
max_dist_matrix |
double | Maximum distance table for data association |
max_area_matrix |
double | Maximum area table for data association |
min_area_matrix |
double | Minimum area table for data association |
max_rad_matrix |
double | Maximum angle table for data association |
Assumptions / Known limits
<!– Write assumptions and limitations of your implementation.
Example: This algorithm assumes obstacles are not moving, so if they rapidly move after the vehicle started to avoid them, it might collide with them. Also, this algorithm doesn’t care about blind spots. In general, since too close obstacles aren’t visible due to the sensing performance limit, please take enough margin to obstacles.
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
Dependant Packages
Launch files
- launch/multi_object_tracker.launch.xml
-
- input [default: /perception/object_recognition/detection/objects]
- output [default: objects]
- tracker_setting_path [default: $(find-pkg-share multi_object_tracker)/config/multi_object_tracker_node.param.yaml]
- data_association_matrix_path [default: $(find-pkg-share multi_object_tracker)/config/data_association_matrix.param.yaml]
Messages
Services
Plugins
Recent questions tagged multi_object_tracker at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 1.0.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Yukihiro Saito
- Yoshi Ri
Authors
multi_object_tracker
Purpose
The results of the detection are processed by a time series. The main purpose is to give ID and estimate velocity.
Inner-workings / Algorithms
This multi object tracker consists of data association and EKF.
Data association
The data association performs maximum score matching, called min cost max flow problem. In this package, mussp[1] is used as solver. In addition, when associating observations to tracers, data association have gates such as the area of the object from the BEV, Mahalanobis distance, and maximum distance, depending on the class label.
EKF Tracker
Models for pedestrians, bicycles (motorcycles), cars and unknown are available. The pedestrian or bicycle tracker is running at the same time as the respective EKF model in order to enable the transition between pedestrian and bicycle tracking. For big vehicles such as trucks and buses, we have separate models for passenger cars and large vehicles because they are difficult to distinguish from passenger cars and are not stable. Therefore, separate models are prepared for passenger cars and big vehicles, and these models are run at the same time as the respective EKF models to ensure stability.
Inputs / Outputs
Input
Name | Type | Description |
---|---|---|
~/input |
autoware_auto_perception_msgs::msg::DetectedObjects |
obstacles |
Output
Name | Type | Description |
---|---|---|
~/output |
autoware_auto_perception_msgs::msg::TrackedObjects |
modified obstacles |
Parameters
Core Parameters
Node parameters are defined in multi_object_tracker.param.yaml and association parameters are defined in data_association.param.yaml.
Node parameters
Name | Type | Description |
---|---|---|
***_tracker |
string | EKF tracker name for each class |
world_frame_id |
double | object kinematics definition frame |
enable_delay_compensation |
bool | if True, tracker use timers to schedule publishers and use prediction step to extrapolate object state at desired timestamp |
publish_rate |
double | Timer frequency to output with delay compensation |
Association parameters
Name | Type | Description |
---|---|---|
can_assign_matrix |
double | Assignment table for data association |
max_dist_matrix |
double | Maximum distance table for data association |
max_area_matrix |
double | Maximum area table for data association |
min_area_matrix |
double | Minimum area table for data association |
max_rad_matrix |
double | Maximum angle table for data association |
Assumptions / Known limits
<!– Write assumptions and limitations of your implementation.
Example: This algorithm assumes obstacles are not moving, so if they rapidly move after the vehicle started to avoid them, it might collide with them. Also, this algorithm doesn’t care about blind spots. In general, since too close obstacles aren’t visible due to the sensing performance limit, please take enough margin to obstacles.
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
Dependant Packages
Launch files
- launch/multi_object_tracker.launch.xml
-
- input [default: /perception/object_recognition/detection/objects]
- output [default: objects]
- tracker_setting_path [default: $(find-pkg-share multi_object_tracker)/config/multi_object_tracker_node.param.yaml]
- data_association_matrix_path [default: $(find-pkg-share multi_object_tracker)/config/data_association_matrix.param.yaml]
Messages
Services
Plugins
Recent questions tagged multi_object_tracker at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 1.0.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Yukihiro Saito
- Yoshi Ri
Authors
multi_object_tracker
Purpose
The results of the detection are processed by a time series. The main purpose is to give ID and estimate velocity.
Inner-workings / Algorithms
This multi object tracker consists of data association and EKF.
Data association
The data association performs maximum score matching, called min cost max flow problem. In this package, mussp[1] is used as solver. In addition, when associating observations to tracers, data association have gates such as the area of the object from the BEV, Mahalanobis distance, and maximum distance, depending on the class label.
EKF Tracker
Models for pedestrians, bicycles (motorcycles), cars and unknown are available. The pedestrian or bicycle tracker is running at the same time as the respective EKF model in order to enable the transition between pedestrian and bicycle tracking. For big vehicles such as trucks and buses, we have separate models for passenger cars and large vehicles because they are difficult to distinguish from passenger cars and are not stable. Therefore, separate models are prepared for passenger cars and big vehicles, and these models are run at the same time as the respective EKF models to ensure stability.
Inputs / Outputs
Input
Name | Type | Description |
---|---|---|
~/input |
autoware_auto_perception_msgs::msg::DetectedObjects |
obstacles |
Output
Name | Type | Description |
---|---|---|
~/output |
autoware_auto_perception_msgs::msg::TrackedObjects |
modified obstacles |
Parameters
Core Parameters
Node parameters are defined in multi_object_tracker.param.yaml and association parameters are defined in data_association.param.yaml.
Node parameters
Name | Type | Description |
---|---|---|
***_tracker |
string | EKF tracker name for each class |
world_frame_id |
double | object kinematics definition frame |
enable_delay_compensation |
bool | if True, tracker use timers to schedule publishers and use prediction step to extrapolate object state at desired timestamp |
publish_rate |
double | Timer frequency to output with delay compensation |
Association parameters
Name | Type | Description |
---|---|---|
can_assign_matrix |
double | Assignment table for data association |
max_dist_matrix |
double | Maximum distance table for data association |
max_area_matrix |
double | Maximum area table for data association |
min_area_matrix |
double | Minimum area table for data association |
max_rad_matrix |
double | Maximum angle table for data association |
Assumptions / Known limits
<!– Write assumptions and limitations of your implementation.
Example: This algorithm assumes obstacles are not moving, so if they rapidly move after the vehicle started to avoid them, it might collide with them. Also, this algorithm doesn’t care about blind spots. In general, since too close obstacles aren’t visible due to the sensing performance limit, please take enough margin to obstacles.
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
eigen |
Dependant Packages
Launch files
- launch/multi_object_tracker.launch.xml
-
- input [default: /perception/object_recognition/detection/objects]
- output [default: objects]
- tracker_setting_path [default: $(find-pkg-share multi_object_tracker)/config/multi_object_tracker_node.param.yaml]
- data_association_matrix_path [default: $(find-pkg-share multi_object_tracker)/config/data_association_matrix.param.yaml]