Amit Dovev
Amit Dovev
The reason for disabling OpenMP is that Tesseract currently uses it inefficiently. For text recognition the speed benefit for using OpenMP with fast / tessdata (best->int) traineddata is too small...
`--disable-openmp` disables OpenMP at compile time, while `OMP_THREAD_LIMIT=1` disables it at runtime. The first method is more efficient, while the second method is more flexible.
Stefan, for 5.1.0, do you want to keep a way to enable OpenMP with `--enable-openmp`?
``` Error in boxClipToRectangle: box outside rectangle Error in pixScanForForeground: invalid box ``` Add a white/black frame to the image and no error messages will appear. ``` convert 427-1.jpg -bordercolor...
> The biggest problem for me, however, is that in OCRopus they don't even get OCRed. This place is for bug reports about **Tesseract**, not OCRopus.
>I'm guessing OCRopus is using Tesseract Ocropy (and clstm) does not use Tesseract. A VERY OLD version of Ocropus (0.4) did use Tesseract.
Similar issues #468 #1601 These error messages are produced by Leptonica. They are triggered by a call to `pixClipBoxToForeground()` https://github.com/DanBloomberg/leptonica/blob/bbe289cf3f0fe368d5b9eac64df2ccd6e9b05c56/src/pix5.c#L1956 https://github.com/tesseract-ocr/tesseract/search?q=pixClipBoxToForeground
@stweil, this seems like a bug in Tesseract, maybe you can explore it and find its cause.
https://github.com/tesseract-ocr/tesseract/search?q=pixClipBoxToForeground I noticed that Tesseract does not check the return value from Leptonica's functions (`l_ok`).
@csidirop, Does adding a white or black border to the image help? https://github.com/tesseract-ocr/tesseract/issues/427#issuecomment-248153491 If not, post an image that demonstrate the issue.