Papers › FRNet: Frustum-Range Networks for Scalable LiDAR Segmentation
FRNet: Frustum-Range Networks for Scalable LiDAR Segmentation
Xiang Xu, Lingdong Kong, Hui Shuai, Qingshan Liu
LiDAR segmentation has become a crucial component of advanced autonomous driving systems. Recent range-view LiDAR segmentation approaches show promise for real-time processing. However, they inevitably suffer from corrupted contextual information and rely heavily on post-processing techniques for prediction refinement. In this work, we propose FRNet, a simple yet powerful method aimed at restoring the contextual information of range image pixels using corresponding frustum LiDAR points. First, a frustum feature encoder module is used to extract per-point features within the frustum region, which preserves scene consistency and is critical for point-level predictions. Next, a frustum-point fusion module is introduced to update per-point features hierarchically, enabling each point to extract more surrounding information through the frustum features. Finally, a head fusion module is used to fuse features at different levels for final semantic predictions. Extensive experiments conducted on four popular LiDAR segmentation benchmarks under various task setups demonstrate the superiority of FRNet. Notably, FRNet achieves 73.3% and 82.5% mIoU scores on the testing sets of SemanticKITTI and nuScenes. While achieving competitive performance, FRNet operates 5 times faster than state-of-the-art approaches. Such high efficiency opens up new possibilities for more scalable LiDAR segmentation. The code has been made publicly available at https://github.com/Xiangxu-0103/FRNet.
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="2312.04484")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2312.04484", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2312.04484")
Code
Syntology 19 code samples harvested from 2 repositories linked to this paper: 14 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 2 honoured, 0 violated, 7 with no contract checked; 5 where Syntology's instrument failed) · 5 unverified. Where Syntology's instrument failed: 4 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.
By repository: official repository: 19 samples from 2 repositories, 14 ran (9 with no instrument failure; 5 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.
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
19 samples harvested: 14 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 2 honoured, 0 violated, 7 with no contract checked; 5 where Syntology's instrument failed) · 5 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.
Licence: 18 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 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. 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.
census: 18 implementations from 25 papers, 10 distinct outputs across 6 buckets, one shared input per bucket frnet/models/losses/boundary_loss.py unverified Apache-2.0 (permissive) ·
3dd5e5e1db226e90 · report
9aee2cc91c8abd60 · report
fixture: signature p:ParameterSet/0/?, pc:ndarray/2/float · returned ndarray · level recorded 2026-09-24 0140b17b497f7722 · report
fixture: signature angles:ndarray/2/float · returned tuple · level recorded 2026-09-24 ee792b6d83528ceb · report
fixture: signature snowfall_rate:float/0/float, terminal_velocity:float/0/float, snow_density:float/0/float · returned float · level recorded 2026-09-24 3d0bbf09504533a0 · report
fixture: signature pc:ndarray/2/float, min_dist:float/0/float, max_dist:float/0/float · returned ndarray · level recorded 2026-09-24 cbe622a1a2d3a0dc · report
fixture: signature pc:ndarray/2/float, l:float/0/float, w:float/0/float, h:float/0/float · returned ndarray · level recorded 2026-09-24 a7437aeafce98daa · report
fixture: signature dirname:str/0/str · returned list · level recorded 2026-09-24 f01d04ede070478d · report
fixture: signature pts_rect:ndarray/2/float, img_shape:tuple/1/int, calib:MockCalib/0/? · returned ndarray · level recorded 2026-09-24 c67f2408fbc802c5 · report
fixture: signature points:ndarray/2/float · returned ndarray · level recorded 2026-09-24 d6ce9efdedbab114 · report
fixture: signature pointcloud:ndarray/2/float, percentage:float/0/float · returned tuple · level recorded 2026-09-24 6e80b332e869fc92 · report
fixture: signature rainfall_rate:float/0/float, terminal_velocity:float/0/float, snowflake_density:float/0/float, snowflake_diameter:float/0/float · returned float · level recorded 2026-09-24 844e02f134b3dfc4 · report
fixture: signature snowfall_rate:float/0/float, terminal_velocity:float/0/float, snowflake_density:float/0/float, snowflake_diameter:float/0/float · returned float64 · level recorded 2026-09-24 f8128e47543b84c3 · report
fixture: signature a:list/1/int, n:int/0/int · returned generator · level recorded 2026-09-24 42c4f33782806a6c · report
fixture: signature angles:ndarray/2/float, right_angle:float/0/float, left_angle:float/0/float, right_angle_hit:ndarray/1/bool, left_angle_hit:ndarray/1/bool · returned ndarray · level recorded 2026-09-24 c325d7f76bd1d254 · report
fixture: signature lines:tuple/1/ndarray, center_angles:ndarray/2/float · returned ndarray · level recorded 2026-09-24 b83474507717a738 · report
6fbbfd21ea101ff0 · report
5eb857761017e97b · report
6981e9a2b99c60d9 · report
Tasks
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| 3D Semantic Segmentation | SemanticKITTI | FRNet | test mIoU | 73.3% | #6 of 45 | Archive leaderboard | report |
| 3D Semantic Segmentation | SemanticKITTI | FRNet | val mIoU | 68.7% | #6 of 45 | Archive leaderboard | report |
| 3D Semantic Segmentation | nuScenes | FRNet | mIoU | 82.5% | #2 of 3 | Archive leaderboard | report |
| LIDAR Semantic Segmentation | nuScenes | FRNet | test mIoU | 0.825 | #4 of 36 | Archive leaderboard | report |
| LIDAR Semantic Segmentation | nuScenes | FRNet | val mIoU | 0.790 | #4 of 36 | 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