-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Release 2.1.10 #3240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 2.1.10 #3240
Conversation
master->dev
Fix block coverage
fix: optimize block removal logic by tracking processed indices
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This release (2.1.10) fixes an issue in the pipeline backend where block overlap was causing parsing results to deviate from expectations. The changes improve block merging and overlap detection logic to resolve conflicts between OCR and table detection results.
- Refactored table merging polygon coordinate assignment for cleaner code
- Added new function to remove overlapping blocks with low confidence scores
- Improved text block classification logic for better OCR integration
- Updated documentation with release notes
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.
File | Description |
---|---|
mineru/utils/model_utils.py | Refactored polygon assignment and added block overlap removal functionality |
mineru/backend/pipeline/model_json_to_middle_json.py | Improved text block classification logic and code structure |
README_zh-CN.md | Added Chinese changelog entry for version 2.1.10 |
README.md | Added English changelog entry for version 2.1.10 |
Co-authored-by: Copilot <[email protected]>
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
Checklist
Before PR:
After PR: