From 685000716f5f143ffba8746ed5147958db4b9a3f Mon Sep 17 00:00:00 2001 From: Glenn Jocher Date: Wed, 7 Oct 2026 19:11:21 +0200 Subject: [PATCH 1/2] Migrate the compare hub decision tree to the unified Mermaid design system Convert the Quick Decision Guide from graph TD with legacy classDef colors to flowchart TD with question decisions, labeled exits and a start terminal, so the shared site renderer owns its look. The tree now covers the hardware and performance choice its intro sentence describes. --- docs/en/compare/index.md | 27 ++++++++------------------- 1 file changed, 8 insertions(+), 19 deletions(-) diff --git a/docs/en/compare/index.md b/docs/en/compare/index.md index a2c1bfc8bec..ed9ecb843e0 100644 --- a/docs/en/compare/index.md +++ b/docs/en/compare/index.md @@ -23,25 +23,14 @@ This chart visualizes key [performance metrics](https://docs.ultralytics.com/gui Not sure where to start? Use this decision tree to narrow down the architecture that best fits your hardware and performance requirements. ```mermaid -graph TD - A[Start: Define Project Needs]:::start --> B{Deployment Hardware?}:::decide - B -- "Edge / Mobile (CPU/NPU)" --> C{Latency Priority?}:::decide - B -- "Cloud / GPU" --> D{Accuracy vs Speed?}:::decide - - C -- "Extreme Speed (Real-time)" --> E[YOLO26n / YOLO26s]:::out - C -- "Balanced Legacy" --> F[YOLO11s / YOLOv8s]:::out - - D -- "Max Accuracy (SOTA)" --> G[YOLO26x / YOLO26l]:::out - D -- "Balanced Performance" --> H[YOLO26m / YOLO11m]:::out - - A --> I{Specialized Features?}:::decide - I -- "NMS-Free Inference" --> J[YOLO26 / YOLOv10]:::out - I -- "Multitask (Seg/Pose/OBB)" --> K[YOLO26 / YOLO11]:::out - I -- "Video Analytics" --> L[YOLO26 + Tracking]:::out - - classDef start fill:#4CAF50,color:#fff - classDef decide fill:#FF9800,color:#fff - classDef out fill:#9C27B0,color:#fff +flowchart TD + A([Define project needs]) --> B{Existing YOLO11 pipeline?} + B -->|yes| C[YOLO11] + B -->|no| D{Edge or mobile?} + D -->|no| E{Accuracy first?} + D -->|yes| F[YOLO26n or YOLO26s] + E -->|yes| G[YOLO26l or YOLO26x] + E -->|no| H[YOLO26m] ``` ## The Current Landscape: YOLO26 and Beyond From 209b95ec016941256479029f25083e90643a47b9 Mon Sep 17 00:00:00 2001 From: Glenn Jocher Date: Wed, 7 Oct 2026 21:15:26 +0200 Subject: [PATCH 2/2] Mark compare hub decision outcomes as terminals and list yes exits first --- docs/en/compare/index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/en/compare/index.md b/docs/en/compare/index.md index ed9ecb843e0..28c8e4ee010 100644 --- a/docs/en/compare/index.md +++ b/docs/en/compare/index.md @@ -25,12 +25,12 @@ Not sure where to start? Use this decision tree to narrow down the architecture ```mermaid flowchart TD A([Define project needs]) --> B{Existing YOLO11 pipeline?} - B -->|yes| C[YOLO11] + B -->|yes| C([YOLO11]) B -->|no| D{Edge or mobile?} + D -->|yes| F([YOLO26n or YOLO26s]) D -->|no| E{Accuracy first?} - D -->|yes| F[YOLO26n or YOLO26s] - E -->|yes| G[YOLO26l or YOLO26x] - E -->|no| H[YOLO26m] + E -->|yes| G([YOLO26l or YOLO26x]) + E -->|no| H([YOLO26m]) ``` ## The Current Landscape: YOLO26 and Beyond