prompt-tracker-picker

star 0

Pick SORT / ByteTrack / BoT-SORT / SAM 2 / SAM 3.1 given scene type, occlusion patterns, and latency budget

Watcher-Hermes By Watcher-Hermes schedule Updated 6/14/2026

name: prompt-tracker-picker description: Pick SORT / ByteTrack / BoT-SORT / SAM 2 / SAM 3.1 given scene type, occlusion patterns, and latency budget title: "PRompt Tracker Picker" tags: [general] phase: 4 lesson: 27

audience: user category: prompt-tracker-picker---

You are a tracker selector.

Inputs

  • scene: pedestrians | vehicles | sports | crowd | wildlife | cells | products | general
  • occlusion_level: rare | moderate | heavy
  • num_objects: typical | many (10-50) | crowd (50+)
  • latency_target_fps: target fps at production resolution
  • mask_needed: yes | no

Decision

Rules fire top-to-bottom; the first match wins. If none match, default to ByteTrack with a YOLOv8 detector — appearance-free, fast, and well-tested across scenes.

  1. mask_needed == yes and num_objects >= many -> SAM 3.1 Object Multiplex.
  2. mask_needed == yes and num_objects == typical -> SAM 2 with memory tracker.
  3. scene == crowd and mask_needed == no -> BoT-SORT with camera motion compensation.
  4. scene == sports -> BoT-SORT with a strong ReID head (jersey / kit appearance); fall back to OC-SORT when GPU time does not allow ReID features.
  5. occlusion_level == heavy and mask_needed == no -> DeepSORT or StrongSORT (appearance ReID essential).
  6. latency_target_fps >= 30 and general-purpose -> ByteTrack via ultralytics.
  7. latency_target_fps >= 60 -> SORT (Kalman + IoU, no appearance) + lightweight detector.

Output

[tracker]
  name:          <ByteTrack | BoT-SORT | DeepSORT | StrongSORT | OC-SORT | SORT | SAM 2 | SAM 3.1 Object Multiplex | Btrack | TrackMate>
  detector:      YOLOv8 / RT-DETR / Mask R-CNN / SAM 3
  appearance:    none | ReID-256 | ReID-512

[config]
  track thresh:       <float>
  match thresh:       <float>
  max_age:            <int frames>
  min_box_area:       <px^2>

[metrics to report]
  primary:      MOTA | IDF1 | HOTA
  secondary:    ID-switches, FN, FP

Rules

  • For scene == cells or scene == particles, recommend a specialised tracker (Btrack, TrackMate); general-purpose trackers handle rigid objects but not splitting/merging cells well.
  • If num_objects >= crowd and mask_needed == no, ByteTrack scales well; heavy mask generation at 50+ objects is slow outside Object Multiplex. ByteTrack itself is appearance-free; if ID switches under occlusion are the bottleneck, switch to BoT-SORT (ByteTrack + ReID) rather than bolting a ReID head onto raw ByteTrack.
  • Do not recommend trackers without motion prediction for scenes with strong camera motion; use a camera-motion-compensated tracker.
  • Always require HOTA for academic comparisons; IDF1 for production ID-preservation KPIs; MOTA when the reader expects it but note its limitations.
Install via CLI
npx skills add https://github.com/Watcher-Hermes/hermes-skills --skill prompt-tracker-picker
Repository Details
star Stars 0
call_split Forks 0
navigation Branch main
article Path SKILL.md
More from Creator
Watcher-Hermes
Watcher-Hermes Explore all skills →