Papers › SFPNet: Sparse Focal Point Network for Semantic Segmentation on General LiDAR Point Clouds

SFPNet: Sparse Focal Point Network for Semantic Segmentation on General LiDAR Point Clouds

16 Jul 2024arXiv:2407.11569archive 2025-07-28

Yanbo Wang, Wentao Zhao, Chuan Cao, Tianchen Deng, Jingchuan Wang, Weidong Chen

Although LiDAR semantic segmentation advances rapidly, state-of-the-art methods often incorporate specifically designed inductive bias derived from benchmarks originating from mechanical spinning LiDAR. This can limit model generalizability to other kinds of LiDAR technologies and make hyperparameter tuning more complex. To tackle these issues, we propose a generalized framework to accommodate various types of LiDAR prevalent in the market by replacing window-attention with our sparse focal point modulation. Our SFPNet is capable of extracting multi-level contexts and dynamically aggregating them using a gate mechanism. By implementing a channel-wise information query, features that incorporate both local and global contexts are encoded. We also introduce a novel large-scale hybrid-solid LiDAR semantic segmentation dataset for robotic applications. SFPNet demonstrates competitive performance on conventional benchmarks derived from mechanical spinning LiDAR, while achieving state-of-the-art results on benchmark derived from solid-state LiDAR. Additionally, it outperforms existing methods on our novel dataset sourced from hybrid-solid LiDAR. Code and dataset are available at https://github.com/Cavendish518/SFPNet and https://www.semanticindustry.top.

PaperPDFCodeCode 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 10 code samples harvested from 1 repository linked to this paper: 8 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 2 honoured, 0 violated, 3 with no contract checked; 3 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 2 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: 10 samples from 1 repository, 8 ran (5 with no instrument failure; 3 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-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

Cavendish518/SFPNet officialmentioned in papermentioned on GitHubpytorchNOASSERTIONSyntology: 10 samples, 8 ran (3 instrument-failed) · 2 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

10 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 2 honoured, 0 violated, 3 with no contract checked; 3 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 last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · honoured contract
2ran · our draft was wrong
1ran; the contract check could not run
3ran
2unverified

Licence: 10 of the 10 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 Cavendish518/SFPNet. “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.

Cavendish518/SFPNet official repository 10 samples, 8 ran (3 instrument-failed) · 2 unverified
collation_fn_voxelmean_tta Demo/demo_util.py ran · our draft was wrong licence not identified · pointer only · 72f7edec803ad943 · report fixture: signature batch_list:list/1/tuple · returned list · level recorded 2026-09-24
colorize in 60 papers util/common_util.py ran licence not identified · pointer only · 1dad93b61e98c32e · report fixture: signature gray:ndarray/2/int, palette:list/1/int · returned Image · level recorded 2026-09-24
fnv_hash_vec in 14 papers util/voxelize.py ran · honoured contract fingerprinted no licence file found · pointer only · 0086c892bd1df796 · report fixture: signature arr:ndarray/2/int · returned ndarray · level recorded 2026-09-25
get_logger in 383 papers util/logger.py ran licence not identified · pointer only · e985f384ed063aef · report fixture: signature output:NoneType/0/?, color:bool/0/bool, name:str/0/str, abbrev_name:str/0/str · returned Logger · level recorded 2026-09-24
intersectionAndUnion in 16 papers util/common_util.py ran; the contract check could not run (RAISES) licence not identified · pointer only · 2a66f4ab6863908c · report fixture: signature output:ndarray/2/int, target:ndarray/2/int, K:int/0/int, ignore_index:int/0/int · returned tuple · level recorded 2026-09-24
load_cfg_from_cfg_file in 24 papers util/config.py ran · our draft was wrong no licence file found · pointer only · 277a13798d6d6981 · report fixture: signature file:str/0/str · returned CfgNode · level recorded 2026-09-25
ravel_hash_vec in 13 papers util/voxelize.py ran · honoured contract fingerprinted no licence file found · pointer only · afdc8ad15d9098b8 · report fixture: signature arr:ndarray/2/int · returned ndarray · level recorded 2026-09-25
voxelize util/voxelize.py ran licence not identified · pointer only · c8e625f7af34ae7b · report fixture: signature coord:ndarray/2/float, voxel_size:float/0/float, hash_type:str/0/str, mode:int/0/int · returned tuple · level recorded 2026-09-24
intersectionAndUnionGPU in 10 papers util/common_util.py unverified licence not identified · pointer only · 136834d66336e6b9 · report
merge_cfg_from_list in 24 papers util/config.py unverified no licence file found · pointer only · 4efe685c6fb1ec11 · report

Tasks

LIDAR Semantic SegmentationSemantic Segmentation

Datasets

Introduced by this paper, per the archive.

S.MID

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
LIDAR Semantic Segmentation S.MID SFPNet val mIoU 72.8% #1 of 4 Archive leaderboard report
LIDAR Semantic Segmentation SemanticKITTI SFPNet mIOU 70.3% #2 of 4 Archive leaderboard report
LIDAR Semantic Segmentation SemanticKITTI SFPNet val mIoU 69.2% #2 of 4 Archive leaderboard report
LIDAR Semantic Segmentation nuScenes SFPNet test mIoU 0.802 #9 of 36 Archive leaderboard report
LIDAR Semantic Segmentation nuScenes SFPNet val mIoU 0.801 #9 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