Get Started

Object Tracking Heatmaps with Ultralytics YOLO26

Open Heatmaps In Colab

The Heatmap solution in Ultralytics YOLO26 tracks objects across video frames and overlays their accumulated movement intensity onto each frame, so busy areas glow in warm colors while quiet areas stay cool. Built on YOLO26 object tracking, it turns any video into a spatial activity map that reveals traffic flow, crowd movement, and dwell zones with a single Python call or CLI command.



Watch: How to Create Heatmaps with Ultralytics YOLO26 | Visualize Object Activity | VisionAI in Retail 🚀

Why Use Heatmaps for Video Analytics?#

  • Spot activity patterns at a glance: Intensity accumulates wherever tracked objects spend time, so high-traffic lanes, popular shelves, or crowd bottlenecks stand out without manual frame-by-frame review.
  • Tracking built in: The solution runs YOLO26 detection and tracking internally, so there is no separate tracking pipeline to wire up.
  • Counting in the same pass: Pass a region to count objects entering and exiting a zone while the heatmap builds, combining two analytics tasks in one run.

Real World Applications#

TransportationRetail
Ultralytics YOLO heatmap overlay showing vehicle traffic densityUltralytics YOLO heatmap overlay showing retail customer movement
Ultralytics YOLO Transportation HeatmapUltralytics YOLO Retail Heatmap

How to Generate Heatmaps with Ultralytics YOLO#

Run the Heatmap solution on a video source from the CLI or Python. The Python example writes the processed frames to an output video file:

Heatmaps using Ultralytics YOLO
# Run a heatmap example
yolo solutions heatmap show=True

# Pass a source video
yolo solutions heatmap source="path/to/video.mp4"

# Pass a custom colormap
yolo solutions heatmap colormap=cv2.COLORMAP_INFERNO

# Heatmaps + object counting
yolo solutions heatmap region="[(20, 400), (1080, 400), (1080, 360), (20, 360)]"

Heatmap() Arguments#

Here's a table with the Heatmap arguments:

ArgumentTypeDefaultDescription
modelstrNonePath to an Ultralytics YOLO model file.
colormapintcv2.COLORMAP_DEEPGREENColormap to use for the heatmap.
show_inboolTrueFlag to control whether to display the in counts on the video stream.
show_outboolTrueFlag to control whether to display the out counts on the video stream.
regionlist or dictNonePoints defining the region of interest, either a list of (x, y) tuples or a dictionary mapping region names to point lists for multiple regions (RegionCounter only). When None, solutions that require a region fall back to a predefined default.
line_widthint2Line thickness for the boxes, keypoints and counts the solution draws.
verboseboolTrueEnables the solution's per-frame log of input shape, class counts and processing speed. The tracking call itself is always silent.

You can also apply different track arguments in the Heatmap solution.

ArgumentTypeDefaultDescription
trackerstr'tracktrack.yaml'Specifies the tracking algorithm to use. Built-in options: botsort.yaml, bytetrack.yaml, ocsort.yaml, deepocsort.yaml, fasttrack.yaml, tracktrack.yaml.
conffloat0.25Sets the confidence threshold for detections; lower values allow more objects to be tracked but may include false positives.
ioufloat0.5Sets the Intersection over Union (IoU) threshold for filtering overlapping detections.
classeslistNoneFilters results by class index. For example, classes=[0, 2, 3] only tracks the specified classes.
devicestrNoneSpecifies 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.
imgszint or tuple640Target inference image size: an integer for a square or a (height, width) pair. Shapes are adjusted to the model stride.
max_detint300Maximum number of detections kept per frame before tracking, limiting the objects a solution processes in dense scenes.
quantizeint or strNoneInference 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 supported visualization arguments are listed below:

ArgumentTypeDefaultDescription
showboolFalseIf True, displays the annotated images or videos in a window. Useful for immediate visual feedback during development or testing.
show_confboolTrueDisplays the confidence score for each detection alongside the label. Gives insight into the model's certainty for each detection.
show_labelsboolTrueDisplays labels for each detection in the visual output. Provides immediate understanding of detected objects.

