Live data from Hacker News

How we made our OCR code more accurate

pieces.app

31–40 of 50 posts

Re: How we made our OCR code more accurate

#31
post #26
post #20

Earlier quoted context omitted.

The original tesseract OCR has no neural nets. It bare little resemblance to the modern version.

It's still 40. Why not use Ollama-OCR?

Because I benchmarked both on my dataset and found that Tesseract was better for my use-case?

Re: How we made our OCR code more accurate

#34
post #3

Neat article, but I feel like I have no idea why they're doing this! Is transcribing code from images really such a big use case?

It worries me that stuff like that becoming easier will lead to wacky data pipelines being normalized (pulling display output off systems and "scraping" it to get data, of dubious quality, versus just building a proper interface). The kind of crowd that likes "low code" tools like MSFT's "Power Automate" is going to love to make Rube Goldberg nightmares out of tools like this.

It fills me with a deep sadness that we created deterministic machines then, though laziness, exploit every opportunity to "contaminate" them with sloppy practices that make them produce output with the same fuzzy inaccuracy as human brains.

Old man yells a neural networks take: We're entering a "The Machine Stops" era where nobody is going to know how to formulate basic algorithms.

"We need to add some numbers. Let's point a camera at the input, OCR it, then feed it to an LLM that 'knows math'. Then we don't have to figure out an algorithm to add numbers."

I wish compute "cost" more so people would be forced to actually make efficient use of hardware. Sadly, I think it'll take mass societal and infrastructure collapse for that to happen. Until it does, though, let the excess compute flow freely!

Re: How we made our OCR code more accurate

#35
post #17

Tesseract OCR was created by digital (DEC) in 19_8_5 (yes, 40 not four YEARs ago). Now go back and read the article and ROFL with me.

Unix was created in _1971_ and here we are still running processes and shells like it’s the 70s. Why not just have an LLM dream up the output?

Re: How we made our OCR code more accurate

#36
post #26
post #20

Earlier quoted context omitted.

The original tesseract OCR has no neural nets. It bare little resemblance to the modern version.

It's still 40. Why not use Ollama-OCR?

I’ve tested a bunch of vision models on particularly difficult documents (handwritten in a German script that’s no longer used), and I have yet to be impressed. They’re good at BSing to the point that you almost think they nailed it, until you realize that it’s mostly/all made-up text that doesn’t appear in the document.

Re: How we made our OCR code more accurate

#37
post #3

Neat article, but I feel like I have no idea why they're doing this! Is transcribing code from images really such a big use case?

It worries me that stuff like that becoming easier will lead to wacky data pipelines being normalized (pulling display output off systems and "scraping" it to get data, of dubious quality, versus just building a proper interface). The kind of crowd that likes "low code" tools like MSFT's "Power Automate" is going to love to make Rube Goldberg nightmares out of tools like this. It fills me with a deep sadness that we…

asimov - The feeling of power.

Re: How we made our OCR code more accurate

#38
post #9
post #6

Anything that mentions tesseract is about 10 years out of date at this point.

5.5.0 released November last year. Still a very active project as far as I can tell and runs on CPU. Even compared to best open source GPU option it is still pretty good. VLMs work very differently and don't work as well for everything. Why is it out of date?

I don't know that that is true: https://researchify.io/blog/comparing-pytesseract-paddleocr-...

Using Surya gets you significantly better results and makes almost all the work detailed in the article largely unnecessary.

Re: How we made our OCR code more accurate

#40
post #26
post #20

Earlier quoted context omitted.

The original tesseract OCR has no neural nets. It bare little resemblance to the modern version.

It's still 40. Why not use Ollama-OCR?

> It's still 40.

Is it, though? If the important parts of the code are new, does it matter that other parts are older or derived from older code? (Of course, I think this whole line of thought is pointless; what matters is not age, but how well it works, and tesseract generally does seem to work.)

Post reply on HN