-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Wrong bounding box coordinates reported (regression from 4.0.0) #2240
Comments
Could you please try to find out when this regression occurred first, maybe by using |
Does this also occur with commit ce88adb? |
Same problem with ce88adb. Later I'll try git bisect to find the commit. |
Please try commit 7249571 |
Commit 7249571 works as 4.0.0 (tesseract 4.0.0-29-g7249) Here is a comparison of the bounding boxes. 4.0.0: Others: The boxes visually look fine, even better than the old version. Please let me check my code before spending further time on this, maybe the problem is on my side. |
Did you have change to check your code? |
Not yet. If you want we can close this and I will reopen it as soon as I have more details. |
tesseract 4.0.0-279-gec8f
leptonica-1.77.0
libjpeg 6b (libjpeg-turbo 1.2.90) : libpng 1.5.13 : libtiff 4.0.3 : zlib 1.2.7
Found AVX2
Found AVX
Found SSE
b67ff53
Linux ip-xxx-xx-xx-xxx.eu-west-1.compute.internal 3.10.0-957.5.1.el7.x86_64 #1 SMP Wed Dec 19 10:46:58 EST 2018 x86_64 x86_64 x86_64 GNU/Linux
Current Behavior:
Space len is reported as -470
Space len is computed as the distance between the right side of previous box and the left side of the one containing the symbol.
Expected Behavior:
Should be about 17 (as in version 4.0.0 and as from pixel inspection)
Test img:
This is a comparison of the app log:
tess-diff.txt
"DEBUG:root:# Spazio troppo breve -470 lo ignoro"
This means "space too short, ignoring it" and the computed distance is -470.
Many other "space len" are reported as negative values.
I think is a new one, not the same as in #2024 and the two referenced issues.
The text was updated successfully, but these errors were encountered: