Skip to content

Write mAP headers as mAP<sup>val</sup><sub>50-95</sub>: IoU range as a subscript - #376

Merged
glenn-jocher merged 3 commits into
mainfrom
metric-notation
Nov 1, 2026
Merged

glenn-jocher merged 3 commits into
mainfrom
metric-notation

Conversation

@glenn-jocher

@glenn-jocher glenn-jocher commented Nov 1, 2026 •

Copy link
Copy Markdown
Member

Summary

The compare-page table headers now use the metric notation used across Ultralytics: the evaluation split as a superscript and the IoU range as a subscript, mAP<sup>val</sup><sub>50-95</sub>. Before, the range was stacked inside the superscript (mAP<sup>val<br>50-95</sup>), so 50-95 rendered as a superscript in tables and as a subscript everywhere else.

  • 156 headers across the 156 compare pages. Tables were realigned with the repo's Prettier settings, so the diff is mostly whitespace.
  • One prose mention ("a higher mAP50-95") drops the code style for the same notation.
  • Python print(...) lines in code blocks are unchanged.

On docs.ultralytics.com the renderer stacks the superscript over the subscript, as in LaTeX (ultralytics/portal#5011). GitHub shows the same markup side by side.

Related

🛠️ PR Summary

Made with ❤️ by Ultralytics Actions

WARNING ⚠️ this PR is very large, summary may not cover all changes.

🌟 Summary

Compare-page tables now format mAP with val as a superscript and 50-95 as a subscript, matching the notation used elsewhere in Ultralytics docs.

📊 Key Changes

  • Updated mAP headers across 156 compare pages from mAP<sup>val<br>50-95</sup> to mAP<sup>val</sup><sub>50-95</sub>.
  • Removed inline code styling from one prose mention of mAP50-95.
  • Reflowed table spacing to match Prettier formatting; metric values and Python print(...) lines were unchanged.

🎯 Purpose & Impact

  • Readers see the evaluation split and IoU range in distinct superscript and subscript positions in compare tables; the reported metrics themselves are unchanged.

…a subscript

The compare tables stacked the IoU range inside the superscript (mAP<sup>val<br>50-95</sup>). They now use the notation every Ultralytics source uses: the split as a superscript, then the IoU range as a subscript. One prose mention moves from code style to the same notation.
@UltralyticsAssistant UltralyticsAssistant added the documentation Improvements or additions to documentation label Nov 1, 2026
@UltralyticsAssistant

Copy link
Copy Markdown
Member

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/docs 🚀 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/docs 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 UltralyticsAssistant left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔍 PR Review

Made with ❤️ by Ultralytics Actions

Reviewed the mAP notation changes across all 156 compare pages, including the prose update. The superscript and subscript markup is applied consistently, and no regressions were found. LGTM.

⚠️ Large PR: Review focused on critical issues. Some details may not be covered.

@glenn-jocher
glenn-jocher merged commit 07738e2 into main Nov 1, 2026
6 checks passed
@glenn-jocher
glenn-jocher deleted the metric-notation branch November 1, 2026 13:40
@UltralyticsAssistant

Copy link
Copy Markdown
Member

🎉 Thanks @glenn-jocher for the merged PR! The updated mAP notation makes the evaluation split and IoU range distinct across compare tables, while leaving metric values unchanged.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants