Papers › GridPull: Towards Scalability in Learning Implicit Representations from 3D Point Clouds

GridPull: Towards Scalability in Learning Implicit Representations from 3D Point Clouds

25 Aug 2023ICCV 2023 1arXiv:2308.13175archive 2025-07-28

Chao Chen, Yu-Shen Liu, Zhizhong Han

Learning implicit representations has been a widely used solution for surface reconstruction from 3D point clouds. The latest methods infer a distance or occupancy field by overfitting a neural network on a single point cloud. However, these methods suffer from a slow inference due to the slow convergence of neural networks and the extensive calculation of distances to surface points, which limits them to small scale points. To resolve the scalability issue in surface reconstruction, we propose GridPull to improve the efficiency of learning implicit representations from large scale point clouds. Our novelty lies in the fast inference of a discrete distance field defined on grids without using any neural components. To remedy the lack of continuousness brought by neural networks, we introduce a loss function to encourage continuous distances and consistent gradients in the field during pulling queries onto the surface in grids near to the surface. We use uniform grids for a fast grid search to localize sampled queries, and organize surface points in a tree structure to speed up the calculation of distances to the surface. We do not rely on learning priors or normal supervision during optimization, and achieve superiority over the latest methods in terms of complexity and accuracy. We evaluate our method on shape and scene benchmarks, and report numerical and visual comparisons with the latest methods to justify our effectiveness and superiority. The code is available at https://github.com/chenchao15/GridPull.

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

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

By repository: official repository: 6 samples from 1 repository, 5 ran (5 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 on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

chenchao15/gridpull officialmentioned in papermentioned on GitHubtfSyntology: 6 samples, 5 ran (0 instrument-failed) · 1 unverified 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.

Code Syntology ran Syntology

6 samples harvested: 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 1 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.

5ran
1unverified

Licence: 6 of the 6 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 chenchao15/gridpull. “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.

chenchao15/gridpull official repository 6 samples, 5 ran (0 instrument-failed) · 1 unverified
bigger sample_func.py ran fingerprinted no licence file found · pointer only · a97858f127d487ee · report fixture: signature p:Tensor/2/float, size:int/0/int · returned Tensor · level recorded 2026-09-24
conv1d in 31 papers tf_util.py ran no licence file found · pointer only · 054f0bfff19d6c70 · report fixture: signature inputs:SymbolicTensor/3/float, num_output_channels:int/0/int, kernel_size:int/0/int, scope:str/0/str, stride:int/0/int, padding:str/0/str, use_xavier:bool/0/bool, stddev:float/0/float, weight_decay:float/0/float, activation_fn:callable/0/?, bn:bool/0/bool, bn_decay:float/0/float, is_training:SymbolicTensor/0/bool · returned SymbolicTensor · level recorded 2026-09-24
conv2d in 119 papers tf_util.py ran no licence file found · pointer only · de5633d5eed47014 · report fixture: signature inputs:SymbolicTensor/4/float, num_output_channels:int/0/int, kernel_size:list/1/int, scope:str/0/str, stride:list/1/int, padding:str/0/str, use_xavier:bool/0/bool, stddev:float/0/float, weight_decay:float/0/float, activation_fn:callable/0/?, bn:bool/0/bool, bn_decay:float/0/float, is_training:SymbolicTensor/0/bool · returned SymbolicTensor · level recorded 2026-09-24
conv2d_transpose in 18 papers tf_util.py ran no licence file found · pointer only · eb8cf1976d6c83e3 · report fixture: signature inputs:SymbolicTensor/4/float, num_output_channels:int/0/int, kernel_size:list/1/int, scope:str/0/str, stride:list/1/int, padding:str/0/str, use_xavier:bool/0/bool, stddev:float/0/float, weight_decay:float/0/float, activation_fn:callable/0/?, bn:bool/0/bool, bn_decay:NoneType/0/?, is_training:SymbolicTensor/0/bool · returned SymbolicTensor · level recorded 2026-09-24
init_sphere sample_func.py ran no licence file found · pointer only · d2c82ff9f1587b41 · report fixture: signature radius:float/0/float, size:int/0/int · returned ndarray · level recorded 2026-09-24
get_sample in 14 papers sample_func.py unverified no licence file found · pointer only · 391e5e25e0fdcc33 · report

Tasks

Surface Reconstruction

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

SPEED

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