Heatmap Colormaps#

The colormap argument accepts any OpenCV colormap. Pass the constant from the cv2 module, for example colormap=cv2.COLORMAP_INFERNO:

Colormap NameDescription
cv2.COLORMAP_AUTUMNAutumn color map
cv2.COLORMAP_BONEBone color map
cv2.COLORMAP_JETJet color map
cv2.COLORMAP_WINTERWinter color map
cv2.COLORMAP_RAINBOWRainbow color map
cv2.COLORMAP_OCEANOcean color map
cv2.COLORMAP_SUMMERSummer color map
cv2.COLORMAP_SPRINGSpring color map
cv2.COLORMAP_COOLCool color map
cv2.COLORMAP_HSVHSV (Hue, Saturation, Value) color map
cv2.COLORMAP_PINKPink color map
cv2.COLORMAP_HOTHot color map
cv2.COLORMAP_PARULAParula color map
cv2.COLORMAP_MAGMAMagma color map
cv2.COLORMAP_INFERNOInferno color map
cv2.COLORMAP_PLASMAPlasma color map
cv2.COLORMAP_VIRIDISViridis color map
cv2.COLORMAP_CIVIDISCividis color map
cv2.COLORMAP_TWILIGHTTwilight color map
cv2.COLORMAP_TWILIGHT_SHIFTEDShifted Twilight color map
cv2.COLORMAP_TURBOTurbo color map
cv2.COLORMAP_DEEPGREENDeep Green color map

How Heatmaps Work#

The Heatmap solution extends the ObjectCounter class. On the first processed frame it creates a blank intensity layer matching the frame size, and it starts a fresh layer whenever the frame size changes rather than rescaling the activity accumulated so far. Each frame is then processed in two steps:

  1. YOLO26 tracking detects and follows every object in the frame
  2. For each tracked object, the heatmap intensity increases within a circular region centered in its bounding box

Once per frame, the accumulated intensity layer is normalized, colorized with the selected colormap, and blended with the original frame. The overlay appears once at least one object has been tracked; until then, frames are shown without the heatmap overlay.

The result is a dynamic visualization that builds up over time, revealing traffic patterns, crowd movements, or other spatial behaviors in your video data. When a region is set, the solution also counts objects entering and exiting that region while the heatmap builds.

Conclusion#

The Ultralytics YOLO26 Heatmap solution turns object tracking results into an intuitive activity overlay with a few lines of code. To go further, combine it with object counting, explore the other Ultralytics Solutions, or read about the underlying tracking mode.

FAQ#

  • Ultralytics YOLO26 generates heatmaps by tracking objects across video frames and accumulating an intensity value at each tracked object's location, then colorizing the result and blending it with the original frame. Areas where objects appear frequently or linger build up higher intensity and render in warmer colors. For configuration options, refer to the Heatmap() Arguments section.

  • Use OpenCV's cv2.VideoWriter and write results.plot_im for every processed frame, as shown in the main example. The plot_im attribute holds the frame with the heatmap overlay already applied.

  • Yes. Pass a region argument to Heatmap() with line, rectangle, or polygon points, and the solution counts objects entering and exiting that region while the heatmap builds. The returned results include in_count, out_count, and per-class counts. See the object counting guide for region configuration details.

  • Pass the classes argument to Heatmap() with the class indices you want to keep. For example, classes=[0, 2] builds the heatmap only from persons and cars (COCO class indices 0 and 2):

    import cv2
    
    from ultralytics import solutions
    
    cap = cv2.VideoCapture("path/to/video.mp4")
    heatmap = solutions.Heatmap(show=True, model="yolo26n.pt", classes=[0, 2])
    
    while cap.isOpened():
        success, im0 = cap.read()
        if not success:
            break
        results = heatmap(im0)
    cap.release()
    cv2.destroyAllWindows()
  • Ultralytics YOLO26 heatmaps integrate object detection, tracking, intensity accumulation, and overlay rendering into a single call, while generic tools like OpenCV or Matplotlib require you to build that pipeline yourself. The solution processes video streams in real time and supports persistent tracking and customizable colormaps out of the box.

