Papers › Fourier Contour Embedding for Arbitrary-Shaped Text Detection

Fourier Contour Embedding for Arbitrary-Shaped Text Detection

21 Apr 2021CVPR 2021 2021 4arXiv:2104.10442archive 2025-07-28

Yiqin Zhu, Jianyong Chen, Lingyu Liang, Zhanghui Kuang, Lianwen Jin, Wayne Zhang

One of the main challenges for arbitrary-shaped text detection is to design a good text instance representation that allows networks to learn diverse text geometry variances. Most of existing methods model text instances in image spatial domain via masks or contour point sequences in the Cartesian or the polar coordinate system. However, the mask representation might lead to expensive post-processing, while the point sequence one may have limited capability to model texts with highly-curved shapes. To tackle these problems, we model text instances in the Fourier domain and propose one novel Fourier Contour Embedding (FCE) method to represent arbitrary shaped text contours as compact signatures. We further construct FCENet with a backbone, feature pyramid networks (FPN) and a simple post-processing with the Inverse Fourier Transformation (IFT) and Non-Maximum Suppression (NMS). Different from previous methods, FCENet first predicts compact Fourier signatures of text instances, and then reconstructs text contours via IFT and NMS during test. Extensive experiments demonstrate that FCE is accurate and robust to fit contours of scene texts even with highly-curved shapes, and also validate the effectiveness and the good generalization of FCENet for arbitrary-shaped text detection. Furthermore, experimental results show that our FCENet is superior to the state-of-the-art (SOTA) methods on CTW1500 and Total-Text, especially on challenging highly-curved text subset.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

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

Syntology 7 code samples harvested from 2 repositories linked to this paper: 5 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 1 violated, 3 with no contract checked; 1 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 7 samples from 2 repositories, 5 ran (4 with no instrument failure; 1 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 5 of its repositories that Syntology harvested for other papers:

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

ElectronicBabylonianLiterature/ebl-ai-api mentioned on GitHubpytorchMITSyntology: not harvested report
gxym/textbpn-plus-plus mentioned on GitHubpytorchSyntology: not harvested report
gxym/textbpn-puls-plus mentioned on GitHubpytorchSyntology: not harvested report
zhiminzhang0830/FCENet_Paddle mentioned on GitHubpaddleApache-2.0Syntology: 6 samples, 4 ran (0 instrument-failed) · 2 unverified report
MindCode-4/code-10 mindsporeSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
MindCode-4/code-14 mindsporeSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to IMMA: Immunizing text-to-image Models against Malicious Adaptation (arXiv:2311.18815; that paper's own run record: 11 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 1 where Syntology's instrument failed) · 6 unverified); nothing checks that they implement this paper's method. report
MindSpore-scientific/code-12 mindsporeSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Block Diffusion: Interpolating Between Autoregressive and Diffusion Language Models (arXiv:2503.09573; that paper's own run record: 14 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 7 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
PaddlePaddle/PaddleOCR paddleApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to KRETA: A Benchmark for Korean Reading and Reasoning in Text-Rich VQA Attuned to... (arXiv:2508.19944; that paper's own run record: 6 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 3 violated, 0 with no contract checked; 3 where Syntology's instrument failed) · 2 unverified); nothing checks that they implement this paper's method. report
mindspore-ai/contrib mindsporeSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Unified Embedding: Battle-Tested Feature Representations for Web-Scale ML Systems (arXiv:2305.12102; that paper's own run record: 2 ran (of which 1 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 1 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
mindspore-lab/mindocr mindsporenot reachable when probed 2026-09-17 — repositories for recent papers often appear after camera-readySyntology: not harvested report
open-mmlab/mmocr pytorchApache-2.0Syntology: not harvested report
pwc-1/Paper-9 mindsporeSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to RandAugment: Practical automated data augmentation with a reduced search space (arXiv:1909.13719; that paper's own run record: 58 ran (of which 1 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 1 violated, 6 with no contract checked; 51 where Syntology's instrument failed) · 7 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

7 samples harvested: 5 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 1 violated, 3 with no contract checked; 1 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.

1ran · violated contract
1ran · our draft was wrong
3ran
2unverified

Licence: 1 of the 7 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 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”. “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.

zhiminzhang0830/FCENet_Paddle community (archive-listed) 6 samples, 4 ran (0 instrument-failed) · 2 unverified
ohem_single ppocr/losses/det_basic_loss.py ran Apache-2.0 (permissive) · ea3ff3c86a936513 · report fixture: signature score:ndarray/2/float, gt_text:ndarray/2/float, training_mask:ndarray/2/float, ohem_ratio:float/0/float · returned ndarray · level recorded 2026-09-24
parse_lang paddleocr.py ran Apache-2.0 (permissive) · 668e2bee747f1417 · report fixture: signature lang:str/0/str · returned tuple · level recorded 2026-09-24
read in 34 papers PPOCRLabel/PPOCRLabel.py ran Apache-2.0 (permissive) · 14b9c019942ef1b5 · report fixture: signature filename:str/0/str, default:NoneType/0/? · returned bytes · level recorded 2026-09-24
str2bool in 533 papers PPOCRLabel/PPOCRLabel.py ran · violated contract Apache-2.0 (permissive) here; the stored copy is pointer only · 7373b3408ee13c1c · report fixture: signature v:str/0/str · returned bool · level recorded 2026-09-22
inverted PPOCRLabel/PPOCRLabel.py unverified Apache-2.0 (permissive) · 0769a6bb4dc29a4c · report
multi_apply in 11 papers ppocr/losses/det_fce_loss.py unverified Apache-2.0 (permissive) · 3803145597ea6de4 · report
MindCode-4/code-10 community (archive-listed) 1 sample, 1 ran (1 instrument-failed) · 0 unverified
fourier_transform FCENet/util/misc.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) · 7a656add0ef9fc15 · report fixture: signature polygon:ndarray/2/float, k:int/0/int · returned ndarray · level recorded 2026-09-22

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for Fourier Contour Embedding (FCE) (graph method: Fourier Contour Embedding (FCE)). 1 brick; individually on a fixture: 1 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.

  1. fourier_transform entry · level 1 · ran · our draft was wrong · 7a656add0ef9fc15

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2104.10442") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Scene Text DetectionText Detection

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Introduced by this paper: Fourier Contour Embedding

Fourier Contour Embedding

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