[glenn-jocher]

Summary

Metric names now use the notation every Ultralytics repo uses: IoU thresholds are subscripts (mAP₅₀, mAP_50-95, mAP₇₅, AP₅₀), the depth threshold is a subscript (δ₁), and an evaluation split or task comes first as a superscript (mAP^val_50-95).

• Legacy spellings in prose (mAP@0.5, mAP@0.5:0.95, mAP<sub>0.5:0.95</sub>, delta1) become the canonical names.
• Stacked table headers (mAP<sup>val<br>50-95</sup>) put the IoU range in a subscript after the split superscript.
• Code, logged metric keys (metrics/mAP_0.5, metrics/mAP50-95(B)), URLs and image alt text are unchanged.

Related

ultralytics/ultralytics#26990, ultralytics/docs#376 and ultralytics/portal#5011 apply the same notation across the docs, READMEs and every Ultralytics site.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Updated metric labels across model READMEs to use consistent subscript and superscript notation without changing metric values.

📊 Key Changes

• Reformatted YOLO11 and YOLO26 performance table headers to show evaluation splits or tasks as superscripts and IoU thresholds as subscripts.
• Updated YOLOv8-World metric labels and explanatory prose to use mAP<sub>50-95</sub>, mAP<sub>50</sub>, and mAP<sub>75</sub>.
• Changed the ImageNet validation-set link in the YOLO26 classification README to the Ultralytics dataset documentation.

🎯 Purpose & Impact

• README readers see consistent, clearer metric notation; model values and runtime behavior are unchanged.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/replicate 🚀 PR! This automated message confirms your contribution was received, and an Ultralytics engineer will assist with the review. 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/replicate 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; the CLA check will comment with signing instructions if needed.
• ✅ 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}

Reviewed the README metric-notation changes. The IoU-specific labels are updated, but the overall mAP metric remains ambiguous in the table and matching prose.

💬 Posted 1 inline comment

• 📝 LOW yolov8s-worldv2/README.md:67 The first column reports COCO mAP over IoU thresholds 0.50–0.95, but its bare mAP label leaves the range ambiguous—the notation this PR is standardizing. Please use mAP<sub>50-95</sub> here and for the matching bare mAP references in the metric bullet and endpoint note below.

[UltralyticsAssistant]

🎉 This PR has been merged—thank you, @glenn-jocher!

“The details are not the details. They make the design.” — Charles Eames

Consistent metric notation makes the model READMEs clearer while keeping all metric values unchanged.