correct ratio determination for noise estimation

[rmast]

I solved issue #52 myself.

[MerlijnWajer]

Thanks -- I will review this tonight or tomorrow at latest, I'm mostly on the road today.

[rmast]

The second commit is for solving this error:
#55 (comment)

[MerlijnWajer]

btw, I think I fixed this in 3c20a46 - can you confirm?

[rmast]

btw, I think I fixed this in 3c20a46 - can you confirm?

Without resetting up and retesting it I read through the issues to see what we were trying to solve.
In the text of #52, namely #52 (comment), I read some inline patch of mrc.py on the inversion that I don't see reflected. So I can imagine not all inversion is handled correctly.

The issue with the double text (Array) is caused by a segmentation bug in Tesseract which I've tried to crack during my summer holiday. However there's too little testing capacity and core-knowledge at Tesseract to allow core-changes to repair this segmentation, which caused the superior EasyOCR-segmentation to emerge.

At the end of my summer holiday this year I tried to get a complete new inversion based on the segmentation of EasyOCR and an algorithm to compare the inner color and the outer color of those found segments for the inversion choice. I unfortunately didn't have the time to mold it into a working product.

[rmast]

This Christmas Holiday my attention is distracted by new AI programming capabilities of OpenAI Codex, rolling on the ChatGPT-hype. As I'm really bad at Cython programming I'm trying to let Codex make consistent/improve my code for a new context sensitive inverter. I wonder whether there is an other approach for interpreting and segmenting documents at a more intelligent level: https://x-decoder-vl.github.io/