Comments65

Ask a question, share your results, or help someone else.

  1. RizwanMunawarGitHub

    🎉 Big News Alert! 🚀 Ultralytics Solutions CLI is here from ultralytics>=8.3.28! Now, you can easily harness the power of advanced YOLO solutions straight from the command line. Simplify your workflow, and streamline object detection, tracking, counting, and more—all with just a few commands! Get ready to experience a whole new level of efficiency! 💥

    CLI Usage Overview

    yolo SOLUTIONS SOLUTION_NAME ARGS
    • SOLUTIONS is a mandatory keyword.
    • SOLUTION_NAME (optional): Choose from ['count', 'heatmap', 'queue', 'speed', 'workout', 'analytics'].
    • ARGS (optional): Use custom arg=value pairs, like show_in=True, to customize settings.

    Examples

    yolo solutions heatmap show=True  # For object counting
    
    yolo solutions heatmap source="path/to/video/file.mp4"  # Specify a video file path

    Start exploring now and let Ultralytics Solutions CLI power up your projects!

    4
    1. Glenn JocherUltralytics(edited)

      Yes, applying heatmaps to instance segmentation is feasible and offers a vivid way to visualize the density and distribution of detected objects across video frames 🌈. The Heatmap solution runs tracking itself with whatever model you give it, including a segmentation model, and accumulates intensity around each tracked object's bounding box (the masks themselves are not used). Here's a simplified example:

      import cv2
      
      from ultralytics import solutions
      
      cap = cv2.VideoCapture("path/to/video.mp4")
      assert cap.isOpened(), "Failed to open video file or stream!"
      w, h, fps = (int(cap.get(x)) for x in (cv2.CAP_PROP_FRAME_WIDTH, cv2.CAP_PROP_FRAME_HEIGHT, cv2.CAP_PROP_FPS))
      video_writer = cv2.VideoWriter("heatmap_output.avi", cv2.VideoWriter_fourcc(*"mp4v"), fps, (w, h))
      
      # Initialize your heatmap object with a segmentation model
      heatmap = solutions.Heatmap(show=True, model="yolo26n-seg.pt", colormap=cv2.COLORMAP_PARULA)
      
      # Process video frames
      while cap.isOpened():
          success, frame = cap.read()
          if not success:
              break  # Exit loop if no more frames
      
          results = heatmap(frame)
          video_writer.write(results.plot_im)
      
      cap.release()
      video_writer.release()
      cv2.destroyAllWindows()

      This snippet performs tracking with an instance segmentation model on video frames and overlays the accumulated heatmap. Remember, the success of applying heatmaps heavily relies on the quality of your model, so ensure it has been adequately trained or fine-tuned for your instance segmentation task. Happy visualizing! 🚀

    2. Paula DerrengerUltralytics(edited)

      Yes, applying heatmaps to instance segmentation is feasible and offers a vivid way to visualize the density and distribution of detected objects across video frames 🌈. The Heatmap solution tracks objects with the model you provide, including a segmentation model, and overlays the accumulated activity on each frame. It builds the heatmap from the tracked objects' bounding boxes rather than the masks.

      Here's a simplified example:

      import cv2
      
      from ultralytics import solutions
      
      # Initialize video capture
      cap = cv2.VideoCapture("path/to/your/video.mp4")
      assert cap.isOpened(), "Error reading video file"
      
      # Video writer setup
      w, h, fps = (int(cap.get(x)) for x in (cv2.CAP_PROP_FRAME_WIDTH, cv2.CAP_PROP_FRAME_HEIGHT, cv2.CAP_PROP_FPS))
      video_writer = cv2.VideoWriter("segmentation_heatmap.avi", cv2.VideoWriter_fourcc(*"mp4v"), fps, (w, h))
      
      # Initialize heatmap with a segmentation model
      heatmap = solutions.Heatmap(show=True, model="yolo26n-seg.pt", colormap=cv2.COLORMAP_JET)
      
      while cap.isOpened():
          success, im0 = cap.read()
          if not success:
              break
      
          # Track objects and generate the heatmap overlay
          results = heatmap(im0)
      
          # Write heatmap output
          video_writer.write(results.plot_im)
      
      # Cleanup
      cap.release()
      video_writer.release()
      cv2.destroyAllWindows()

      Feel free to experiment with different configurations, such as colormap, to meet your specific visualization needs. Happy coding! 🚀

    3. Arjunpixel28GitHub

      Hi ,

      heatmap_obj = heatmap.Heatmap(view_img=False, imw=w, imh=h, heatmap_alpha=0.5, colormap=cv2.COLORMAP_JET)
      TypeError: Heatmap.__init__() got an unexpected keyword argument 'view_img'

      when i tried to run this i got this error !

    4. Paula DerrengerUltralytics(edited)

      Hey there! 👋 It looks like you encountered an unexpected view_img argument error. I'm here to help!

      This happens because the view_img argument no longer exists in the Heatmap solution; it was replaced by show. Update your Ultralytics library and use the current arguments:

      heatmap = solutions.Heatmap(show=True, model="yolo26n-seg.pt", colormap=cv2.COLORMAP_JET)

      To update the library, run:

      pip install ultralytics --upgrade

      That should do the trick! Keep us posted if you run into any more issues or need further assistance. Happy coding! 🚀

    5. Arjunpixel28GitHub

      I Tried upgrading the ultralytics also its giving same attribute error heatmap_obj = heatmap.Heatmap(imw=w, imh=h, heatmap_alpha=0.5, colormap=cv2.COLORMAP_JET) TypeError: Heatmap.init() got an unexpected keyword argument 'imw'

    6. Paula DerrengerUltralytics(edited)

      @Arjunpixel28 hi there! 👋 It seems there's a mix-up with the initialization arguments for the Heatmap class. You don't need to specify imw and imh, because the frame size is taken from the frames you process. In current versions, initialize it like this:

      heatmap = solutions.Heatmap(model="yolo26n.pt", colormap=cv2.COLORMAP_JET, show=True)
      results = heatmap(frame)  # annotated image is in results.plot_im

      See the Heatmaps guide for the full list of arguments. This setup should work without errors. Should you face any more issues or have further questions, feel free to reach out! 🚀

    7. Arjunpixel28GitHub

      Hi Paula Derrenger,

      in the earlier response you had only given the parameters of imw and imh and now your saying it should not be used and even now its not working still have issue with that.

      heatmap_obj = heatmap.Heatmap(colormap=cv2.COLORMAP_JET, heatmap_alpha=0.5) TypeError: Heatmap.init() got an unexpected keyword argument 'colormap'

      I just asked a simple thing to apply heat map on instance segmentation since so many days you guys have not sloved that

    8. Paula DerrengerUltralytics(edited)

      @Arjunpixel28 hey there! I understand your concern and appreciate your patience. The Heatmap settings are now passed when you create the object (there is no separate set_args()), and the object is called directly on each frame, running tracking itself:

      import cv2
      
      from ultralytics import solutions
      
      cap = cv2.VideoCapture("path/to/video.mp4")
      assert cap.isOpened(), "Error reading video file"
      
      # Settings such as colormap are set at initialization
      heatmap = solutions.Heatmap(model="yolo26n.pt", colormap=cv2.COLORMAP_PARULA)
      
      while cap.isOpened():
          success, frame = cap.read()
          if not success:
              break
      
          results = heatmap(frame)
          cv2.imshow("Heatmap", results.plot_im)
          if cv2.waitKey(1) & 0xFF == ord("q"):
              break
      
      cap.release()
      cv2.destroyAllWindows()

      See the Heatmaps guide for all available arguments. If you encounter other issues, please let us know! 🚀

    9. Arjunpixel28GitHub

      frame_with_heatmap = heatmap_obj.generate_heatmap(frame, tracks) File "/usr/local/lib/python3.10/dist-packages/ultralytics/solutions/heatmap.py", line 163, in generate_heatmap self.heatmap *= self.decay_factor # decay factor TypeError: unsupported operand type(s) for *=: 'NoneType' and 'float' and again i got this error Type error

    10. Paula DerrengerUltralytics(edited)

      @Arjunpixel28 hey there! 👋 It looks like you're encountering a TypeError related to the initialization of the Heatmap object. Sorry for the confusion caused by previous responses. The Heatmap class lives in ultralytics.solutions (it is not importable from ultralytics directly), and arguments such as colormap and show are passed when you create it. The object is then called on each frame:

      import cv2
      
      from ultralytics import solutions
      
      cap = cv2.VideoCapture("path/to/your/video.mp4")
      assert cap.isOpened(), "Failed to open video."
      
      heatmap = solutions.Heatmap(model="yolo26n.pt", colormap=cv2.COLORMAP_JET)
      
      while True:
          ret, frame = cap.read()
          if not ret:
              break  # Exit loop if no more frames
      
          results = heatmap(frame)  # tracking and heatmap overlay in one call
          cv2.imshow("Heatmap Visual", results.plot_im)
          if cv2.waitKey(10) == ord("q"):
              break
      
      cap.release()
      cv2.destroyAllWindows()

      If you're still facing issues, check your Ultralytics version with pip show ultralytics and upgrade with pip install -U ultralytics. Thanks for your patience, and we're here to help get you through this!

    11. Arjunpixel28GitHub

      from ultralytics import YOLO, Heatmap ImportError: cannot import name 'Heatmap' from 'ultralytics' (/home/safepro/.local/lib/python3.10/site-packages/ultralytics/init.py)

    12. Paula DerrengerUltralytics(edited)

      Hey there! 🌟 It looks like you've encountered an import error when trying to use Heatmap from the ultralytics package.

      The heatmap functionality is part of the ultralytics.solutions module. The current import is:

      from ultralytics import solutions
      
      heatmap = solutions.Heatmap(model="yolo26n.pt", show=True)

      If solutions is not recognized, your installed version is likely too old. Update to the latest version using pip:

      pip install ultralytics --upgrade

      See the Heatmaps guide for a full example. Thanks for your understanding, and feel free to reach out with any more questions! 🚀

  2. hariouatGitHub

    Hello everyone,

    Please, how to generate heatmaps for classification model with yolov11?

    Thanks in advance for your reply.

    1
    1. Glenn JocherUltralytics

      Thank you for your question! Currently, heatmap generation in Ultralytics YOLO11 is supported for object detection tasks and not directly for classification models. If you're specifically looking to visualize classification results, you might need to adapt custom visualization techniques using libraries like Matplotlib or OpenCV. For more details on heatmap usage, visit the documentation.

  3. hnyllGitHub

    tips pls on how to generate heatmaps for single images with yolo11 model?

    1
    1. hnyllGitHub

      also is it possible to choose what "class" or thing i want to create a heatmap of?

    2. Glenn JocherUltralytics(edited)

      @hnyll to generate a heatmap for a single image with a YOLO model, create the Heatmap solution with your model and call it on the image, then use the annotated result:

      import cv2
      
      from ultralytics import solutions
      
      heatmap = solutions.Heatmap(model="yolo26n.pt", show=False)
      results = heatmap(cv2.imread("path/to/image.jpg"))
      cv2.imwrite("heatmap_result.jpg", results.plot_im)

      Heatmaps build up intensity over time, so a single image gives only a snapshot of the detected objects. To restrict it to specific classes, pass classes=[...] when creating Heatmap. For more details, please refer to the Ultralytics heatmap guide.

    3. hnyllGitHub(edited)

      thanks for the reply. i found out how to do heatmap on single images. i just wasnt looking carefully enough. do you happen to know where i can find more information about what the classes represent? im not sure that i could find it on the Ultralytics heatmap guide. for example what classes 12 and 18 when i do

      heatmap = solutions.Heatmap( show=True, model="yolo11n.pt", colormap=cv2.COLORMAP_PARULA, classes=[12,18] )

      also is there any way that i can add a class by training a model or something? i wanted to create heatmaps on something that probably isnt in the list of classes in the pretrained yolo model.

    4. Glenn JocherUltralytics

      For class information, you can refer to the dataset's YAML file used during training, which lists all class names. To add a new class, you'll need to retrain the model with a dataset that includes the new class.

  4. JaykhokharaGitHub

    Have you ever tried tracking short video segments (for example, 10-minute chunks) from the same camera based on timestamps, and then combining the heatmaps using those timestamps — such as merging 6 chunks (10 minutes each) to create a 1-hour heatmap? I tried saving the heatmap data in JSON, but the file becomes very large and slow to load. Storing the data in .npy works, but using it at scale or in a larger platform isn’t very practical. Do we have any recommended approach or solution for this in Ultralytics?

    1. Glenn JocherUltralytics

      Yes—rather than JSON, the scalable approach is to persist the underlying accumulated raster (heatmap.heatmap, a NumPy array) and merge by summing arrays (same camera/resolution), then normalize/visualize once at the end; you can either keep a single solutions.Heatmap instance alive across your 10‑minute chunks, or save/load the array between runs (see the Heatmaps guide and the Heatmap solution reference).

      import numpy as np
      import cv2
      from ultralytics import solutions
      
      heatmap = solutions.Heatmap(model="yolo26n.pt", show=False, colormap=cv2.COLORMAP_PARULA)
      
      # ...process a 10-min chunk...
      # results = heatmap(im0)  # call per-frame
      
      # save compactly (much smaller than JSON)
      np.savez_compressed("cam1_2026-01-18T1200Z.npz", heatmap=heatmap.heatmap.astype(np.float32))
      
      # later: merge multiple chunks (1-hour heatmap)
      merged = None
      for f in ["cam1_2026-01-18T1200Z.npz", "cam1_2026-01-18T1210Z.npz", "cam1_2026-01-18T1220Z.npz"]:
          h = np.load(f)["heatmap"]
          merged = h if merged is None else (merged + h)

      If you share what “at scale” means for your platform (e.g., cloud object storage, DB constraints, expected camera count), reply here in this discussion with a bit more detail and we can suggest the best storage format (e.g., chunked zarr/HDF5 vs compressed npz).

    1. Glenn JocherUltralytics

      Los videos de ejemplo específicos mostrados en la documentación no están disponibles para descarga directa. Sin embargo, puedes usar cualquier video para probar la funcionalidad de heatmaps con YOLO11:

      # Usar tu propio video
      yolo solutions heatmap source="path/to/tu_video.mp4" show=True
      
      # O usar videos de ejemplo disponibles públicamente
      # Prueba con videos de tráfico, multitudes, o cualquier escena con movimiento

      También puedes encontrar videos de prueba gratuitos en sitios como Pixabay o usar tu cámara web con source=0 para testing en tiempo real.

  5. haiyuouGitHub

    Is there a heatmap module compatible with YOLO v11 for image detection?

    1. Glenn JocherUltralytics

      @haiyuou thanks for your interest in YOLO11! The current heatmap implementation is designed for video tracking applications, but you can adapt it for single image detection by using the same Heatmap solution with static images. Please continue the discussion here on GitHub rather than via email so the entire community can benefit from the solutions.

    1. Glenn JocherUltralytics(edited)

      @reigngers15 To generate a heatmap visualization for a specific image, you can adapt the solutions approach with a few modifications:

      import cv2
      
      from ultralytics import solutions
      
      # Load your image
      image = cv2.imread("path/to/your/image.jpg")
      
      # Initialize heatmap object
      heatmap = solutions.Heatmap(
          show=True,
          model="yolo26n.pt",
          colormap=cv2.COLORMAP_PARULA,
          # classes=[0, 2],  # Optional: specify classes for heatmap
      )
      
      # Process the image with the heatmap (runs the model internally)
      results = heatmap(image)
      
      # Display or save the result
      cv2.imshow("Heatmap", results.plot_im)
      cv2.waitKey(0)
      cv2.imwrite("heatmap_result.jpg", results.plot_im)

      Since heatmaps typically build up intensity over time across video frames, for a single image you'll get a snapshot visualization of detected objects. If you need more visualization control, you can find additional information in our heatmaps documentation.

    2. reigngers15GitHub

      how about in this code, can i add or change the size of heatmap?

      Initialize heatmap object

      heatmap = solutions.Heatmap( show=True, model=model, # Pass the model directly colormap=cv2.COLORMAP_PARULA, # classes=[0, 2], # Optional: specify classes for heatmap size=15 (if px) )

    3. Glenn JocherUltralytics

      @reigngers15 Currently, the Heatmap class in YOLO11 doesn't have direct parameters for changing the size or shape of the heatmap points from circles to squares. The heatmap implementation uses a radius-based approach to create circular effects around detected objects.

      If you need to customize the size or shape of the heatmap, you would likely need to modify the heatmap_effect method in the source code. This method is responsible for calculating the area of effect for each detection.

      Here's what you could potentially do:

      1. For changing the size: You might need to fork the repository and modify the calculation in the heatmap_effect method to adjust the radius used.

      2. For changing to a square shape: You would need to replace the circular distance calculation with a square boundary check.

      For advanced customizations like these, I recommend checking out the source code in the ultralytics/solutions/heatmap.py file and making your own modified version.

      If you need further guidance on specific implementation details, feel free to ask!

      1
  6. fangyuZ1025GitHub

    That just track task , if i want do some detect, classify,segement task? how can i modify the code?

    1. Glenn JocherUltralytics(edited)

      @fangyuZ1025 the Heatmap solution accumulates the locations of tracked objects, so it needs a model that outputs bounding boxes: a detection model (for example yolo26n.pt) or a segmentation model (for example yolo26n-seg.pt), which you pass as model= when you create solutions.Heatmap(...). Classification models (-cls) produce no object locations, so a heatmap can't be built from them. Refer to the Heatmaps guide for detailed examples and configurations. Let me know if you need further clarification!

    2. fangyuZ1025GitHub

      Sorry, I think I didn't express what I meant. I am working on the heat map of yolov8 to explain the interpretability of the model. This code is doing the heat map of the video tracking task, and I want to implement my image heat map feature detection based on it. I wonder if there is any relevant code. Thanks again for your reply

    3. Glenn JocherUltralytics(edited)

      Thank you for clarifying! To produce a heatmap for static images, you can use the same Heatmap solution and call it on an image: results = heatmap(image) returns a results object with the overlay in results.plot_im. Note that generate_heatmap no longer exists. For further guidance, refer to the heatmap.py implementation. Let us know if you need further assistance!

  7. Halibo01GitHub

    Hello, I'm trying to apply a heatmap using a classification model in YOLOv8, but I'm encountering an issue. The error message I receive is: 'AttributeError: 'NoneType' object has no attribute 'cpu'. Is there a known solution to this?

    1. Glenn JocherUltralytics

      @Halibo01 it seems like the error might be due to an issue with the tracking results. Please ensure you are using the latest version of the Ultralytics package. If the issue persists, double-check that the model and input data are correctly loaded and processed. For more detailed guidance, refer to the Heatmaps Guide.

    2. Glenn JocherUltralytics

      @Halibo01 it looks like you're encountering an issue with the classification model in YOLOv8. The error 'AttributeError: 'NoneType' object has no attribute 'cpu'' typically indicates that a variable expected to hold a tensor is actually None. Please ensure that your model's output is correctly assigned and not None before calling .cpu(). Additionally, verify that you are using the latest version of the Ultralytics package. For further details on heatmaps, you can refer to the Ultralytics Heatmaps Guide.