Papers › CoordFill: Efficient High-Resolution Image Inpainting via Parameterized Coordinate Querying
CoordFill: Efficient High-Resolution Image Inpainting via Parameterized Coordinate Querying
Weihuang Liu, Xiaodong Cun, Chi-Man Pun, Menghan Xia, Yong Zhang, Jue Wang
Image inpainting aims to fill the missing hole of the input. It is hard to solve this task efficiently when facing high-resolution images due to two reasons: (1) Large reception field needs to be handled for high-resolution image inpainting. (2) The general encoder and decoder network synthesizes many background pixels synchronously due to the form of the image matrix. In this paper, we try to break the above limitations for the first time thanks to the recent development of continuous implicit representation. In detail, we down-sample and encode the degraded image to produce the spatial-adaptive parameters for each spatial patch via an attentional Fast Fourier Convolution(FFC)-based parameter generation network. Then, we take these parameters as the weights and biases of a series of multi-layer perceptron(MLP), where the input is the encoded continuous coordinates and the output is the synthesized color value. Thanks to the proposed structure, we only encode the high-resolution image in a relatively low resolution for larger reception field capturing. Then, the continuous position encoding will be helpful to synthesize the photo-realistic high-frequency textures by re-sampling the coordinate in a higher resolution. Also, our framework enables us to query the coordinates of missing pixels only in parallel, yielding a more efficient solution than the previous methods. Experiments show that the proposed method achieves real-time performance on the 2048×2048 images using a single GTX 2080 Ti GPU and can handle 4096×4096 images, with much better performance than existing state-of-the-art methods visually and numerically. The code is available at: https://github.com/NiFangBaAGe/CoordFill.
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):
get_harvested_code_for_paper(arxiv_id="2303.08524")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2303.08524", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2303.08524")
Code
Syntology 18 code samples harvested from 1 repository linked to this paper: 7 ran (of which 6 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 0 where Syntology's instrument failed) · 11 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.
By repository: official repository: 18 samples from 1 repository, 7 ran (7 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.
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.
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.
Code Syntology ran Syntology
18 samples harvested: 7 ran (of which 6 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 0 where Syntology's instrument failed) · 11 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.
Licence: 0 of the 18 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 nifangbaage/coordfill. “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: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.
443a27e88886f962 · report
fixture: returned BaseNetwork · level recorded 2026-09-22 62bac9f9e210efc9 · report
fixture: signature x:tuple/1/Tensor · returned Tensor · level recorded 2026-09-24 1fbf7982390f137b · report
fixture: returned FFC_BN_ACT · level recorded 2026-09-22 50b8f556e23dc337 · report
fixture: returned FourierUnit · level recorded 2026-09-22 6fee4cc5e77c63d6 · report
fixture: returned ParaGenNet · level recorded 2026-09-22 ec5b3c5fc06f3065 · report
fixture: returned PixelQueryNet · level recorded 2026-09-22 a59dece88a263461 · report
fixture: returned SELayer · level recorded 2026-09-22 42961bc165cc995c · report
5ce9dfb242e8a34b · report
0a70b66723b3cedd · report
fe401746b27bf76b · report
7eba59f96acf99cd · report
ab3392be53d55e96 · report
1a5021c2953d66fe · report
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 CoordFill (graph method: CoordFill). 19 bricks; individually on a fixture: 8 ran (of which 6 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 1 where Syntology's instrument failed) · 11 unverified. The assembly has not been run end-to-end.
- CoordFill entry · level 0 · unverified ·
771402ef412f4280 - AttFFCResNetGenerator model · level 0 · unverified ·
42961bc165cc995c - CoordFillGenerator helper · level 0 · unverified ·
5ce9dfb242e8a34b - FFCResNetGenerator helper · level 0 · unverified ·
fe401746b27bf76b - MLPModel helper · level 0 · unverified ·
a31edbc4f9e59c23 - AttFFC model · level 0 · unverified ·
9cf9b865af2e1c2d - ConcatTupleLayer helper · level 1 · ran ·
62bac9f9e210efc9 - FFC_BN_ACT helper · level 1 · ran ·
1fbf7982390f137b - BaseNetwork helper · level 1 · ran ·
443a27e88886f962 - ParaGenNet model · level 1 · ran ·
6fee4cc5e77c63d6 - PixelQueryNet model · level 1 · ran ·
ec5b3c5fc06f3065 - FFCResnetBlock helper · level 0 · unverified ·
7eba59f96acf99cd - LearnableSpatialTransformWrapper helper · level 0 · unverified ·
ab3392be53d55e96 - get_activation helper · level 1 · ran · our draft was wrong ·
b67152b806ff0b3b - FFC helper · level 0 · unverified ·
0a70b66723b3cedd - _get_coords helper · level 0 · unverified ·
03bfb68584c430f0 - SpectralTransform helper · level 0 · unverified ·
1a5021c2953d66fe - FourierUnit helper · level 1 · ran ·
50b8f556e23dc337 - SELayer helper · level 1 · ran ·
a59dece88a263461
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="2303.08524") returns these assemblies with each brick's role and wiring (how to connect).
Tasks
1 archive task tag without a task page not shown.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Methods
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