Papers › LION: Linear Group RNN for 3D Object Detection in Point Clouds

LION: Linear Group RNN for 3D Object Detection in Point Clouds

25 Jul 2024arXiv:2407.18232archive 2025-07-28

Zhe Liu, Jinghua Hou, Xinyu Wang, Xiaoqing Ye, Jingdong Wang, Hengshuang Zhao, Xiang Bai

The benefit of transformers in large-scale 3D point cloud perception tasks, such as 3D object detection, is limited by their quadratic computation cost when modeling long-range relationships. In contrast, linear RNNs have low computational complexity and are suitable for long-range modeling. Toward this goal, we propose a simple and effective window-based framework built on LInear grOup RNN (i.e., perform linear RNN for grouped features) for accurate 3D object detection, called LION. The key property is to allow sufficient feature interaction in a much larger group than transformer-based methods. However, effectively applying linear group RNN to 3D object detection in highly sparse point clouds is not trivial due to its limitation in handling spatial modeling. To tackle this problem, we simply introduce a 3D spatial feature descriptor and integrate it into the linear group RNN operators to enhance their spatial features rather than blindly increasing the number of scanning orders for voxel features. To further address the challenge in highly sparse point clouds, we propose a 3D voxel generation strategy to densify foreground features thanks to linear group RNN as a natural property of auto-regressive models. Extensive experiments verify the effectiveness of the proposed components and the generalization of our LION on different linear group RNN operators including Mamba, RWKV, and RetNet. Furthermore, it is worth mentioning that our LION-Mamba achieves state-of-the-art on Waymo, nuScenes, Argoverse V2, and ONCE dataset. Last but not least, our method supports kinds of advanced linear RNN operators (e.g., RetNet, RWKV, Mamba, xLSTM and TTT) on small but popular KITTI dataset for a quick experience with our linear RNN-based framework.

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 7 code samples harvested from 1 repository linked to this paper: 6 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; 1 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 7 samples from 1 repository, 6 ran (5 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.

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

happinesslz/LION officialmentioned on GitHubpytorchApache-2.0Syntology: 7 samples, 6 ran (1 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

7 samples harvested: 6 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; 1 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 last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · our draft was wrong
5ran
1unverified

Licence: 0 of the 7 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 happinesslz/LION. “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.

happinesslz/LION official repository 7 samples, 6 ran (1 instrument-failed) · 1 unverified
cfg_from_yaml_file in 59 papers pcdet/config.py ran · our draft was wrong Apache-2.0 (permissive) · 44db2351bcc0bffe · report fixture: signature cfg_file:str/0/str, config:dict/0/? · returned EasyDict · level recorded 2026-09-25
compute_fg_mask in 36 papers pcdet/utils/loss_utils.py ran Apache-2.0 (permissive) · 65fe32ede00e7dcb · report fixture: signature gt_boxes2d:Tensor/3/float, shape:Size/1/int, downsample_factor:int/0/int, device:device/0/? · returned Tensor · level recorded 2026-09-25
get_window_coors_shift_v1 pcdet/models/backbones_3d/lion_backbone_one_stride.py ran Apache-2.0 (permissive) · db9938da0161aab2 · report fixture: signature coords:ndarray/2/int, sparse_shape:tuple/1/int, window_shape:tuple/1/int · returned tuple · level recorded 2026-09-25
get_window_coors_shift_v2 pcdet/models/backbones_3d/lion_backbone_one_stride.py ran Apache-2.0 (permissive) · 62fc63b374bdbb50 · report fixture: signature coords:Tensor/2/int, sparse_shape:tuple/1/int, window_shape:tuple/1/int, shift:bool/0/bool · returned tuple · level recorded 2026-09-25
merge_new_config in 59 papers pcdet/config.py ran Apache-2.0 (permissive) · 50e8e8cdfc5129f0 · report fixture: signature config:dict/0/?, new_config:dict/0/? · returned EasyDict · level recorded 2026-09-25
neg_loss_cornernet in 36 papers pcdet/utils/loss_utils.py ran Apache-2.0 (permissive) · 488b91d67a807558 · report fixture: signature pred:Tensor/4/float, gt:Tensor/4/float, mask:Tensor/3/float · returned Tensor · level recorded 2026-09-25
get_corner_loss_lidar in 51 papers pcdet/utils/loss_utils.py unverified Apache-2.0 (permissive) · 1780d388cc532a6d · report

Tasks

3D Object DetectionLong-range modelingMambaObject Detectionobject-detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
3D Object Detection Argoverse2 LION mAP 41.5 #1 of 2 Archive leaderboard report
3D Object Detection ONCE LION mAP 66.6 #1 of 2 Archive leaderboard report
3D Object Detection Waymo Open Dataset LION mAPH/L2 74.0 #1 of 8 Archive leaderboard report
3D Object Detection nuScenes LiDAR only LION NDS 73.9 #1 of 7 Archive leaderboard report
3D Object Detection nuScenes LiDAR only LION NDS (val) 72.1 #1 of 7 Archive leaderboard report
3D Object Detection nuScenes LiDAR only LION mAP 69.8 #1 of 7 Archive leaderboard report
3D Object Detection nuScenes LiDAR only LION mAP (val) 68.0 #1 of 7 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.

Methods

LionMamba

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