Lidar-inertial odometry (LIO) has an efficiency problem. High-resolution lidars produce millions of points per second that must be processed online on the resource-constrained hardware of robots, cars, or drones, yet most LIO methods neither bound their memory nor report their compute footprint. We introduce Pelorus, a resource-aware LIO with a fixed-capacity multiresolution map of voxelized normal distributions and an iterated equivariant state estimator. A relevance-based eviction keeps the map memory bounded, and a maturity-weighted map update suppresses inconsistent observations. The pipeline runs in parallel on CPUs and GPUs. On five sequences from three public datasets, Pelorus achieves the lowest relative pose error in seven of ten metrics with a small, bounded memory footprint and, with GPU offloading, the lowest CPU load of all compared methods. On an NVIDIA Jetson Orin NX, it processes a 128-beam lidar at 10 Hz. Pelorus is open source with CUDA, Vulkan, and Metal backends.
Figures & tables
Fig. 1: Memory and logical CPU cores of LIO systems on helipr/town02:ouster in logarithmic scale, measured on an Intel Core i7-14700 with an NVIDIA GeForce RTX 4060 Ti and bounded by its 28 logical cores and 64GB . Boxes span from the 50th percentile to the maximum with the measurement density inside, lines mark the 95th percentiles, and the box color encodes the relative pose error (RPE) as a multiple of the lowest one on a logarithmic scale. The RPE in the labels is the geometric mean of its translational and rotational parts. Pelorus achieves the lowest relative error with a small, bounded memory footprint. Only RKO-LIO uses less memory, but at a higher RPE and CPU load. With CUDA, Pelorus has the lowest CPU load.
Dataset
Metric
Pelorus
FAST-LIO2 [ 6 ]
Eq-LIO [ 13 ]
Faster-LIO [ 9 ]
RKO-LIO [ 36 ]
EllipseLIO [ 37 ]
DLIO [ 10 ]
iG-LIO [ 19 ]
KISS-ICP [ 38 ]
Newer College [ 29 ]
RPE T
0.0255
0.0373
0.0735
0.0310
0.0496
0.0498
0.0529
0.0276
0.2468
park_merged:os0_128
RPE R
0.2821
0.4795
0.5227
0.4815
0.4281
0.4762
1.3187
0.2913
0.8397
2.4km
APE T
0.2925
0.2655
11.4013
0.2134
1.4669
0.2970
0.2749
0.1973
0.7702
APE R
0.6632
0.6196
5.8040
0.5851
1.0732
0.6357
1.3189
0.4782
1.0919
HeLiPR [ 30 ]
RPE T
0.0648
0.0611
d.n.f.
0.0628
0.0907
d.n.f.
0.0865
0.2487
0.1302
bridge02:ouster
RPE R
0.0568
0.0536
d.n.f.
0.0437
0.0582
d.n.f.
0.0826
0.1230
0.0689
TABLE I: Accuracy Across LIO Systems
Method
Scans
Latency
Proc.
Power
E ⋅ RPE
(%)
p95 (ms)
p95 (ms)
(W)
(mJ m)
Pelorus Vulkan
100.0
192
97.8
13.1
50.3
Pelorus CUDA
99.7
175
83.7
12.4
48.4
Pelorus CUDA + CPU ×4
100.0
173
78.1
12.2
46.8
Pelorus CPU ×4
87.6
3105
220.3
12.0
50.7
Pelorus CPU ×8
93.1
2616
173.2
12.4
49.9
TABLE II: Timings, Power, and Energy Efficiency on the Jetson Orin NX
Fig. 2: Resource footprints on an NVIDIA Jetson Orin NX running helipr/town02:ouster in real time, with the axes bounded by its eight CPU cores and 16GB . With CUDA, Pelorus handles the high-bandwidth OS2 lidar at sensor rate, and both builds hold the desktop accuracy with a fraction of the resources of the other methods. FAST-LIO2, Faster-LIO, and KISS-ICP drop too many scans and lose track, and EllipseLIO and Eq-LIO crash on the board, so they are not shown. Table II lists all methods.
Fig. 3: Capacity sweep on helipr/town02:ouster with the CPU build. Translational and rotational APE and RPE over the peak resident memory for map capacities ∣M∣ from 32k to 512k distributions (k = 1024), each relative to the smallest capacity. The capacity used is marked in bold.
APE T (m)
RPE T
∣M∣
Eviction
NC
OQ02
CC02
town02
( % )
16384
LRU
5.36
0.728
0.411
16.0
T/P
2.15
0.759
0.226
18.2
+2
32768
LRU
1.88
0.404
0.187
9.16
T/P
1.32
0.181
0.132
9.75
+1
65536
LRU
2.10
0.365
0.217
6.01
TABLE III: Eviction Ablation with Reduced Map Capacity
APE T (m) and change ( % )
Mean ( % )
Update
NC
OQ02
CC02
APE T
RPE T
Count-weighted
0.309
0.224
0.125
0
0
κ=5
0.308 (+0)
0.123 ( − 45)
0.101 ( − 19)
− 22
+5
κ=10
0.292 ( − 5)
0.097 ( − 57)
0.089 ( − 29)
− 30
+5
κ=20
0.317 (+3)
0.120 ( − 46)
0.102 ( − 19)
− 21
+7
κ=40
0.298 ( − 3)
0.145 ( − 35)
0.109 ( − 13)
− 17
+10
TABLE IV: Map Update Ablation
RPE T (m)
Map
NC
OQ02
CC02
town02
Multiresolution
0.0255
0.0073
0.0071
0.0391
Single 0.3m
0.0261
0.0077
0.0087
0.0404
Single 0.5m
0.0284
0.0127
0.0153
0.0438
Single 0.7m
0.0330
0.0211
0.0383
0.0492
TABLE V: Multiresolution Ablation with Equal Total Capacity