See
https://github.com/tesseract-ocr/tesseract/commit/5deebe6c279f70215935c1f86baa7e7016c7f2a7
Ray's comment for commit
Moved cube aside without deleting it.
- excuse the brevity, sent from mobile
On 22-Mar-2017 10:07 PM, "THintz" wrote:
> I'm sure I cloned master on
I noticed OpenMP support isn't enabled by default. I'll get new timings.
What do modes 4 & 5 do if Cube is no longer present? They produced good
output, and performance was the best.
--
You received this message because you are subscribed to the Google Groups
"tesseract-ocr" group.
To
I'm sure I cloned master on 3/20/2017 3:55. publictypes.h defines this:
enum OcrEngineMode {
OEM_TESSERACT_ONLY, // Run Tesseract only - fastest
OEM_LSTM_ONLY,// Run just the LSTM line recognizer.
OEM_TESSERACT_LSTM_COMBINED, // Run the LSTM recognizer, but
Sorry, mentioned incorrect code for LSTM
OCR Engine modes:
0Original Tesseract only.
1Neural nets LSTM only.
2Tesseract + LSTM.
3Default, based on what is available
- excuse the brevity, sent from mobile
On 22-Mar-2017 9:02 PM, "ShreeDevi Kumar"
The initial 4.0alpha tag from November has cube in it. It was deleted later
and is no longer in master.
In fact, the OEM code for LSTM was originally 4 and now is 2.
Shouldn't semantic versioning require tagging at major updates?
- excuse the brevity, sent from mobile
On 22-Mar-2017 8:58 PM,
See
https://github.com/tesseract-ocr/tesseract/wiki/4.0-Accuracy-and-Performance
- excuse the brevity, sent from mobile
On 22-Mar-2017 8:58 PM, "universal reseller" wrote:
> how did you used cube engine on tesse 4 !?
>
> --
> You received this message because you are
how did you used cube engine on tesse 4 !?
--
You received this message because you are subscribed to the Google Groups
"tesseract-ocr" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tesseract-ocr+unsubscr...@googlegroups.com.
To post to this group,
LSTM recognize via TessBaseAPIRecognize() gives me the following
performance numbers for the same bi-tonal image. The image is read and
passed as a bitmap. These numbers are only for the TessBaseAPIRecognize()
call portion of the process.
The question is this: should I have expected LSTM
8 matches
Mail list logo