[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 notation in Ultralytics skill documentation to use explicit subscripts for IoU thresholds and the depth metric, aligning the displayed names with the stated canonical notation.

📊 Key Changes

• Changed model-comparison tables to display mAP<sub>50-95</sub>.
• Updated training and tuning guidance to use mAP<sub>50</sub> and mAP<sub>50-95</sub>.
• Changed the depth metric label from delta1 to δ<sub>1</sub> and the Platform CLI description from AP50 to AP<sub>50</sub>.

🎯 Purpose & Impact

• These edits affect how metric names appear in the skill documentation; they do not change commands, metric calculations, or logged metric keys.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/skills 🚀 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/skills 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 metric-notation edits in the four changed skill files. The HTML subscript notation is valid in the edited prose and tables, and the documented code and metric keys remain unchanged. LGTM; no behavioral issues found.

[UltralyticsAssistant]

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

“Great things are done by a series of small things brought together.” — Vincent van Gogh

These small documentation updates make metric notation clearer and consistent with the stated canonical names.