Download ocr-tech/docs/HISTORY_2026-06_BASELINES.md from prosperious/ocr-projects-archive: direct link, hf CLI and curl.
- Browser
- Download file 12.6 kB
-
https://huggingface.co/prosperious/ocr-projects-archive/resolve/main/ocr-tech/docs/HISTORY_2026-06_BASELINES.md
- Command line
-
hf download hf://prosperious/ocr-projects-archive/ocr-tech/docs/HISTORY_2026-06_BASELINES.md
-
curl -L -o HISTORY_2026-06_BASELINES.md https://huggingface.co/prosperious/ocr-projects-archive/resolve/main/ocr-tech/docs/HISTORY_2026-06_BASELINES.md
June 2026 baseline history (TrOCR, Tesseract, Surya routers)
Moved verbatim from the README on 2026-09-24. These results predate the Limbu recognizer and the Devanagari fine-tune; they document why the project stopped building routers over Tesseract/Surya and moved to script-specific PaddleOCR recognizers.
Current HF Result
The strongest verified TrOCR candidate so far is the rebalanced mixed-script run trained on k2 and evaluated on a held-out 180-sample mixed Nepali/English line set.
That run is materially better than our own earlier HF candidates:
- overall benchmark CER:
1.628157->0.586139 - English CER:
0.379729->0.300454 - Nepali CER:
7.870295->2.014560 - real-slice CER:
12.702701->1.770016
But the first named baseline comparison is still bad news for the project claim: on that same eval split, tesseract is better than the rebalanced candidate on overall, English, Nepali, real, and synthetic OCR metrics.
The next attempted rescue path also failed. On June 14, 2026, a ByT5 text-correction model trained on k2 from mined Tesseract noisy/clean pairs was packaged as a text_correction_composite candidate with raw Tesseract as the base engine. On the same held-out 180-sample eval, that composite regressed catastrophically: overall CER 6.912065 versus raw Tesseract 0.329012, with paired CER 0 wins, 170 losses, and 10 ties. That rules out the current Tesseract-plus-corrector path as a serious answer.
There is one narrower improvement worth keeping, but it is not a claim-grade win. A routed Tesseract composite now exists as quality_select_composite: it runs default Tesseract (psm=6) and a secondary variant (psm=13), scores both outputs with the local quality_score, and switches only when the secondary beats the primary by a configured margin.
The same-pack tuned run looked slightly better on the original 180-sample mixed eval, but that was not honest enough. After splitting that pack into a separate calibration half (89 samples) and untouched holdout half (91 samples), the calibrated routed candidate still improved overall CER on the holdout, just by much less:
- raw tesseract holdout overall CER:
0.342234 - routed tesseract holdout overall CER:
0.340608 - paired CER on holdout:
2wins,1loss,88ties
That makes it a plausible engineering baseline, not a frontier result. The effect size is tiny, the pack still is not claim-ready, and the real Devanagari recognizer problem remains open.
We also tested a richer calibrated Tesseract ensemble over psm=6/7/11/13 with learned quality-score biases. That looked better on the calibration half, but it failed on the untouched holdout: overall CER regressed from 0.342234 to 0.358352. That is exactly the kind of result the new calibration workflow is supposed to expose.
The more useful June 14, 2026 result is a calibrated Tesseract-plus-Surya script router on k2. Raw Surya was not competitive overall on the 91-sample holdout (2.198362 CER vs raw Tesseract 0.342234), but it was materially better on the Nepali slice. A routed script_select_composite candidate calibrated on the separate 89-sample half and evaluated on the untouched 91-sample holdout did better than raw Tesseract across every reported slice:
- raw tesseract holdout overall CER:
0.342234 - calibrated script router overall CER:
0.313084 - paired CER on holdout:
9wins,0losses,82ties
That is the strongest verified baseline improvement in the repo so far. It is still not a frontier claim, because it is one internal line-level split and not the full claim bundle, but it is a real out-of-sample gain and a better direction than the current TrOCR branch. The router now also supports routing_granularity=page for mixed multi-page documents; the calibrated k2 result above is still the original document-level calibration, not a new page-level benchmark.
We also ran an exploratory page-level script router on the same 91-sample holdout, reusing the document-level threshold 0.4. The result was identical to the document-level router (0.313084 overall CER, 9 wins, 0 losses, 82 ties vs raw Tesseract). That is expected for this pack because it is dominated by single-page line-crop samples; page routing needs a real multi-page document pack before it can prove anything new.
The internal image eval pack now has a real rendered multi_page slice with bundled page images and actual drawn table grids. On that small rendered smoke pack, the plain script router already beat Tesseract strongly on text (0.243224 vs 0.540584 overall CER) and on the dedicated table page (table_cell_f1 1.0 vs 0.0). A follow-up exploratory model with secondary_structure_backfill=true kept the same CER and backfilled Surya table structure on the multi-page report, lifting aggregate table_cell_f1 from 0.5 to 1.0 on that smoke pack. That is still not claim-grade evidence because the pack is tiny and only clean, but it is a real document-capability improvement.
The next step was to stop calling it smoke evidence and run the same backfill router on a claim-ready rendered image pack. That broader internal pack contains 25 samples across clean, scan, blur, low_contrast, and skew, and its audit passed cleanly. The calibrated backfill router also passed preflight-claim on that pack. Against raw Tesseract on the same rendered claim pack it still held up on text and structure:
- overall CER:
0.248654vs0.689214 - blur CER:
0.260039vs0.991613 - scan CER:
0.237424vs0.593631 - skew CER:
0.239317vs0.766067 - aggregate
table_cell_f1:0.955556vs0.0 - aggregate
table_exact_match:0.8vs0.0 - paired CER:
9wins,1loss,15ties
That result is good enough to keep and bad enough to describe plainly. The multi-page slice tied Tesseract on CER (0.315789 each) while still recovering table structure that Tesseract missed (table_cell_f1 0.911111 vs 0.0). The form slice regressed slightly on CER (0.231933 vs 0.230010). Aggregate reading-order pair accuracy on this rendered pack is also still worse than Tesseract (0.764 vs 0.816). So the current candidate is meaningfully better on OCR robustness and table extraction for this internal rendered pack, but it is not yet a clean document-understanding leader.
We then widened the comparison beyond Tesseract. Two more June 14, 2026 checks on k2 matter:
- raw Surya on the same
25-sample rendered claim pack is better on text CER than the calibrated backfill router:0.195260vs0.248654 - but the router is still not pointless: it ties Surya on aggregate
table_cell_f1(0.955556each) and is slightly better on aggregatereading_order_pair_accuracy(0.764000vs0.750909)
That means the current routed candidate is still not “better than what is out there” on this rendered document pack. Raw Surya is the stronger text OCR baseline here. The router is only defending a narrower position: it preserves comparable structure while staying closer to the existing Tesseract-centered stack.
We also fixed a real integration bug in the local Paddle baseline. paddleocr 3.7.0 on k2 returns v3 OCRResult objects, and the old adapter in this repo treated them like the older tuple/list API and silently dropped their text. After fixing that parser and installing paddlepaddle 3.3.1, stock-paddle became a real benchmark target on k2. On this same rendered pack it is still a weak baseline overall:
- stock-Paddle overall CER:
1.749081 - stock-Paddle aggregate
table_cell_f1:0.0 - stock-Paddle aggregate
reading_order_pair_accuracy:1.0
So the current picture is sharper now, not prettier: the routed candidate beats Tesseract and this stock-Paddle configuration on OCR robustness and table extraction, but it still loses to raw Surya on text CER.
We then used the new filter-manifest helper to run a broader but still tractable rendered-document comparison on k2: a 5-sample blur-only subset spanning paragraph, table, form, figure, and multi-page layouts. All 30 runs completed without error across candidate, tesseract, surya, stock-paddle, glm-ocr, and paddleocr-vl. The result sharpened the ranking again:
- candidate CER:
0.223273 - raw Surya CER:
0.197601 - Tesseract CER:
0.732364 - stock-Paddle CER:
2.810426 - GLM-OCR CER:
2.820269 - PaddleOCR-VL CER:
18.470663
On that subset, the current backfill candidate still held the structure line where Tesseract and the weaker VLM baselines collapsed (table_cell_f1 = 1.0 for the candidate versus 0.0 for Tesseract, stock-Paddle, GLM-OCR, and PaddleOCR-VL). But it still did not beat raw Surya on text CER. That keeps the same honest conclusion intact: on rendered document OCR text, the strongest baseline in this repo is still Surya, not the current routed candidate.
The stricter rendered-document result is now explicit too. On k2, a larger rendered claimpack-rendered-v2 split was calibrated separately and evaluated on an untouched 50-sample holdout. That calibration selected primary_script_threshold=0.0, so the routed script_select_composite collapsed to "always pick Surya" on the calibration set. On the holdout:
- candidate CER:
0.180893 - raw Surya CER:
0.180893 - candidate
table_cell_f1:0.947500 - raw Surya
table_cell_f1:0.970833
That is the ceiling of the current branch, not a win. The candidate no longer even has a text-vs-structure tradeoff story there; on this larger rendered holdout it effectively degenerates to Surya on text and still loses slightly on table structure. The claim guardrails now reject this case directly: routed candidates that collapse to one engine across all calibration samples fail candidate-calibration in both preflight-claim and review-claim.
We also tested whether a quality-based Surya/Tesseract selector could recover anything on that same rendered-v2 setup. It did not. The rendered-v2 Surya quality router calibrated to selected_threshold=0.0, then landed at:
- candidate CER:
0.181128 - raw Surya CER:
0.180893 - candidate
table_cell_f1:0.947500 - raw Surya
table_cell_f1:0.947500 - paired CER vs Surya:
0wins,1loss,49ties
That is not a distinct better engine. It is basically Surya with one extra mistake.
We then tested line_align_composite on the same rendered-v2 holdout: keep Surya text, align it to Tesseract's line scaffold, and see whether the ordering gain is worth the merge. It was not:
- candidate CER:
0.310549 - raw Surya CER:
0.180893 - candidate
table_cell_f1:0.897500 - raw Surya
table_cell_f1:0.970833 - candidate
reading_order_pair_accuracy:0.792727 - raw Surya
reading_order_pair_accuracy:0.750909 - paired CER vs Surya:
0wins,7losses,43ties
That is another useful paper result, but not a winning model branch. Better line ordering alone did not rescue the Surya/Tesseract composite family.
The upper bound is now measured too. A sample-level oracle that chooses the better of raw Surya and raw Tesseract per holdout sample using ground-truth CER landed at:
- oracle CER:
0.180529 - raw Surya CER:
0.180893 - raw Tesseract CER:
0.714207 - oracle choices: Surya
49, Tesseract1 - paired CER vs Surya:
1win,0losses,49ties
That closes the routing branch for text OCR. There is almost no remaining sample-level headroom in the Surya/Tesseract component family on rendered-v2. The next credible model-side step has to use a genuinely stronger recognizer or document model, not another selector over these same two engines.
See docs/EXPERIMENTS.md for the exact commands, artifact paths, and the current evidence gap.
If you are turning this work into a paper, start from docs/PAPER_NOTES.md. Then use docs/PAPER_RESULTS.md for the current generated comparison tables and branch chronology tied to local artifacts.