"I" (vowel) symbol recognition
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 18/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Ambito
- ai, machine-learning
Direzione di ricerca
The report concerns recognition on vertical layouts with preserve_aspect_ratio set to True, so start with the pre-processing path that resizes and pads crops before recognition, and with how the predictor exposes preserve_aspect_ratio and symmetric_pad to the caller. Reproduce with the attached FastAPI script on the two JSON outputs and count the "I" characters. Done would mean a documented or automatic choice that recovers the missing "I" characters without degrading horizontal text, and the issue has been open over a year with one comment and no maintainer decision, so it needs a design call first.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
🚀 The feature
"I" (vowel) symbol is systematically missing from recognition model output when using a vertical image layout with preserve _aspect_ratio option set True.
Motivation, pitch
I have discovered that the model consistently struggles with recognizing the vowel "I" in various positions within a sentence—particularly at the start and end, when the preserve_aspect_ratio parameter in the Pre-Processor is set to True.
Setting preserve_aspect_ratio=False helps mitigate the issue, but only for vertically oriented text.
However, when using horizontally oriented text setting preserve_aspect_ratio=True results in better recognition of "I" symbols occurrences.
I have also tried to change interpolation method in image resize preprocessing stage. While it improves the overall quality of recognition, it does not affect the "I"s.
Alternatives
I have three suggestions of how it is possible to fix that issue:
-
To use the conditional check to define the value of preserve_aspect_ratio parameter based on the ratio of image sides. Where the detection of horizontal text will lead to using True value and vertical - to False value.
-
Allow to choose the preserve_aspect_ratio value when calling the model.
-
To add more horizontal text samples into the datasets and retrain/finetune the detection and recognition models.
Additional context
I have tested the issue with the image composed from different sentences containing I's on the latest version of doctr library (torch).
The picture represents a comparison between two runs of ocr on the same image using different values of preserve_aspect_ratio parameter.
Colors of boxes meaning:
- the blue color is assigned to preserve_aspect_ratio set to False outlier results;
- the red color is assigned to preserve_aspect_ratio set to True outlier results;
- gray color signifies there is no change between runs;
- other colors represent partial difference.
Two json files attached show the doctr ouput on the same image. In the doctr_ocr_par_False where are 10 "I" occurrences, while in doctr_ocr_par_True where are 5 "I" occurrences.
The basic script used for tests:
from fastapi import FastAPI, UploadFile, File
import numpy as np
from doctr.models import ocr_predictor
from PIL import Image
import io
import torch
import uvicorn
app = FastAPI()
DETECTION_MODEL = "db_resnet50"
RECOGNITION_MODEL = "crnn_mobilenet_v3_large"
PRESERVE_ASPECT_RATIO = False
DEVICE = torch.device("cuda" if torch.cuda.is_available() else "cpu")
model = ocr_predictor(
pretrained=True,
det_arch=DETECTION_MODEL,
reco_arch=RECOGNITION_MODEL,
assume_straight_pages=True,
preserve_aspect_ratio=PRESERVE_ASPECT_RATIO,
symmetric_pad=True,
).to(device=DEVICE)
@app.post("/ocr")
async def ocr(file: UploadFile = File(...)):
image = await file.read()
await file.close()
doc = []
image_pil = Image.open(io.BytesIO(image)).convert("RGB")
doc.append(np.asarray(image_pil))
result = model(doc)
return result.export()
if __name__ == "__main__":
uvicorn.run("main:app", host="0.0.0.0", port=44556, reload=False
- Lingua principale
- Python
- Stelle
- 6.4k
- Fork
- 684
- Merge medio
- 20h 40m
- PR unite (30g)
- 30
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di mindee/doctr
-
ext: tests topic: ci type: enhancement
Difficoltà 3/5 Mezza giornata Idoneità per principianti 45/100
mindee/doctr#2171 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Per-task YAML configuration for the reference training scriptsForse già presa @felixdittrich92 l’ha presa 23 giorni fa. Apertaext: references topic: documentation type: new feature
mindee/doctr#2149 · 1 commento · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
Release tracker - v1.2.0Forse di nuovo libera @felixdittrich92 l’ha presa 65 giorni fa e non c’è nessuna pull request aperta. Apertacritical
mindee/doctr#2126 · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
[table structure] Extend table structure datasetForse di nuovo libera @simont2k l’ha presa 86 giorni fa e non c’è nessuna pull request aperta. Apertatopic: table comprehension
mindee/doctr#2119 · 1 commento · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
type: enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 12/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di mindee/doctr
Issue simili
-
[Bug]: Revit selector reads process ids 2000-2099 as years (flaky AgentClientTests.AYearOrAProcessIdSelectsTheHost)Forse già presa @Wurschdhaud l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
pyrevitlabs/pyRevit#3817 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
521xueweihan/HelloGitHub#4074 ·
-
follow-up
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 1 giorno
-
Helm chart: allow setting ingressClassName on the IngressForse già presa @commarla l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
pgadmin-org/pgadmin4#10658 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100