Go to file
Praveen Palanisamy 5d435fd3f2
Updated README to clarify real, sim, dataset LiDAR data
2019-08-27 00:14:41 -07:00
include/kf_tracker v1. Object ID/data association works. In this version PCL based unsupervised clustering is done separately. 2015-12-07 17:20:12 -05:00
src Removed indirection op to be compatible with OpenCV 3+ 2019-04-26 04:57:22 -04:00
.gitignore Asked git to ignore temp vim buffers 2019-04-13 15:06:42 -04:00
CHANGELOG.rst 1.0.1 2019-04-26 06:33:58 -04:00
CMakeLists.txt Changed package name to multi_object_tracking_lidar 2019-04-13 13:12:39 -04:00
README.md Updated README to clarify real, sim, dataset LiDAR data 2019-08-27 00:14:41 -07:00
package.xml 1.0.1 2019-04-26 06:33:58 -04:00

README.md

Multiple objects detection, tracking and classification from LIDAR scans/point-clouds

Sample demo of multiple object tracking using LIDAR scans

PCL based ROS package to Detect/Cluster --> Track --> Classify static and dynamic objects in real-time from LIDAR scans implemented in C++.

Features:

  • K-D tree based point cloud processing for object feature detection from point clouds
  • Unsupervised k-means clustering based on detected features and refinement using RANSAC
  • Stable tracking (object ID & data association) with an ensemble of Kalman Filters
  • Robust compared to k-means clustering with mean-flow tracking

Usage:

Follow the steps below to use this (multi_object_tracking_lidar) package:

  1. Create a catkin workspace (if you do not have one setup already).
  2. Navigate to the src folder in your catkin workspace: cd ~/catkin_ws/src
  3. Clone this repository: git clone https://github.com/praveen-palanisamy/multiple-object-tracking-lidar.git
  4. Compile and build the package: cd ~/catkin_ws && catkin_make
  5. Add the catkin workspace to your ROS environment: source ~/catkin_ws/devel/setup.bash
  6. Run the kf_tracker ROS node in this package: rosrun multi_object_tracking_lidar kf_tracker

If all went well, the ROS node should be up and running! As long as you have the point clouds (from 1. A real LiDAR or 2. A simulated LiDAR or 3. A point cloud dataset or 4. Any other data source that produces point clouds) published on to the filtered_cloud rostopic, you should see outputs from this node published onto the obj_id, cluster_0, cluster_1, …, cluster_5 topics along with the markers on viz topic which you can visualize using RViz.