You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When evaluating OCR performance on DIR300 dataset(or DocUNet benchmark), the size of the predicted image and GT image are different. I suppose you have resized one of the two in advance. To which size did you resize the images?(predicted size or GT size?)
Hi, sorry for the late reply due to my health.
(1) I have uploaded the evalUnwarp.m in this repo.
(2) For the OCR evaluation, I do not resize the two images. Maybe you could explore the impact of resize operation.
(3) I didn't pay particular attention to this problem. I download the tesseract from the link and the version is 5.0.1.20220118.
Hope this helps~!
Hi, I have a few questions on OCR evaluation.
When evaluating OCR performance on DIR300 dataset(or DocUNet benchmark), the size of the predicted image and GT image are different. I suppose you have resized one of the two in advance. To which size did you resize the images?(predicted size or GT size?)
Which tessdata(traineddata) did you use for Tesseract?(tessdata_fast or tessdata_best or tessdata)
reference: https://tesseract-ocr.github.io/tessdoc/Data-Files.html
The text was updated successfully, but these errors were encountered: