Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Add static detection to OCR solution - #26152

Open
ojedavd wants to merge 5 commits into
ultralytics:mainfrom
ojedavd:feature/ocr-solution
Open

Add static detection to OCR solution#26152
ojedavd wants to merge 5 commits into
ultralytics:mainfrom
ojedavd:feature/ocr-solution

Conversation

@ojedavd

@ojedavd ojedavd commented Sep 12, 2026

Copy link
Copy Markdown

🛠️ PR Summary

Made with ❤️ by Ultralytics Actions

🌟 Summary

Adds static detection support to an OCR solution, based on the pull request title; the diff was unavailable for verification.

📊 Key Changes

  • The PR is titled “Add static detection to OCR solution.”
  • No diff was available, so specific files, APIs, or implementation details cannot be confirmed.

🎯 Purpose & Impact

The intended workflow impact is enabling static object detection within the OCR solution, but the exact behavior and user-facing changes require diff review.

@github-actions

github-actions Bot commented Sep 12, 2026

Copy link
Copy Markdown

All Contributors have signed the CLA. ✅

@UltralyticsAssistant UltralyticsAssistant added detect Object Detection issues, PR's enhancement New feature or request solutions Ultralytics Solutions issues, PR's, Discussions labels Sep 12, 2026
@UltralyticsAssistant

Copy link
Copy Markdown
Member

👋 Hello @ojedavd, thank you for submitting a ultralytics/ultralytics 🚀 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/ultralytics 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 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

⚠️ Review generation encountered an error: ERROR: UNABLE TO RETRIEVE DIFF.

@ojedavd

ojedavd commented Sep 12, 2026

Copy link
Copy Markdown
Author

I have read the CLA Document and I sign the CLA

@codecov

codecov Bot commented Sep 12, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 93.61702% with 3 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
ultralytics/solutions/ocr.py 93.47% 3 Missing ⚠️

📢 Thoughts on this report? Let us know!

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

Labels

detect Object Detection issues, PR's enhancement New feature or request solutions Ultralytics Solutions issues, PR's, Discussions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants