Re: [tesseract-ocr] Tesseract 4 LSTM vs TesseractAndCube performance

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

[tesseract-ocr] Re: Tesseract 4 LSTM vs TesseractAndCube performance

Enabling OpenMP in Visual Studio for the build roughly doubled LSTM performance. -- 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] Re: training font

you can train it for single font. On Sunday, March 19, 2017 at 1:23:50 PM UTC+5:30, Ava Nimaee wrote: > > hi , i need your help. > i want know that in tesseract-ocr for persian , we have a train for each > font or we have a train for all fonts ?thanks > -- You received this message because you

Re: [tesseract-ocr] train tesseract OCR 4.0

Thank you shree for your valuable reply. But now i have created box files for a particuler image and trained it..but still i am missing something, may you please help me what i have to do after creating box file for that image and make tesseract to read the characters from that image. thanks

Re: [tesseract-ocr] Tesseract 4 LSTM vs TesseractAndCube performance

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

Re: [tesseract-ocr] Tesseract 4 LSTM vs TesseractAndCube performance

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

Re: [tesseract-ocr] Tesseract 4 LSTM vs TesseractAndCube performance

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"

Re: [tesseract-ocr] Tesseract 4 LSTM vs TesseractAndCube performance

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,

Re: [tesseract-ocr] Tesseract 4 LSTM vs TesseractAndCube performance

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

Re: [tesseract-ocr] Tesseract 4 LSTM vs TesseractAndCube performance

​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,

[tesseract-ocr] Re: FOSS Project Proposal: tesseract-cloud

That's a great idea -- I don't have spare time for new projects at the moment, but I wonder if something like OpenOCR might be useful as a starting point for an effort like this: https://github.com/tleyden/open-ocr On Tuesday, March 21, 2017 at 4:03:52 PM UTC-4, Rich Jones wrote: > > Hello,

[tesseract-ocr] Tesseract 4 LSTM vs TesseractAndCube performance

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