Papers › What Is Wrong With Scene Text Recognition Model Comparisons? Dataset and Model Analysis

What Is Wrong With Scene Text Recognition Model Comparisons? Dataset and Model Analysis

3 Apr 2019ICCV 2019 10arXiv:1904.01906archive 2025-07-28

Jeonghun Baek, Geewook Kim, Junyeop Lee, Sungrae Park, Dongyoon Han, Sangdoo Yun, Seong Joon Oh, Hwalsuk Lee

Many new proposals for scene text recognition (STR) models have been introduced in recent years. While each claim to have pushed the boundary of the technology, a holistic and fair comparison has been largely missing in the field due to the inconsistent choices of training and evaluation datasets. This paper addresses this difficulty with three major contributions. First, we examine the inconsistencies of training and evaluation datasets, and the performance gap results from inconsistencies. Second, we introduce a unified four-stage STR framework that most existing STR models fit into. Using this framework allows for the extensive evaluation of previously proposed STR modules and the discovery of previously unexplored module combinations. Third, we analyze the module-wise contributions to performance in terms of accuracy, speed, and memory demand, under one consistent set of training and evaluation datasets. Such analyses clean up the hindrance on the current comparisons to understand the performance gain of the existing modules.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

No sample from the archive's official repository (clovaai/deep-text-recognition-benchmark) is linked to this paper; the 19 samples below come from 4 community repositories. Syntology harvested code from clovaai/deep-text-recognition-benchmark for another paper.

clovaai/deep-text-recognition-benchmark: Syntology's graph links these samples to COO: Comic Onomatopoeia Dataset for Recognizing Arbitrary or Truncated Texts (arXiv:2207.04675; that paper's own run record: 2 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method.

