RECOGNIZE TIME: 00:00:11.3292062 | ENGINE: LstmOnly
RECOGNIZE TIME: 00:00:05.9569210 | ENGINE:
TesseractAndCube
RECOGNIZE TIME: 00:00:10.6854010 | ENGINE:
TesseractAndLstm
RECOGNIZE TIME: 00:00:10.6725257 | ENGINE: Default
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+unsubscribe@googlegroups.com.
To post to this group, send email to tesser...@googlegroups.com.
Visit this group at https://groups.google.com/group/tesseract-ocr.
To view this discussion on the web visit https://groups.google.com/d/msgid/tesseract-ocr/CAC9ebrorORNrpApquscKiPf2Qbguc85qY1SJve6heu2j4Dithg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
how did you used cube engine on tesse 4 !?
--
OCR Engine modes: 0 Original Tesseract only. 1 Neural nets LSTM only. 2 Tesseract + LSTM. 3 Default, based on what is available
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 allow fallback // to Tesseract when things get difficult. OEM_DEFAULT, // Specify this mode when calling init_*(), // to indicate that any of the above modes // should be automatically inferred from the // variables in the language-specific config, // command-line configs, or if not specified // in any of the above should be set to the // default OEM_TESSERACT_ONLY. OEM_CUBE_ONLY, // Run Cube only - better accuracy, but slower OEM_TESSERACT_CUBE_COMBINED, // Run both and combine results - best accuracy};
Sorry, mentioned incorrect code for LSTMOCR Engine modes: 0 Original Tesseract only. 1 Neural nets LSTM only. 2 Tesseract + LSTM. 3 Default, based on what is available- excuse the brevity, sent from mobile
On 22-Mar-2017 9:02 PM, "ShreeDevi Kumar" <shree...@gmail.com> wrote:
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, "universal reseller" <unire...@gmail.com> wrote:
--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-oc...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to tesseract-ocr+unsubscribe@googlegroups.com.
To post to this group, send email to tesser...@googlegroups.com.
Visit this group at https://groups.google.com/group/tesseract-ocr.
To view this discussion on the web visit https://groups.google.com/d/msgid/tesseract-ocr/0a0bb2e9-cc85-464c-8801-c4614edbfd05%40googlegroups.com.