I noticed an unfortunate case when a batch process hit the full-resolution version of http://dl.wdl.org/11298_1_1.png. Tesseract
v3.02.02 takes a very long amount of time (~30 minutes) in page segmentation, presumably repetitively processing every fiber in the cloth cover as the down-scaled linked image above runs quickly. https://gist.github.com/af9c84d4232da1e6127f Obviously, there are ways we could work around this in our workflow but I was wondering whether there's been any thought to something as simple as a time limit for this stage? Chris -- -- You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/tesseract-ocr?hl=en --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
