🚨 Repository Name Change Announcement 🚨

We are planning to rename this repository from yolov8_ros to yolo_ros on 31-10-2024.

The repository is renamed since more YOLO models are supported in this tool, not only YOLOv8.

Check out the updates in the yolo_ros branch.

Please update your local repository, dependencies, scripts or tools that rely on the repository URL.

After the name change, update your local repository URL:

git remote set-url origin https://github.com/mgonzs13/yolo_ros.git

ROS 2 wrap for Ultralytics YOLOv8 to perform object detection and tracking, instance segmentation, human pose estimation and Oriented Bounding Box (OBB). There are also 3D versions of object detection, including instance segmentation, and human pose estimation based on depth images.

1. Installation
2. Models
3. Usage
4. Demos

$ cd ~/ros2_ws/src
$ git clone https://github.com/mgonzs13/yolov8_ros.git
$ pip3 install -r yolov8_ros/requirements.txt
$ cd ~/ros2_ws
$ rosdep install --from-paths src --ignore-src -r -y
$ colcon build

The available models for yolov8_ros are the following:

• YOLOv3
• YOLOv4
• YOLOv5
• YOLOv6
• YOLOv7
• YOLOv8
• YOLOv9
• YOLOv10
• YOLOv11
• YOLO-NAS

$ ros2 launch yolov8_bringup yolov5.launch.py

$ ros2 launch yolov8_bringup yolov8.launch.py

$ ros2 launch yolov8_bringup yolov9.launch.py

$ ros2 launch yolov8_bringup yolov10.launch.py

$ ros2 launch yolov8_bringup yolov11.launch.py

$ ros2 launch yolov8_bringup yolo-nas.launch.py

• /yolo/detections: Objects detected by YOLO using the RGB images. Each object contains a bounding boxes and a class name. It may also include a mak or a list of keypoints.
• /yolo/tracking: Objects detected and tracked from YOLO results. Each object is assigned a tracking ID.
• /yolo/debug_image: Debug images showing the detected and tracked objects. They can be visualized with rviz2.

• model_type: Ultralytics model type (default: YOLO)
• model: YOLOv8 model (default: yolov8m.pt)
• tracker: Tracker file (default: bytetrack.yaml)
• device: GPU/CUDA (default: cuda:0)
• enable: Wether to start YOLOv8 enabled (default: True)
• threshold: Detection threshold (default: 0.5)
• input_image_topic: Camera topic of RGB images (default: /camera/rgb/image_raw)
• image_reliability: Reliability for the image topic: 0=system default, 1=Reliable, 2=Best Effort (default: 2)

$ ros2 launch yolov8_bringup yolov8_3d.launch.py

• /yolo/detections: Objects detected by YOLO using the RGB images. Each object contains a bounding boxes and a class name. It may also include a mak or a list of keypoints.
• /yolo/tracking: Objects detected and tracked from YOLO results. Each object is assigned a tracking ID.
• /yolo/detections_3d: 3D objects detected. YOLO results are used to crop the depth images to create the 3D bounding boxes and 3D keypoints.
• /yolo/debug_image: Debug images showing the detected and tracked objects. They can be visualized with rviz2.

• model_type: Ultralytics model type (default: YOLO)
• model: YOLOv8 model (default: yolov8m.pt)
• tracker: tracker file (default: bytetrack.yaml)
• device: GPU/CUDA (default: cuda:0)
• enable: wether to start YOLOv8 enabled (default: True)
• threshold: detection threshold (default: 0.5)
• input_image_topic: camera topic of RGB images (default: /camera/rgb/image_raw)
• image_reliability: reliability for the image topic: 0=system default, 1=Reliable, 2=Best Effort (default: 2)
• input_depth_topic: camera topic of depth images (default: /camera/depth/image_raw)
• depth_image_reliability: reliability for the depth image topic: 0=system default, 1=Reliable, 2=Best Effort (default: 2)
• input_depth_info_topic: camera topic for info data (default: /camera/depth/camera_info)
• depth_info_reliability: reliability for the depth info topic: 0=system default, 1=Reliable, 2=Best Effort (default: 2)
• depth_image_units_divisor: divisor to convert the depth image into metres (default: 1000)
• target_frame: frame to transform the 3D boxes (default: base_link)
• maximum_detection_threshold: maximum detection threshold in the z axis (default: 0.3)

Previous updates add Lifecycle Nodes support to all the nodes available in the package. This implementation tries to reduce the workload in the unconfigured and inactive states by only loading the models and activating the subscriber on the active state.

These are some resource comparisons using the default yolov8m.pt model on a 30fps video stream.

This is the standard behavior of YOLOv8, which includes object tracking.

$ ros2 launch yolov8_bringup yolov8.launch.py

Instance masks are the borders of the detected objects, not the all the pixels inside the masks.

$ ros2 launch yolov8_bringup yolov8.launch.py model:=yolov8m-seg.pt

Online persons are detected along with their keypoints.

$ ros2 launch yolov8_bringup yolov8.launch.py model:=yolov8m-pose.pt

The 3D bounding boxes are calculated filtering the depth image data from an RGB-D camera using the 2D bounding box. Only objects with a 3D bounding box are visualized in the 2D image.

$ ros2 launch yolov8_bringup yolov8_3d.launch.py

In this, the depth image data is filtered using the max and min values obtained from the instance masks. Only objects with a 3D bounding box are visualized in the 2D image.

$ ros2 launch yolov8_bringup yolov8_3d.launch.py model:=yolov8m-seg.pt

Each keypoint is projected in the depth image and visualized using purple spheres. Only objects with a 3D bounding box are visualized in the 2D image.

$ ros2 launch yolov8_bringup yolov8_3d.launch.py model:=yolov8m-pose.pt