-
Notifications
You must be signed in to change notification settings - Fork 255
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
Tesseract 5.0.1 test_LSTM_choices(...) fails #295
Comments
Hi @simonflueckiger , can you please provide the instructions on how to build tesserocr with tesseract 5 . |
@srinivas1746 you can have a look at my appveyor.yml from my repository tesserocr-windows_build. |
Hi @simonflueckiger , thank you for the update. In my case I want to build on UBUNTU system. Please let me know if there is any way? |
CMake and vcpkg work very similarly on Linux, so if you want to build Tesseract 5.x from source you can use most of appveyor.yml with minor adaptations. To build tesserocr on Linux please refer to this README. |
@simonflueckiger thank you for you respose. I am able to build tesserocr + tesseract 5 with instructions in this link. |
@sirfz has this been changed/fixed in the meantime? |
@simonflueckiger I saw the last comment about the working windows build, now I realize the issue is unrelated so I'm reopening it. Anyone with knowledge about |
I also encounter a strange behavior when using tesserocr 2.5.2 together with tesseract 5.0.1 After the switch I get strange confidence values, the symbol choices themselves seem to be okay.
|
I think we should change the test case, we shouldn't be testing tesseract's correctness, instead just test that tesserocr's API wrapping works. It's not wrong to get different results (especially confidence scores) from different models/versions (like in this case with tesseract 5 vs 4) so we shouldn't expect it to be a static value or range |
They scores didn't just change, I think they are wrong. If you look at the values I posted above, you can see that they increase with getting more unlikely. I first thought this could be a log-prob., but this neither makes sense. What you are saying is that this may be a bug in Tesseract itself? |
popos 22.04, tesseract 5.2, tesserocr main branch
reinstalled and tried to use tesseract 4.1
|
https://build.opensuse.org/request/show/1067957 by user dgarcia + dimstar_suse - Disable current broken tests, test_LSTM_choices, test_detect_os and or test_init, gh#sirfz/tesserocr#295
This seems to be an issue with a changed API in tesseract itself. See tesseract-ocr/tesseract#3706 In order to convert the scores to confidences you have to first fetch a variable: Then you get the scores from tesserocr: Then you can convert the scores: |
I compiled tesserocr 2.5.2 with Tesseract 5.0.1 on Windows. When executing
tesserocr\tests\test_api.py
I get the following exception for test_LSTM_choices(...):Very similar to this #147 (comment). It passes when built with Tesseract 4.1.3. Does this also pass on Travis for Tesseract 5.x? I get a 404 when trying to access the build pipeline.
The text was updated successfully, but these errors were encountered: