On Wed, Nov 6, 2013 at 6:02 PM, Tom Morris <[email protected]> wrote:
> On Tuesday, November 5, 2013 12:38:57 PM UTC-5, rkomar wrote: > >> So, I would say that totally different results with code >> compiled with different options or different compilers >> is a sign of bad code. I don't think it should just be >> shrugged off as unavoidable. >> > > I agree with Rob here. Numerical/algorithm instability isn't just going > to be an issue between platforms. It indicates a fragility that could be > broken by compiler upgrades and other changes on a single platform. > > The test results that Nick pointed out report on gross error rates, but at > the detail level, there are going to be a set of individual characters > which are (mis)recognized differently as well as specific reasons for those > differences. It'll take work to isolate the problems, but it's certainly > not an intractable problem. > > Speaking optimistically, Ray edited that wiki page just a few days ago, so > perhaps he's already on the task. > > I don't think so - he just removed the outdated link to UNLV tests. -- -- 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.
