YOLO26 performance comparison PNG

[glenn-jocher]

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Updates the ultralytics/assets README example to use a newer YOLO model filename (YOLO26) instead of YOLOv8 🚀

📊 Key Changes

• Replaced the README code sample model load from yolov8n.pt to yolo26n.pt 🧠
• Adjusted the accompanying comment to be version-agnostic (“Ultralytics YOLO model” instead of “YOLOv8n”) ✍️
• Updated an auto-generated/lock asset file: yolo/performance-comparison.png (diff not shown) 🖼️

🎯 Purpose & Impact

• Keeps documentation aligned with the latest Ultralytics model naming and examples 📚
• Helps new users start with the intended default model family, reducing confusion when following the README ✅
• Potentially affects copy-paste workflows: users who previously expected YOLOv8 weights will now download/use yolo26n.pt by default ⬇️

📋 Skipped 1 file (lock files, generated, images, etc.)

• yolo/performance-comparison.png

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/assets 🚀 PR! This is an automated note—an engineer will review and assist shortly. 🤖✨ To ensure a seamless integration of your work, please review the following checklist:

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/assets main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀

[UltralyticsAssistant]

🔍 PR Review

_{Made with ❤️ by Ultralytics Actions}

Small README update; overall clean. Two things to verify: (1) keep the comment line more future-proof by referring to "Ultralytics YOLO" rather than embedding the specific variant in prose, and (2) confirm yolo26n.pt is the exact downloadable checkpoint name so the quickstart doesn’t break.

💬 Posted 2 inline comments

📋 Skipped 1 file (lock files, generated, images, etc.)

• yolo/performance-comparison.png

[UltralyticsAssistant]

Merged and looking great — thank you @glenn-jocher! This update keeps the ultralytics/assets README aligned with the latest Ultralytics YOLO naming (YOLO26) and makes the example more version-agnostic, which will help new users avoid confusion and succeed faster with copy‑paste workflows.

As Leonardo da Vinci put it, “Simplicity is the ultimate sophistication.” This PR embodies that: a small, thoughtful documentation tweak that meaningfully improves clarity and onboarding for everyone who lands on the repo.

Appreciate you continuing to polish the details that make the Ultralytics ecosystem feel seamless.