Package Summary
Tags | No category tags. |
Version | 1.12.0 |
License | Apache 2 |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Description | autoware.ai perf |
Checkout URI | https://github.com/is-whale/autoware_learn.git |
VCS Type | git |
VCS Version | 1.14 |
Last Updated | 2025-03-14 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Kosuke Murakami
Authors
Naive Motion Prediction
Autoware package for motion prediction.
- From a sourced terminal:
roslaunch naive_motion_predict naive_motion_predict.launch
- From Runtime Manager:
Computing Tab -> Prediction/ Motion Predictor -> naive_motion_predict
Requirements
-
ray_ground_filter
node. -
eucledian_cluster
node. -
/tf
topic.velodyne
toworld
. -
imm_ukf_pda_tracker
node.
Parameters
Launch file available parameters for naive_motion_predict
Parameter | Type | Description |
---|---|---|
input topic |
String | Input topic(type: autoware_msgs::DetectedObjectArray). Default /detection/lidar_tracker/objects . |
interval_sec |
Double | Interval second for prediction. Default 9.22 . |
num_prediction |
Int | The number of prediction this node will make. Default 0.99 . |
sensor_height |
Double | Uses sensor height for visualized path’s height. Default 0.9 . |
Subscribed topics
Topic | Type | Objective |
---|---|---|
/detection/objects |
autoware_msgs::DetectedObjectArray |
The result topic from Autoware Detection stack |
Published topics
Topic | Type | Objective |
---|---|---|
/prediction/objects |
autoware_msgs::DetectedObjectArray |
Added predicted objects to input data.. |
/prediction/motion_predictor/path_markers |
visualization_msgs::MarkerArray |
Visualzing predicted path in ros marker array |
Video
Changelog for package naive_motion_predict
1.11.0 (2019-03-21)
- [fix] not predicting objects at x<=0 or y<=0 (#2122)
- [Feature] costmap generator
(#1774)
-
- Initial commit for visualization package
-
Removal of all visualization messages from perception nodes
-
Visualization dependency removal
-
Launch file modification
-
- Fixes to visualization
-
Error on Clustering CPU
-
Reduce verbosity on markers
-
Publish acceleration and velocity from ukf tracker
-
Remove hardcoded path
-
Updated README
-
updated prototype
-
Prototype update for header and usage
-
Removed unknown label from being reported
-
Updated publishing orientation to match develop
-
- Published all the trackers
-
Added valid field for visualization and future compatibility with ADAS ROI filtering
-
Add simple functions
-
- Reversed back UKF node to develop
-
Formatted speed
-
Refactor codes
-
Make tracking visualization work
-
Relay class info in tracker node
-
Remove dependency to jskbbox and rosmarker in ukf tracker
-
apply rosclang to ukf tracker
-
Refactor codes
-
Revert "apply rosclang to ukf tracker"
-
Revert "Remove dependency to jskbbox and rosmarker in ukf tracker"
-
Revert "Relay class info in tracker node"
-
delete dependency to jsk and remove pointcloud_frame
-
get direction nis
-
set velocity_reliable true in tracker node
-
Add divided function
-
add function
-
Sanity checks
-
Relay all the data from input DetectedObject
-
Divided function work both for immukf and sukf
-
Add comment
-
Refactor codes
-
Pass immukf test
-
make direction assisted tracking work
-
Visualization fixes
-
Refactor codes
-
Tracker Merging step added
-
Added launch file support for merging phase
- lane assisted with sukf
-
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/naive_motion_predict.launch
- Launch file for naive_motion_predict
-
- interval_sec [default: 0.1]
- num_prediction [default: 10]
- sensor_height [default: 2.0]
- filter_out_close_object_threshold [default: 1.5]
- input_topic [default: /detection/objects]
Messages
Services
Plugins
Recent questions tagged naive_motion_predict at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 1.12.0 |
License | Apache 2 |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Description | autoware.ai perf |
Checkout URI | https://github.com/is-whale/autoware_learn.git |
VCS Type | git |
VCS Version | 1.14 |
Last Updated | 2025-03-14 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Kosuke Murakami
Authors
Naive Motion Prediction
Autoware package for motion prediction.
- From a sourced terminal:
roslaunch naive_motion_predict naive_motion_predict.launch
- From Runtime Manager:
Computing Tab -> Prediction/ Motion Predictor -> naive_motion_predict
Requirements
-
ray_ground_filter
node. -
eucledian_cluster
node. -
/tf
topic.velodyne
toworld
. -
imm_ukf_pda_tracker
node.
Parameters
Launch file available parameters for naive_motion_predict
Parameter | Type | Description |
---|---|---|
input topic |
String | Input topic(type: autoware_msgs::DetectedObjectArray). Default /detection/lidar_tracker/objects . |
interval_sec |
Double | Interval second for prediction. Default 9.22 . |
num_prediction |
Int | The number of prediction this node will make. Default 0.99 . |
sensor_height |
Double | Uses sensor height for visualized path’s height. Default 0.9 . |
Subscribed topics
Topic | Type | Objective |
---|---|---|
/detection/objects |
autoware_msgs::DetectedObjectArray |
The result topic from Autoware Detection stack |
Published topics
Topic | Type | Objective |
---|---|---|
/prediction/objects |
autoware_msgs::DetectedObjectArray |
Added predicted objects to input data.. |
/prediction/motion_predictor/path_markers |
visualization_msgs::MarkerArray |
Visualzing predicted path in ros marker array |
Video
Changelog for package naive_motion_predict
1.11.0 (2019-03-21)
- [fix] not predicting objects at x<=0 or y<=0 (#2122)
- [Feature] costmap generator
(#1774)
-
- Initial commit for visualization package
-
Removal of all visualization messages from perception nodes
-
Visualization dependency removal
-
Launch file modification
-
- Fixes to visualization
-
Error on Clustering CPU
-
Reduce verbosity on markers
-
Publish acceleration and velocity from ukf tracker
-
Remove hardcoded path
-
Updated README
-
updated prototype
-
Prototype update for header and usage
-
Removed unknown label from being reported
-
Updated publishing orientation to match develop
-
- Published all the trackers
-
Added valid field for visualization and future compatibility with ADAS ROI filtering
-
Add simple functions
-
- Reversed back UKF node to develop
-
Formatted speed
-
Refactor codes
-
Make tracking visualization work
-
Relay class info in tracker node
-
Remove dependency to jskbbox and rosmarker in ukf tracker
-
apply rosclang to ukf tracker
-
Refactor codes
-
Revert "apply rosclang to ukf tracker"
-
Revert "Remove dependency to jskbbox and rosmarker in ukf tracker"
-
Revert "Relay class info in tracker node"
-
delete dependency to jsk and remove pointcloud_frame
-
get direction nis
-
set velocity_reliable true in tracker node
-
Add divided function
-
add function
-
Sanity checks
-
Relay all the data from input DetectedObject
-
Divided function work both for immukf and sukf
-
Add comment
-
Refactor codes
-
Pass immukf test
-
make direction assisted tracking work
-
Visualization fixes
-
Refactor codes
-
Tracker Merging step added
-
Added launch file support for merging phase
- lane assisted with sukf
-
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/naive_motion_predict.launch
- Launch file for naive_motion_predict
-
- interval_sec [default: 0.1]
- num_prediction [default: 10]
- sensor_height [default: 2.0]
- filter_out_close_object_threshold [default: 1.5]
- input_topic [default: /detection/objects]
Messages
Services
Plugins
Recent questions tagged naive_motion_predict at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 1.12.0 |
License | Apache 2 |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Description | autoware.ai perf |
Checkout URI | https://github.com/is-whale/autoware_learn.git |
VCS Type | git |
VCS Version | 1.14 |
Last Updated | 2025-03-14 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Kosuke Murakami
Authors
Naive Motion Prediction
Autoware package for motion prediction.
- From a sourced terminal:
roslaunch naive_motion_predict naive_motion_predict.launch
- From Runtime Manager:
Computing Tab -> Prediction/ Motion Predictor -> naive_motion_predict
Requirements
-
ray_ground_filter
node. -
eucledian_cluster
node. -
/tf
topic.velodyne
toworld
. -
imm_ukf_pda_tracker
node.
Parameters
Launch file available parameters for naive_motion_predict
Parameter | Type | Description |
---|---|---|
input topic |
String | Input topic(type: autoware_msgs::DetectedObjectArray). Default /detection/lidar_tracker/objects . |
interval_sec |
Double | Interval second for prediction. Default 9.22 . |
num_prediction |
Int | The number of prediction this node will make. Default 0.99 . |
sensor_height |
Double | Uses sensor height for visualized path’s height. Default 0.9 . |
Subscribed topics
Topic | Type | Objective |
---|---|---|
/detection/objects |
autoware_msgs::DetectedObjectArray |
The result topic from Autoware Detection stack |
Published topics
Topic | Type | Objective |
---|---|---|
/prediction/objects |
autoware_msgs::DetectedObjectArray |
Added predicted objects to input data.. |
/prediction/motion_predictor/path_markers |
visualization_msgs::MarkerArray |
Visualzing predicted path in ros marker array |
Video
Changelog for package naive_motion_predict
1.11.0 (2019-03-21)
- [fix] not predicting objects at x<=0 or y<=0 (#2122)
- [Feature] costmap generator
(#1774)
-
- Initial commit for visualization package
-
Removal of all visualization messages from perception nodes
-
Visualization dependency removal
-
Launch file modification
-
- Fixes to visualization
-
Error on Clustering CPU
-
Reduce verbosity on markers
-
Publish acceleration and velocity from ukf tracker
-
Remove hardcoded path
-
Updated README
-
updated prototype
-
Prototype update for header and usage
-
Removed unknown label from being reported
-
Updated publishing orientation to match develop
-
- Published all the trackers
-
Added valid field for visualization and future compatibility with ADAS ROI filtering
-
Add simple functions
-
- Reversed back UKF node to develop
-
Formatted speed
-
Refactor codes
-
Make tracking visualization work
-
Relay class info in tracker node
-
Remove dependency to jskbbox and rosmarker in ukf tracker
-
apply rosclang to ukf tracker
-
Refactor codes
-
Revert "apply rosclang to ukf tracker"
-
Revert "Remove dependency to jskbbox and rosmarker in ukf tracker"
-
Revert "Relay class info in tracker node"
-
delete dependency to jsk and remove pointcloud_frame
-
get direction nis
-
set velocity_reliable true in tracker node
-
Add divided function
-
add function
-
Sanity checks
-
Relay all the data from input DetectedObject
-
Divided function work both for immukf and sukf
-
Add comment
-
Refactor codes
-
Pass immukf test
-
make direction assisted tracking work
-
Visualization fixes
-
Refactor codes
-
Tracker Merging step added
-
Added launch file support for merging phase
- lane assisted with sukf
-
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/naive_motion_predict.launch
- Launch file for naive_motion_predict
-
- interval_sec [default: 0.1]
- num_prediction [default: 10]
- sensor_height [default: 2.0]
- filter_out_close_object_threshold [default: 1.5]
- input_topic [default: /detection/objects]
Messages
Services
Plugins
Recent questions tagged naive_motion_predict at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 1.12.0 |
License | Apache 2 |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Description | autoware.ai perf |
Checkout URI | https://github.com/is-whale/autoware_learn.git |
VCS Type | git |
VCS Version | 1.14 |
Last Updated | 2025-03-14 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Kosuke Murakami
Authors
Naive Motion Prediction
Autoware package for motion prediction.
- From a sourced terminal:
roslaunch naive_motion_predict naive_motion_predict.launch
- From Runtime Manager:
Computing Tab -> Prediction/ Motion Predictor -> naive_motion_predict
Requirements
-
ray_ground_filter
node. -
eucledian_cluster
node. -
/tf
topic.velodyne
toworld
. -
imm_ukf_pda_tracker
node.
Parameters
Launch file available parameters for naive_motion_predict
Parameter | Type | Description |
---|---|---|
input topic |
String | Input topic(type: autoware_msgs::DetectedObjectArray). Default /detection/lidar_tracker/objects . |
interval_sec |
Double | Interval second for prediction. Default 9.22 . |
num_prediction |
Int | The number of prediction this node will make. Default 0.99 . |
sensor_height |
Double | Uses sensor height for visualized path’s height. Default 0.9 . |
Subscribed topics
Topic | Type | Objective |
---|---|---|
/detection/objects |
autoware_msgs::DetectedObjectArray |
The result topic from Autoware Detection stack |
Published topics
Topic | Type | Objective |
---|---|---|
/prediction/objects |
autoware_msgs::DetectedObjectArray |
Added predicted objects to input data.. |
/prediction/motion_predictor/path_markers |
visualization_msgs::MarkerArray |
Visualzing predicted path in ros marker array |
Video
Changelog for package naive_motion_predict
1.11.0 (2019-03-21)
- [fix] not predicting objects at x<=0 or y<=0 (#2122)
- [Feature] costmap generator
(#1774)
-
- Initial commit for visualization package
-
Removal of all visualization messages from perception nodes
-
Visualization dependency removal
-
Launch file modification
-
- Fixes to visualization
-
Error on Clustering CPU
-
Reduce verbosity on markers
-
Publish acceleration and velocity from ukf tracker
-
Remove hardcoded path
-
Updated README
-
updated prototype
-
Prototype update for header and usage
-
Removed unknown label from being reported
-
Updated publishing orientation to match develop
-
- Published all the trackers
-
Added valid field for visualization and future compatibility with ADAS ROI filtering
-
Add simple functions
-
- Reversed back UKF node to develop
-
Formatted speed
-
Refactor codes
-
Make tracking visualization work
-
Relay class info in tracker node
-
Remove dependency to jskbbox and rosmarker in ukf tracker
-
apply rosclang to ukf tracker
-
Refactor codes
-
Revert "apply rosclang to ukf tracker"
-
Revert "Remove dependency to jskbbox and rosmarker in ukf tracker"
-
Revert "Relay class info in tracker node"
-
delete dependency to jsk and remove pointcloud_frame
-
get direction nis
-
set velocity_reliable true in tracker node
-
Add divided function
-
add function
-
Sanity checks
-
Relay all the data from input DetectedObject
-
Divided function work both for immukf and sukf
-
Add comment
-
Refactor codes
-
Pass immukf test
-
make direction assisted tracking work
-
Visualization fixes
-
Refactor codes
-
Tracker Merging step added
-
Added launch file support for merging phase
- lane assisted with sukf
-
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/naive_motion_predict.launch
- Launch file for naive_motion_predict
-
- interval_sec [default: 0.1]
- num_prediction [default: 10]
- sensor_height [default: 2.0]
- filter_out_close_object_threshold [default: 1.5]
- input_topic [default: /detection/objects]
Messages
Services
Plugins
Recent questions tagged naive_motion_predict at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 1.12.0 |
License | Apache 2 |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Description | autoware.ai perf |
Checkout URI | https://github.com/is-whale/autoware_learn.git |
VCS Type | git |
VCS Version | 1.14 |
Last Updated | 2025-03-14 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Kosuke Murakami
Authors
Naive Motion Prediction
Autoware package for motion prediction.
- From a sourced terminal:
roslaunch naive_motion_predict naive_motion_predict.launch
- From Runtime Manager:
Computing Tab -> Prediction/ Motion Predictor -> naive_motion_predict
Requirements
-
ray_ground_filter
node. -
eucledian_cluster
node. -
/tf
topic.velodyne
toworld
. -
imm_ukf_pda_tracker
node.
Parameters
Launch file available parameters for naive_motion_predict
Parameter | Type | Description |
---|---|---|
input topic |
String | Input topic(type: autoware_msgs::DetectedObjectArray). Default /detection/lidar_tracker/objects . |
interval_sec |
Double | Interval second for prediction. Default 9.22 . |
num_prediction |
Int | The number of prediction this node will make. Default 0.99 . |
sensor_height |
Double | Uses sensor height for visualized path’s height. Default 0.9 . |
Subscribed topics
Topic | Type | Objective |
---|---|---|
/detection/objects |
autoware_msgs::DetectedObjectArray |
The result topic from Autoware Detection stack |
Published topics
Topic | Type | Objective |
---|---|---|
/prediction/objects |
autoware_msgs::DetectedObjectArray |
Added predicted objects to input data.. |
/prediction/motion_predictor/path_markers |
visualization_msgs::MarkerArray |
Visualzing predicted path in ros marker array |
Video
Changelog for package naive_motion_predict
1.11.0 (2019-03-21)
- [fix] not predicting objects at x<=0 or y<=0 (#2122)
- [Feature] costmap generator
(#1774)
-
- Initial commit for visualization package
-
Removal of all visualization messages from perception nodes
-
Visualization dependency removal
-
Launch file modification
-
- Fixes to visualization
-
Error on Clustering CPU
-
Reduce verbosity on markers
-
Publish acceleration and velocity from ukf tracker
-
Remove hardcoded path
-
Updated README
-
updated prototype
-
Prototype update for header and usage
-
Removed unknown label from being reported
-
Updated publishing orientation to match develop
-
- Published all the trackers
-
Added valid field for visualization and future compatibility with ADAS ROI filtering
-
Add simple functions
-
- Reversed back UKF node to develop
-
Formatted speed
-
Refactor codes
-
Make tracking visualization work
-
Relay class info in tracker node
-
Remove dependency to jskbbox and rosmarker in ukf tracker
-
apply rosclang to ukf tracker
-
Refactor codes
-
Revert "apply rosclang to ukf tracker"
-
Revert "Remove dependency to jskbbox and rosmarker in ukf tracker"
-
Revert "Relay class info in tracker node"
-
delete dependency to jsk and remove pointcloud_frame
-
get direction nis
-
set velocity_reliable true in tracker node
-
Add divided function
-
add function
-
Sanity checks
-
Relay all the data from input DetectedObject
-
Divided function work both for immukf and sukf
-
Add comment
-
Refactor codes
-
Pass immukf test
-
make direction assisted tracking work
-
Visualization fixes
-
Refactor codes
-
Tracker Merging step added
-
Added launch file support for merging phase
- lane assisted with sukf
-
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/naive_motion_predict.launch
- Launch file for naive_motion_predict
-
- interval_sec [default: 0.1]
- num_prediction [default: 10]
- sensor_height [default: 2.0]
- filter_out_close_object_threshold [default: 1.5]
- input_topic [default: /detection/objects]
Messages
Services
Plugins
Recent questions tagged naive_motion_predict at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 1.12.0 |
License | Apache 2 |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Description | autoware.ai perf |
Checkout URI | https://github.com/is-whale/autoware_learn.git |
VCS Type | git |
VCS Version | 1.14 |
Last Updated | 2025-03-14 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Kosuke Murakami
Authors
Naive Motion Prediction
Autoware package for motion prediction.
- From a sourced terminal:
roslaunch naive_motion_predict naive_motion_predict.launch
- From Runtime Manager:
Computing Tab -> Prediction/ Motion Predictor -> naive_motion_predict
Requirements
-
ray_ground_filter
node. -
eucledian_cluster
node. -
/tf
topic.velodyne
toworld
. -
imm_ukf_pda_tracker
node.
Parameters
Launch file available parameters for naive_motion_predict
Parameter | Type | Description |
---|---|---|
input topic |
String | Input topic(type: autoware_msgs::DetectedObjectArray). Default /detection/lidar_tracker/objects . |
interval_sec |
Double | Interval second for prediction. Default 9.22 . |
num_prediction |
Int | The number of prediction this node will make. Default 0.99 . |
sensor_height |
Double | Uses sensor height for visualized path’s height. Default 0.9 . |
Subscribed topics
Topic | Type | Objective |
---|---|---|
/detection/objects |
autoware_msgs::DetectedObjectArray |
The result topic from Autoware Detection stack |
Published topics
Topic | Type | Objective |
---|---|---|
/prediction/objects |
autoware_msgs::DetectedObjectArray |
Added predicted objects to input data.. |
/prediction/motion_predictor/path_markers |
visualization_msgs::MarkerArray |
Visualzing predicted path in ros marker array |
Video
Changelog for package naive_motion_predict
1.11.0 (2019-03-21)
- [fix] not predicting objects at x<=0 or y<=0 (#2122)
- [Feature] costmap generator
(#1774)
-
- Initial commit for visualization package
-
Removal of all visualization messages from perception nodes
-
Visualization dependency removal
-
Launch file modification
-
- Fixes to visualization
-
Error on Clustering CPU
-
Reduce verbosity on markers
-
Publish acceleration and velocity from ukf tracker
-
Remove hardcoded path
-
Updated README
-
updated prototype
-
Prototype update for header and usage
-
Removed unknown label from being reported
-
Updated publishing orientation to match develop
-
- Published all the trackers
-
Added valid field for visualization and future compatibility with ADAS ROI filtering
-
Add simple functions
-
- Reversed back UKF node to develop
-
Formatted speed
-
Refactor codes
-
Make tracking visualization work
-
Relay class info in tracker node
-
Remove dependency to jskbbox and rosmarker in ukf tracker
-
apply rosclang to ukf tracker
-
Refactor codes
-
Revert "apply rosclang to ukf tracker"
-
Revert "Remove dependency to jskbbox and rosmarker in ukf tracker"
-
Revert "Relay class info in tracker node"
-
delete dependency to jsk and remove pointcloud_frame
-
get direction nis
-
set velocity_reliable true in tracker node
-
Add divided function
-
add function
-
Sanity checks
-
Relay all the data from input DetectedObject
-
Divided function work both for immukf and sukf
-
Add comment
-
Refactor codes
-
Pass immukf test
-
make direction assisted tracking work
-
Visualization fixes
-
Refactor codes
-
Tracker Merging step added
-
Added launch file support for merging phase
- lane assisted with sukf
-
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/naive_motion_predict.launch
- Launch file for naive_motion_predict
-
- interval_sec [default: 0.1]
- num_prediction [default: 10]
- sensor_height [default: 2.0]
- filter_out_close_object_threshold [default: 1.5]
- input_topic [default: /detection/objects]
Messages
Services
Plugins
Recent questions tagged naive_motion_predict at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 1.12.0 |
License | Apache 2 |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Description | autoware.ai perf |
Checkout URI | https://github.com/is-whale/autoware_learn.git |
VCS Type | git |
VCS Version | 1.14 |
Last Updated | 2025-03-14 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Kosuke Murakami
Authors
Naive Motion Prediction
Autoware package for motion prediction.
- From a sourced terminal:
roslaunch naive_motion_predict naive_motion_predict.launch
- From Runtime Manager:
Computing Tab -> Prediction/ Motion Predictor -> naive_motion_predict
Requirements
-
ray_ground_filter
node. -
eucledian_cluster
node. -
/tf
topic.velodyne
toworld
. -
imm_ukf_pda_tracker
node.
Parameters
Launch file available parameters for naive_motion_predict
Parameter | Type | Description |
---|---|---|
input topic |
String | Input topic(type: autoware_msgs::DetectedObjectArray). Default /detection/lidar_tracker/objects . |
interval_sec |
Double | Interval second for prediction. Default 9.22 . |
num_prediction |
Int | The number of prediction this node will make. Default 0.99 . |
sensor_height |
Double | Uses sensor height for visualized path’s height. Default 0.9 . |
Subscribed topics
Topic | Type | Objective |
---|---|---|
/detection/objects |
autoware_msgs::DetectedObjectArray |
The result topic from Autoware Detection stack |
Published topics
Topic | Type | Objective |
---|---|---|
/prediction/objects |
autoware_msgs::DetectedObjectArray |
Added predicted objects to input data.. |
/prediction/motion_predictor/path_markers |
visualization_msgs::MarkerArray |
Visualzing predicted path in ros marker array |
Video
Changelog for package naive_motion_predict
1.11.0 (2019-03-21)
- [fix] not predicting objects at x<=0 or y<=0 (#2122)
- [Feature] costmap generator
(#1774)
-
- Initial commit for visualization package
-
Removal of all visualization messages from perception nodes
-
Visualization dependency removal
-
Launch file modification
-
- Fixes to visualization
-
Error on Clustering CPU
-
Reduce verbosity on markers
-
Publish acceleration and velocity from ukf tracker
-
Remove hardcoded path
-
Updated README
-
updated prototype
-
Prototype update for header and usage
-
Removed unknown label from being reported
-
Updated publishing orientation to match develop
-
- Published all the trackers
-
Added valid field for visualization and future compatibility with ADAS ROI filtering
-
Add simple functions
-
- Reversed back UKF node to develop
-
Formatted speed
-
Refactor codes
-
Make tracking visualization work
-
Relay class info in tracker node
-
Remove dependency to jskbbox and rosmarker in ukf tracker
-
apply rosclang to ukf tracker
-
Refactor codes
-
Revert "apply rosclang to ukf tracker"
-
Revert "Remove dependency to jskbbox and rosmarker in ukf tracker"
-
Revert "Relay class info in tracker node"
-
delete dependency to jsk and remove pointcloud_frame
-
get direction nis
-
set velocity_reliable true in tracker node
-
Add divided function
-
add function
-
Sanity checks
-
Relay all the data from input DetectedObject
-
Divided function work both for immukf and sukf
-
Add comment
-
Refactor codes
-
Pass immukf test
-
make direction assisted tracking work
-
Visualization fixes
-
Refactor codes
-
Tracker Merging step added
-
Added launch file support for merging phase
- lane assisted with sukf
-
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/naive_motion_predict.launch
- Launch file for naive_motion_predict
-
- interval_sec [default: 0.1]
- num_prediction [default: 10]
- sensor_height [default: 2.0]
- filter_out_close_object_threshold [default: 1.5]
- input_topic [default: /detection/objects]
Messages
Services
Plugins
Recent questions tagged naive_motion_predict at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 1.12.0 |
License | Apache 2 |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Description | autoware.ai perf |
Checkout URI | https://github.com/is-whale/autoware_learn.git |
VCS Type | git |
VCS Version | 1.14 |
Last Updated | 2025-03-14 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Kosuke Murakami
Authors
Naive Motion Prediction
Autoware package for motion prediction.
- From a sourced terminal:
roslaunch naive_motion_predict naive_motion_predict.launch
- From Runtime Manager:
Computing Tab -> Prediction/ Motion Predictor -> naive_motion_predict
Requirements
-
ray_ground_filter
node. -
eucledian_cluster
node. -
/tf
topic.velodyne
toworld
. -
imm_ukf_pda_tracker
node.
Parameters
Launch file available parameters for naive_motion_predict
Parameter | Type | Description |
---|---|---|
input topic |
String | Input topic(type: autoware_msgs::DetectedObjectArray). Default /detection/lidar_tracker/objects . |
interval_sec |
Double | Interval second for prediction. Default 9.22 . |
num_prediction |
Int | The number of prediction this node will make. Default 0.99 . |
sensor_height |
Double | Uses sensor height for visualized path’s height. Default 0.9 . |
Subscribed topics
Topic | Type | Objective |
---|---|---|
/detection/objects |
autoware_msgs::DetectedObjectArray |
The result topic from Autoware Detection stack |
Published topics
Topic | Type | Objective |
---|---|---|
/prediction/objects |
autoware_msgs::DetectedObjectArray |
Added predicted objects to input data.. |
/prediction/motion_predictor/path_markers |
visualization_msgs::MarkerArray |
Visualzing predicted path in ros marker array |
Video
Changelog for package naive_motion_predict
1.11.0 (2019-03-21)
- [fix] not predicting objects at x<=0 or y<=0 (#2122)
- [Feature] costmap generator
(#1774)
-
- Initial commit for visualization package
-
Removal of all visualization messages from perception nodes
-
Visualization dependency removal
-
Launch file modification
-
- Fixes to visualization
-
Error on Clustering CPU
-
Reduce verbosity on markers
-
Publish acceleration and velocity from ukf tracker
-
Remove hardcoded path
-
Updated README
-
updated prototype
-
Prototype update for header and usage
-
Removed unknown label from being reported
-
Updated publishing orientation to match develop
-
- Published all the trackers
-
Added valid field for visualization and future compatibility with ADAS ROI filtering
-
Add simple functions
-
- Reversed back UKF node to develop
-
Formatted speed
-
Refactor codes
-
Make tracking visualization work
-
Relay class info in tracker node
-
Remove dependency to jskbbox and rosmarker in ukf tracker
-
apply rosclang to ukf tracker
-
Refactor codes
-
Revert "apply rosclang to ukf tracker"
-
Revert "Remove dependency to jskbbox and rosmarker in ukf tracker"
-
Revert "Relay class info in tracker node"
-
delete dependency to jsk and remove pointcloud_frame
-
get direction nis
-
set velocity_reliable true in tracker node
-
Add divided function
-
add function
-
Sanity checks
-
Relay all the data from input DetectedObject
-
Divided function work both for immukf and sukf
-
Add comment
-
Refactor codes
-
Pass immukf test
-
make direction assisted tracking work
-
Visualization fixes
-
Refactor codes
-
Tracker Merging step added
-
Added launch file support for merging phase
- lane assisted with sukf
-
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/naive_motion_predict.launch
- Launch file for naive_motion_predict
-
- interval_sec [default: 0.1]
- num_prediction [default: 10]
- sensor_height [default: 2.0]
- filter_out_close_object_threshold [default: 1.5]
- input_topic [default: /detection/objects]
Messages
Services
Plugins
Recent questions tagged naive_motion_predict at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 1.12.0 |
License | Apache 2 |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Description | autoware.ai perf |
Checkout URI | https://github.com/is-whale/autoware_learn.git |
VCS Type | git |
VCS Version | 1.14 |
Last Updated | 2025-03-14 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Kosuke Murakami
Authors
Naive Motion Prediction
Autoware package for motion prediction.
- From a sourced terminal:
roslaunch naive_motion_predict naive_motion_predict.launch
- From Runtime Manager:
Computing Tab -> Prediction/ Motion Predictor -> naive_motion_predict
Requirements
-
ray_ground_filter
node. -
eucledian_cluster
node. -
/tf
topic.velodyne
toworld
. -
imm_ukf_pda_tracker
node.
Parameters
Launch file available parameters for naive_motion_predict
Parameter | Type | Description |
---|---|---|
input topic |
String | Input topic(type: autoware_msgs::DetectedObjectArray). Default /detection/lidar_tracker/objects . |
interval_sec |
Double | Interval second for prediction. Default 9.22 . |
num_prediction |
Int | The number of prediction this node will make. Default 0.99 . |
sensor_height |
Double | Uses sensor height for visualized path’s height. Default 0.9 . |
Subscribed topics
Topic | Type | Objective |
---|---|---|
/detection/objects |
autoware_msgs::DetectedObjectArray |
The result topic from Autoware Detection stack |
Published topics
Topic | Type | Objective |
---|---|---|
/prediction/objects |
autoware_msgs::DetectedObjectArray |
Added predicted objects to input data.. |
/prediction/motion_predictor/path_markers |
visualization_msgs::MarkerArray |
Visualzing predicted path in ros marker array |
Video
Changelog for package naive_motion_predict
1.11.0 (2019-03-21)
- [fix] not predicting objects at x<=0 or y<=0 (#2122)
- [Feature] costmap generator
(#1774)
-
- Initial commit for visualization package
-
Removal of all visualization messages from perception nodes
-
Visualization dependency removal
-
Launch file modification
-
- Fixes to visualization
-
Error on Clustering CPU
-
Reduce verbosity on markers
-
Publish acceleration and velocity from ukf tracker
-
Remove hardcoded path
-
Updated README
-
updated prototype
-
Prototype update for header and usage
-
Removed unknown label from being reported
-
Updated publishing orientation to match develop
-
- Published all the trackers
-
Added valid field for visualization and future compatibility with ADAS ROI filtering
-
Add simple functions
-
- Reversed back UKF node to develop
-
Formatted speed
-
Refactor codes
-
Make tracking visualization work
-
Relay class info in tracker node
-
Remove dependency to jskbbox and rosmarker in ukf tracker
-
apply rosclang to ukf tracker
-
Refactor codes
-
Revert "apply rosclang to ukf tracker"
-
Revert "Remove dependency to jskbbox and rosmarker in ukf tracker"
-
Revert "Relay class info in tracker node"
-
delete dependency to jsk and remove pointcloud_frame
-
get direction nis
-
set velocity_reliable true in tracker node
-
Add divided function
-
add function
-
Sanity checks
-
Relay all the data from input DetectedObject
-
Divided function work both for immukf and sukf
-
Add comment
-
Refactor codes
-
Pass immukf test
-
make direction assisted tracking work
-
Visualization fixes
-
Refactor codes
-
Tracker Merging step added
-
Added launch file support for merging phase
- lane assisted with sukf
-
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/naive_motion_predict.launch
- Launch file for naive_motion_predict
-
- interval_sec [default: 0.1]
- num_prediction [default: 10]
- sensor_height [default: 2.0]
- filter_out_close_object_threshold [default: 1.5]
- input_topic [default: /detection/objects]