Syntology 19 code samples harvested from 4 repositories linked to this paper: 17 ran (of which 0 constructed an object rather than computing a result; 17 with no instrument failure: 0 honoured, 0 violated, 17 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 19 samples from 4 repositories, 17 ran (17 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 3 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-24 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

13 repositories listed; official and paper-mentioned ones first.

clovaai/deep-text-recognition-benchmark officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to COO: Comic Onomatopoeia Dataset for Recognizing Arbitrary or Truncated Texts (arXiv:2207.04675; that paper's own run record: 2 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
2023-MindSpore-1/ms-code-58 mentioned on GitHubmindsporeSyntology: not harvested report
Eom-taeseon/CV_SceneTextRecognition mentioned on GitHubpytorchApache-2.0Syntology: 7 samples, 5 ran (0 instrument-failed) · 2 unverified report
JoegameZhou/cnnctc mentioned on GitHubmindsporeApache-2.0Syntology: 7 samples, 7 ran (0 instrument-failed) · 0 unverified report
Luckygyana/Invo-AI mentioned on GitHubpytorchGPL-3.0Syntology: not harvested report
RobotMobile/cv-deep-learning-paper-review mentioned on GitHubSyntology: not harvested report
dmitrijsk/attentionhtr mentioned on GitHubpytorchApache-2.0Syntology: 3 samples, 3 ran (0 instrument-failed) · 0 unverified report
jakartaresearch/receipt-ocr mentioned on GitHubpytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Character Region Awareness for Text Detection (arXiv:1904.01941; that paper's own run record: 25 ran (of which 0 constructed an object rather than computing a result; 20 with no instrument failure: 1 honoured, 0 violated, 19 with no contract checked; 5 where Syntology's instrument failed) · 15 unverified); nothing checks that they implement this paper's method. report
luozhilin99/cnnctc mentioned on GitHubmindsporeSyntology: not harvested report
roatienza/deep-text-recognition-benchmark mentioned on GitHubpytorchApache-2.0Syntology: 2 samples, 2 ran (0 instrument-failed) · 0 unverified report
2023-MindSpore-4/Code8 mindsporeSyntology: not harvested report
2024-MindSpore-1/Code7 mindsporeSyntology: not harvested report
mindspore-ai/models mindsporeSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to AdaBin: Improving Binary Neural Networks with Adaptive Binary Sets (arXiv:2208.08084; that paper's own run record: 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

19 samples harvested: 17 ran (of which 0 constructed an object rather than computing a result; 17 with no instrument failure: 0 honoured, 0 violated, 17 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

17ran
2unverified

Licence: 0 of the 19 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 4 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. For 1 sample that ran, the graph records a signature this page does not show: an argument's recorded type or element kind is a printout of an object in Syntology's harness (such as a mock object, a class or a pandas printout), not the type of an input, so it does not describe the call's shape. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

Eom-taeseon/CV_SceneTextRecognition community (archive-listed) 7 samples, 5 ran (0 instrument-failed) · 2 unverified
checkImageIsValid in 5 papers create_lmdb_dataset.py ran Apache-2.0 (permissive) · c7b92e1633b0d2da · report fixture: signature imageBin:bytes/0/? · returned bool · level recorded 2026-09-26
get_args in 84 papers utils.py ran Apache-2.0 (permissive) · ce83d7152f32b55d · report fixture: signature is_train:bool/0/bool · returned Namespace · level recorded 2026-09-24
get_device in 101 papers utils.py ran Apache-2.0 (permissive) · 291192e39061a450 · report fixture: signature verbose:bool/0/bool · returned device · level recorded 2026-09-26
isless dataset.py ran fingerprinted Apache-2.0 (permissive) · 8f99ed40edd07e1e · report fixture: signature prob:float/0/float · returned bool · level recorded 2026-09-26
tensor2im in 30 papers dataset.py ran Apache-2.0 (permissive) · b78e81e855133e45 · report fixture: returned ndarray · level recorded 2026-09-26
create_vitstr modules/vitstr.py unverified Apache-2.0 (permissive) · 8a4fd52ddbb2af6b · report
get_flops in 14 papers predict.py unverified Apache-2.0 (permissive) · edfd158c1fa7f00e · report
JoegameZhou/cnnctc community (archive-listed) 7 samples, 7 ran (0 instrument-failed) · 0 unverified
a_cosine_learning_rate in 5 papers src/lr_schedule.py ran Apache-2.0 (permissive) · 316fb42e9e6ed79e · report fixture: signature current_step:int/0/int, base_lr:float/0/float, warmup_steps:int/0/int, decay_steps:int/0/int · returned float · level recorded 2026-09-24
calcul_acc in 6 papers postprocess.py ran fingerprinted Apache-2.0 (permissive) · 89c58f89ba416399 · report fixture: signature labels:list/1/int, preds:list/1/int · returned float · level recorded 2026-09-24
dynamic_lr in 7 papers src/lr_schedule.py ran Apache-2.0 (permissive) · fe2c44cd738c9d3e · report fixture: signature config:Config/0/?, steps_per_epoch:int/0/int · returned list · level recorded 2026-09-24
linear_warmup_learning_rate in 8 papers src/lr_schedule.py ran fingerprinted Apache-2.0 (permissive) · d6a99ec714147ac1 · report fixture: signature current_step:int/0/int, warmup_steps:int/0/int, base_lr:float/0/float, init_lr:float/0/float · returned float · level recorded 2026-09-24
merge in 85 papers src/model_utils/config.py ran Apache-2.0 (permissive) · b2108b927c53418b · report fixture: signature args:SimpleArgs/0/?, cfg:dict/0/? · returned dict · level recorded 2026-09-24
parse_cli_to_yaml in 29 papers src/model_utils/config.py ran Apache-2.0 (permissive) · 3498f707d22460cd · report fixture: signature parser:ArgumentParser/0/?, cfg:dict/0/?, helper:dict/0/?, choices:dict/0/?, cfg_path:str/0/str · returned Namespace · level recorded 2026-09-24
parse_yaml in 32 papers src/model_utils/config.py ran Apache-2.0 (permissive) · c8d98ae32946f6f0 · report fixture: signature yaml_path:str/0/str · returned tuple · level recorded 2026-09-24
dmitrijsk/attentionhtr community (archive-listed) 3 samples, 3 ran (0 instrument-failed) · 0 unverified
change_args datasets/process_imgur5k.py ran Apache-2.0 (permissive) · 7df8b90dc252b116 · report fixture: signature args:Args/0/?, n_img:int/0/int · returned Args · level recorded 2026-09-24
get_image_split datasets/process_imgur5k.py ran Apache-2.0 (permissive) · 55becdbd1817adde · report fixture: signature img_name:str/0/str, split_idx:dict/0/? · returned str · level recorded 2026-09-24
resize in 108 papers
census: 10 implementations from 14 papers, 5 distinct outputs across 2 buckets, one shared input per bucket
datasets/process_imgur5k.py ran fingerprinted Apache-2.0 (permissive) · e7cc5ea8a6820dc3 · report fixture: signature img:ndarray/3/int, desired_height:int/0/int · returned ndarray · level recorded 2026-09-24
roatienza/deep-text-recognition-benchmark community (archive-listed) 2 samples, 2 ran (0 instrument-failed) · 0 unverified
get_args in 84 papers utils.py ran Apache-2.0 (permissive) · 98206309c9298631 · report fixture: signature is_train:bool/0/bool · returned Namespace · level recorded 2026-09-24
img2text infer.py ran Apache-2.0 (permissive) · d8e30cd1ae314959 · report fixture: signature model:callable/0/?, images:list/1/Tensor, converter:Converter/0/? · returned list · level recorded 2026-09-24

Tasks

Image MatchingScene Text Recognitionmodel

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Scene Text Recognition ICDAR 2003 Baek et al. Accuracy 94.4 #7 of 12 Archive leaderboard report
Scene Text Recognition ICDAR2013 Baek et al. Accuracy 92.3 #31 of 38 Archive leaderboard report
Scene Text Recognition ICDAR2015 Baek et al. Accuracy 71.8 #26 of 27 Archive leaderboard report
Scene Text Recognition SVT Baek et al. Accuracy 87.5 #31 of 37 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections