Analytics using Ultralytics YOLO26
Analytics with Ultralytics YOLO26 turns object detection and tracking results into real-time charts, so you can watch how object counts change across a video frame by frame. This guide covers four data visualization types — line graphs, bar plots, pie charts, and area plots — and shows how to switch between them with shared Python and CLI examples.
Watch: How to generate Analytical Graphs using Ultralytics | Line Graphs, Bar Plots, Area and Pie Charts
Visual Samples#
| Line Graph | Bar Plot | Pie Chart |
|---|---|---|
![]() | ![]() | ![]() |
Why Visualize Detection Data?#
- Line graphs are ideal for tracking changes over short and long periods and for comparing changes for multiple groups over the same period.
- Bar plots are suitable for comparing quantities across different categories and showing relationships between a category and its numerical value.
- Pie charts are effective for illustrating proportions among categories and showing parts of a whole.
- Area plots fill the line graph so per-class object counts over time are easier to read at a glance.
Generate Analytics Graphs#
Pass your video to the Analytics solution and select a chart with analytics_type. The solution runs detection and tracking on every frame and renders a 1280×720 chart (by default) you can write straight to an output video. Switch between "line", "bar", "pie", and "area" with a single argument.
yolo solutions analytics show=True
# Pass the source
yolo solutions analytics source="path/to/video.mp4"
# Generate the pie chart
yolo solutions analytics analytics_type="pie" show=True
# Generate the bar plots
yolo solutions analytics analytics_type="bar" show=True
# Generate the area plots
yolo solutions analytics analytics_type="area" show=TrueAnalytics Arguments#
Here's a table outlining the Analytics arguments:
| Argument | Type | Default | Description |
|---|---|---|---|
model | str | None | Path to an Ultralytics YOLO model file. |
analytics_type | str | 'line' | Type of graph, i.e., line, bar, area, or pie. |
figsize | tuple[float, float] | (12.8, 7.2) | Figure size in inches for Analytics charts; (12.8, 7.2) renders a 1280×720 frame. |
line_width | int | 2 | Line thickness for the boxes, keypoints and counts the solution draws. |
verbose | bool | True | Enables the solution's per-frame log of input shape, class counts and processing speed. The tracking call itself is always silent. |
You can also use track arguments in the Analytics solution.
| Argument | Type | Default | Description |
|---|---|---|---|
tracker | str | 'tracktrack.yaml' | Specifies the tracking algorithm to use. Built-in options: botsort.yaml, bytetrack.yaml, ocsort.yaml, deepocsort.yaml, fasttrack.yaml, tracktrack.yaml. |
conf | float | 0.25 | Sets the confidence threshold for detections; lower values allow more objects to be tracked but may include false positives. |
iou | float | 0.5 | Sets the Intersection over Union (IoU) threshold for filtering overlapping detections. |
classes | list | None | Filters results by class index. For example, classes=[0, 2, 3] only tracks the specified classes. |
device | str | None | Specifies the device for inference (e.g., cpu, cuda:0 or 0). Allows users to select between CPU, a specific GPU, or other compute devices for model execution. |
imgsz | int or tuple | 640 | Target inference image size: an integer for a square or a (height, width) pair. Shapes are adjusted to the model stride. |
max_det | int | 300 | Maximum number of detections kept per frame before tracking, limiting the objects a solution processes in dense scenes. |
quantize | int or str | None | Inference precision: 16 (FP16) or 32/unset (FP32) for PyTorch and TorchScript models off CPU; other formats use the precision their artifact and runtime select. Replaces the deprecated half arg. |
Additionally, the following visualization arguments are supported:
| Argument | Type | Default | Description |
|---|---|---|---|
show | bool | False | If True, displays the annotated images or videos in a window. Useful for immediate visual feedback during development or testing. |
Conclusion#
Understanding when and how to use different types of visualizations is crucial for effective data analysis. Line graphs, bar plots, pie charts, and area plots are fundamental tools that can help you convey your data's story more clearly and effectively. The Ultralytics YOLO26 Analytics solution provides a streamlined way to generate these visualizations from your object detection and tracking results, making it easier to extract meaningful insights from your visual data.
FAQ#
To create a line graph using Ultralytics YOLO26 Analytics, follow these steps:
- Load a YOLO26 model and open your video file.
- Initialize the
Analyticsclass withanalytics_type="line". - Iterate through video frames, calling the solution each frame to update the line graph with data such as object counts.
- Write
results.plot_imto an output video to save the chart.
Use the Python example above as a starting point — it already runs the full frame loop, and a line graph is the default
analytics_type.Using Ultralytics YOLO26 for creating bar plots offers several benefits:
- Real-time Data Visualization: Integrate object detection results into bar plots for dynamic updates.
- Ease of Use: Simple API and functions make it straightforward to implement and visualize data.
- Customization: Customize titles, labels, colors, and more to fit your specific requirements.
- Efficiency: Efficiently handle large amounts of data and update plots in real time during video processing.
To generate a bar plot, set
analytics_type="bar"in the Python example above — the rest of the frame loop is identical. See the Visual Samples section for a preview.Ultralytics YOLO26 is an excellent choice for creating pie charts because:
- Integration with Object Detection: Directly integrate object detection results into pie charts for immediate insights.
- User-Friendly API: Simple to set up and use with minimal code.
- Customizable: Various customization options for colors, labels, and more.
- Real-time Updates: Handle and visualize data in real time, which is ideal for video analytics projects.
To generate a pie chart, set
analytics_type="pie"in the Python example above. For more information, refer to the Visual Samples section in the guide.Yes. Tracking is built into the
Analyticssolution: it tracks multiple objects in real time and refreshes the chart from the tracked objects' data every 30 frames, so line graphs, bar plots, pie charts, and area plots all reflect live counts. This is exactly what the frame loop in the Python example above does. To learn about the underlying tracking functionality, see the Tracking section.Ultralytics YOLO26 stands out from other object detection solutions like OpenCV and TensorFlow for multiple reasons:
- State-of-the-art Accuracy: YOLO26 provides superior accuracy in object detection, instance segmentation, semantic segmentation, and classification tasks.
- Ease of Use: User-friendly API allows for quick implementation and integration without extensive coding.
- Real-time Performance: Optimized for high-speed inference, suitable for real-time applications.
- Diverse Applications: Supports multi-object tracking, custom model training, and exporting to different formats like ONNX, TensorRT, and CoreML.
- Comprehensive Documentation: Extensive documentation and blog resources to guide users through every step.
Comments17
Ask a question, share your results, or help someone else.
UserHello @glenn-jocher How we can optimize/modify the code for YOLO predict, so it can also give final compiled result of prediction as graph. In case of counting objects/cells classed as different categories in images stored in a root folder. Not just the images with the prediction boxes.
yolo train model=yolo11n.pt data=coco8.yaml epochs=100 imgsz=640
yolo predict model=yolo11n.pt source=path/to/bus.jpg
Like the count graph YOLO makes after training or bar/pie chart?
Thanks
User@pderrenger Greetings
UserHello,
In relation to the above question, will this code work?
#!/usr/bin/env python3 """ yolo_predict_results.py
Run YOLO predictions on a single image or a directory of images, save annotated images, export per-image and aggregate counts to CSV, and save plots (aggregate bar chart and optional stacked per-image bar chart).
Requirements: pip install ultralytics pandas matplotlib pillow
Usage (recommended - command line): # Single image python yolo_predict_results.py --model /path/to/yolo11n.pt --source /path/to/bus.jpg --output results --save-annotated --plot-aggregate
# Directory (batch) python yolo_predict_results.py --model /path/to/yolo11n.pt --source /path/to/images_dir --output results --save-annotated --plot-per-image --plot-aggregateThis file includes clearly highlighted comments showing exactly where to set your model path and images directory if you prefer to hardcode them in the script instead of using CLI args. """
import argparse from collections import Counter from pathlib import Path import sys
import numpy as np import pandas as pd import matplotlib.pyplot as plt from PIL import Image
try: from ultralytics import YOLO except Exception as e: print("Please install ultralytics (pip install ultralytics).") raise
IMAGE_EXTS = {".jpg", ".jpeg", ".png", ".bmp", ".tif", ".tiff", ".webp"}
def find_images(directory: Path): return [str(p) for p in sorted(directory.rglob("*")) if p.suffix.lower() in IMAGE_EXTS]
def predict_images(model, paths, conf=0.25, imgsz=640, device=None, save_annotated=False, out_dir=None): """ Run prediction per-image (keeps mapping simple). Returns list of dicts: {'file': path, 'counts': Counter, 'total': int} """ out_dir = Path(out_dir) if out_dir is not None else None annotated_dir = (out_dir / "annotated") if (save_annotated and out_dir is not None) else None if annotated_dir: annotated_dir.mkdir(parents=True, exist_ok=True)
results = [] for p in paths: print(f"Predicting: {p}") res_list = model.predict(source=p, conf=conf, imgsz=imgsz, device=device, verbose=False) if not res_list: print(f"Warning: no result for {p}") continue r = res_list[0] counts = Counter() try: box_cls = getattr(r.boxes, "cls", None) if box_cls is not None: try: arr = box_cls.cpu().numpy() except Exception: arr = np.array(box_cls) arr = arr.astype(int).flatten() for c in arr: name = model.names.get(int(c), str(int(c))) counts[name] += 1 except Exception as e: print(f"Warning: could not parse classes for {p}: {e}") total = sum(counts.values()) results.append({"file": p, "counts": counts, "total": total}) if save_annotated and annotated_dir: try: ann = r.plot() if isinstance(ann, np.ndarray): img_out = Image.fromarray(ann) else: img_out = ann out_path = annotated_dir / (Path(p).stem + "_annotated" + Path(p).suffix) img_out.save(out_path) except Exception as e: print(f"Warning: failed to save annotated image for {p}: {e}") return resultsdef build_dataframe(summary): all_classes = set() for row in summary: all_classes.update(row["counts"].keys()) classes = sorted(all_classes)
rows = [] for row in summary: data = {cls: row["counts"].get(cls, 0) for cls in classes} data["file"] = row["file"] data["total"] = row["total"] rows.append(data) if not rows: # Return empty dataframe df = pd.DataFrame(columns=["file", "total"] + classes) else: df = pd.DataFrame(rows) cols = ["file"] + classes + ["total"] df = df[cols] return df, classesdef save_csvs(summary, out_dir: Path): df, classes = build_dataframe(summary) out_dir.mkdir(parents=True, exist_ok=True) csv1 = out_dir / "counts_per_image.csv" df.to_csv(csv1, index=False) print(f"Saved per-image counts to: {csv1}")
agg = Counter() for r in summary: agg.update(r["counts"]) agg_series = pd.Series(dict(agg)).sort_values(ascending=False) csv2 = out_dir / "aggregate_counts.csv" agg_series.to_csv(csv2, header=["count"]) print(f"Saved aggregate counts to: {csv2}") return df, classes, aggdef plot_aggregate(agg_counter, out_path: Path): names = list(agg_counter.keys()) counts = [agg_counter[n] for n in names] fig, ax = plt.subplots(figsize=(max(6, len(names) * 0.6), 5)) ax.bar(names, counts, color="tab:blue") ax.set_ylabel("Count") ax.set_title("Aggregate object counts") plt.xticks(rotation=45, ha="right") plt.tight_layout() out_path.parent.mkdir(parents=True, exist_ok=True) fig.savefig(out_path) plt.close(fig) print(f"Saved aggregate plot to: {out_path}")
def plot_stacked_per_image(df: pd.DataFrame, classes, out_path: Path, top_n=50): if df.empty: print("No per-image data to plot.") return plot_df = df.copy() if top_n and len(plot_df) > top_n: plot_df = plot_df.sort_values("total", ascending=False).head(top_n) x = plot_df["file"].apply(lambda p: Path(p).name).tolist() bottoms = np.zeros(len(plot_df)) fig, ax = plt.subplots(figsize=(max(8, len(x) * 0.6), 6)) for cls in classes: vals = plot_df[cls].values ax.bar(x, vals, bottom=bottoms, label=cls) bottoms += vals ax.set_ylabel("Counts") ax.set_title("Per-image stacked counts") ax.legend(bbox_to_anchor=(1.05, 1), loc="upper left") plt.xticks(rotation=45, ha="right") plt.tight_layout() out_path.parent.mkdir(parents=True, exist_ok=True) fig.savefig(out_path) plt.close(fig) print(f"Saved per-image stacked plot to: {out_path}")
def main(): ap = argparse.ArgumentParser(description="YOLO predict -> save CSV + plots") ap.add_argument("--model", required=False, help="Path to YOLO model (.pt) (e.g., yolo11n.pt)") ap.add_argument("--source", required=False, help="Image file or directory of images") ap.add_argument("--output", required=False, help="Output directory", default="results") ap.add_argument("--conf", type=float, default=0.25, help="Confidence threshold") ap.add_argument("--imgsz", type=int, default=640, help="Image size for inference") ap.add_argument("--device", type=str, default=None, help="Device (e.g., 0 or 'cpu')") ap.add_argument("--save-annotated", action="store_true", help="Save annotated images") ap.add_argument("--plot-per-image", action="store_true", help="Save stacked per-image plot") ap.add_argument("--plot-aggregate", action="store_true", help="Save aggregate bar chart") ap.add_argument("--top-n", type=int, default=50, help="Top N images for per-image plot when many images")
# Parse CLI args (recommended usage) args = ap.parse_args() # ------------------------------------------------------------------------- # HIGHLIGHT 1: If you want to hardcode paths, replace the `args = ap.parse_args()` line # with the block below. Edit the two highlighted lines inside the block: # model="..." <-- SET YOUR MODEL FILE PATH HERE # source="..." <-- SET YOUR IMAGE FILE OR IMAGES DIRECTORY PATH HERE # # Example (UNCOMMENT and EDIT, then COMMENT OUT or REMOVE the args = ap.parse_args() above): # # args = argparse.Namespace( # model="/path/to/yolo11n.pt", # <<< HIGHLIGHT: set model path here (absolute or relative) # source="/path/to/images_or_image", # <<< HIGHLIGHT: set image file or images directory path here # output="results", # conf=0.25, # imgsz=640, # device=None, # save_annotated=True, # plot_per_image=True, # plot_aggregate=True, # top_n=50 # ) # ------------------------------------------------------------------------- # ------------------------------------------------------------------------- # HIGHLIGHT 2: If you prefer using the command-line, supply these two args when # running the script: # --model /path/to/yolo11n.pt # --source /path/to/images_or_image # These correspond to the variables used below: args.model and args.source # ------------------------------------------------------------------------- if not args.model or not args.source: print("Error: --model and --source are required (or hardcode them in the script).") print("Example:") print(" python yolo_predict_results.py --model /path/to/yolo11n.pt --source /path/to/images --output results --save-annotated --plot-aggregate") sys.exit(1) model_path = Path(args.model) source = Path(args.source) out_dir = Path(args.output) out_dir.mkdir(parents=True, exist_ok=True) print(f"Loading model: {model_path}") model = YOLO(str(model_path)) if source.is_dir(): files = find_images(source) if not files: print(f"No images found under {source}") sys.exit(1) elif source.is_file(): files = [str(source)] else: print(f"Source path not found: {source}") sys.exit(1) summary = predict_images( model=model, paths=files, conf=args.conf, imgsz=args.imgsz, device=args.device, save_annotated=args.save_annotated, out_dir=out_dir, ) if not summary: print("No predictions were produced.") sys.exit(0) df, classes, agg = save_csvs(summary, out_dir) if args.plot_aggregate: plot_aggregate(agg, out_dir / "aggregate_counts.png") if args.plot_per_image: plot_stacked_per_image(df, classes, out_dir / "per_image_stacked_counts.png", top_n=args.top_n) print("All done. Results in:", out_dir.resolve())if name == "main": main()
Glenn JocherUltralytics@MUK003 great question, and thanks for sharing the script in detail.
The short answer is: yes, this is a reasonable way to get per-image and aggregate count graphs from YOLO11 predictions, since
YOLO('yolo11n.pt')returnsResultsobjects wherer.boxes.clsholds the class indices and yourCounter/CSV/Matplotlib logic will work on top of that. I’d recommend first running it on a very small image folder and confirming that the numbers incounts_per_image.csvandaggregate_counts.csvmatch what you expect from a few sample images.From the Ultralytics side there’s currently no built-in
yolo predictCLI flag that directly produces those bar/pie charts like training; your Python approach (or, for video streams, thesolutions.Analyticscharts) is the right pattern. For reference on how analytics is structured inside Ultralytics, you can also glance at the Analytics solution API docs.
User@glenn-jocher Many thanks :)
yeongnamtan
thank you very much @glenn-jocher
yeongnamtan
How to integrate the code for line graph with line counter ?
Glenn JocherUltralytics(edited)@yeongnamtan to integrate the line graph with a line counter, use the
Analyticsclass to update the line graph with the total object counts per frame. Ensure you initialize theAnalyticswithanalytics_type="line"and update it within your video processing loop. For detailed guidance, please refer to the analytics section in the documentation.
Peymankar
Hi, how can i count number of left turns or right turns in an intersection?
Glenn JocherUltralytics@Peymankar hello!
To count the number of left or right turns at an intersection using Ultralytics YOLO, you can set up a tracking system that identifies and follows each vehicle's trajectory. Here’s a brief outline on how you might approach this:
-
Track Vehicles: Use the YOLO model to detect and track vehicles. You can use the
model.track()function to keep track of each vehicle's movement frame by frame. -
Define Zones: Define areas or lines within the video frame that represent the boundaries of different turn directions (left, right).
-
Analyze Trajectories: Analyze the paths of tracked vehicles to determine when they cross these defined zones. This can be done by checking the intersection of vehicle tracks with these zones and classifying the movement as a left or right turn based on the zone they intersect.
-
Count Turns: Maintain a count of how many vehicles make left or right turns based on these intersections.
For a more detailed guide on setting up vehicle tracking and analyzing trajectories, you might find the tracking and analytics features in the Ultralytics documentation helpful. Implementing this will require some custom coding to define zones and analyze paths relative to these zones.
If you need further assistance or more specific guidance, feel free to ask. Happy coding! 😊
-
yeongnamtan
ani = FuncAnimation(fig, animate, frames=range(int(cap.get(cv2.CAP_PROP_FRAME_COUNT))), blit=False, interval=1000/fps, repeat=False)
plt.show()
The code is still not working... I
error meesage ... WARNING ⚠️ best.pt appears to require 'dill', which is not in ultralytics requirements. AutoInstall will run now for 'dill' but this feature will be removed in the future. Recommend fixes are to train a new model using the latest 'ultralytics' package or to run a command with an official YOLOv8 model, i.e. 'yolo predict model=yolov8n.pt' requirements: Ultralytics requirement ['dill'] not found, attempting AutoUpdate... Collecting dill Downloading dill-0.3.8-py3-none-any.whl (116 kB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 116.3/116.3 kB 4.9 MB/s eta 0:00:00 Installing collected packages: dill Successfully installed dill-0.3.8
requirements: AutoUpdate success ✅ 5.8s, installed 1 package: ['dill'] requirements: ⚠️ Restart runtime or rerun command for updates to take effect
requirements: Ultralytics requirement ['lapx>=0.5.2'] not found, attempting AutoUpdate... Collecting lapx>=0.5.2 Downloading lapx-0.5.9-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.7 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.7/1.7 MB 11.8 MB/s eta 0:00:00 Requirement already satisfied: numpy>=1.21.6 in /usr/local/lib/python3.10/dist-packages (from lapx>=0.5.2) (1.25.2) Installing collected packages: lapx Successfully installed lapx-0.5.9
requirements: AutoUpdate success ✅ 7.4s, installed 1 package: ['lapx>=0.5.2'] requirements: ⚠️ Restart runtime or rerun command for updates to take effect
0: 384x640 2 fishs, 134.7ms Speed: 13.4ms preprocess, 134.7ms inference, 747.7ms postprocess per image at shape (1, 3, 384, 640)
DisabledFunctionError Traceback (most recent call last) in <cell line: 26>() 37 clswise_count[model.names[int(cls)]] = 1 38 ---> 39 analytics.update_bar(clswise_count) 40 cv2_imshow('Bar Plot', frame) 41 clswise_count = {}
1 frames /usr/local/lib/python3.10/dist-packages/google/colab/_import_hooks/_cv2.py in wrapped(*args, **kwargs) 46 def wrapped(*args, **kwargs): 47 if not os.environ.get(env_var, False): ---> 48 raise DisabledFunctionError(message, name or func.name) 49 return func(*args, **kwargs) 50
DisabledFunctionError: cv2.imshow() is disabled in Colab, because it causes Jupyter sessions to crash; see https://github.com/jupyter/notebook/issues/3935. As a substitution, consider using from google.colab.patches import cv2_imshow
Paula DerrengerUltralyticsHello,
Thank you for sharing the details of the issue you're encountering. It seems like the
dillandlapxpackages were missing but have now been successfully installed. Please ensure you restart your runtime or rerun your command to allow the updates to take effect, as suggested by the AutoUpdate messages.Regarding the
DisabledFunctionErrorforcv2.imshow()in Colab, this function is indeed disabled because it can cause Jupyter sessions to crash. As an alternative, you can usecv2_imshowfrom thegoogle.colab.patchesmodule to display images in Colab notebooks. Here’s how you can modify your code:from google.colab.patches import cv2_imshow # Replace cv2.imshow with cv2_imshow cv2_imshow(frame)This should allow you to display images without causing any issues in your Colab environment.
If you have any more questions or need further assistance, feel free to ask. Happy coding! 🚀
yeongnamtan
thank you
yeongnamtan
In the code for bar plots , I don't see any cv2.imshow. when I run the code, I get cv2.imshow error.
Paula DerrengerUltralytics@yeongnamtan hello,
It seems like you're encountering an issue with
cv2.imshownot being present in the bar plot code example. This function is indeed necessary to display the frames with the visualizations in real-time. To resolve the error, you can add the following line just after updating the bar plot in the loop:cv2.imshow('Bar Plot', frame)Make sure to include this inside the loop where frames are being processed, and it will display the updated frame with the bar plot. Additionally, ensure that you have the line
if cv2.waitKey(1) & 0xFF == ord('q'):to handle the window closure properly.If you need further assistance or have more questions, feel free to ask!
yeongnamtan
I tried to use google colab but it is giving me error because of cv2.imshow... How can I modify it to use cv2_imshow instead ... from google.colab.patches import cv2_imshow # Import cv2_imshow from google.colab.patches
DisabledFunctionError: cv2.imshow() is disabled in Colab, because it causes Jupyter sessions to crash; see https://github.com/jupyter/notebook/issues/3935. As a substitution, consider using from google.colab.patches import cv2_imshow
Paula DerrengerUltralyticsHello! To use
cv2_imshowinstead ofcv2.imshowin Google Colab, you can make a simple modification to your code. First, ensure you importcv2_imshowfromgoogle.colab.patchesas you've mentioned. Then, replace all instances ofcv2.imshowwithcv2_imshow. Here’s how you can do it:-
Import the function:
from google.colab.patches import cv2_imshow -
Replace
cv2.imshowwithcv2_imshow:# Instead of cv2.imshow("Frame", frame) cv2_imshow(frame)
This change should resolve the issue with displaying images in Google Colab. Let me know if there's anything else you need help with! 😊
-


