Browse State-of-the-Art › Radar odometry
Radar odometry
5 papers with code · 1 benchmark · 3 datasets archive 2025-07-28
Radar odometry is the task of estimating the trajectory of the radar sensor, e.g. as presented in https://arxiv.org/abs/2105.01457. A well established performance metric was presented by Geiger (2012) - "Are we ready for autonomous driving? the KITTI vision benchmark suite"
Description from the archive archive 2025-07-28.
Benchmarks archive 2025-07-28
1 leaderboard table shown for this task, 1 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted.
| Dataset | Best model (first row in archive order) | Paper | Code | Syntology | Compare |
|---|---|---|---|---|---|
| Oxford Radar RobotCar Dataset (1 row) | CFEAR-3-s4 | CFEAR Radarodometry - Conservative Filtering for Efficient and... | code | — | Compare |
Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.
Libraries
Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.
Datasets archive 2025-07-28
3 datasets whose archive record lists this task, ordered by the archive's paper count.
Subtasks archive 2025-07-28
No subtask under this task in the archive's task tree.
Papers archive 2025-07-28
archive papers tagged: 9 · with a code link: 5 · where Syntology ran a sample: 0 (0 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran: none of the 9 tagged papers has a Syntology run on record
Page 1 of 1: papers 1 to 9 of 9, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.
Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from.
-
16 Sep 2021 2 repositories listedThis paper presents the accurate, highly efficient, and learning-free method CFEAR Radarodometry for large-scale radar odometry estimation.
-
29 Jan 2020 2 repositories listedThis paper presents a self-supervised framework for learning to detect robust keypoints for odometry estimation and metric localisation in radar.
-
29 Apr 2025 1 repository listedWhen using data with the appropriate Doppler-enabling frequency modulation pattern, the translation error is reduced to 0.
-
30 Jul 2023 1 repository listedSimulation results demonstrate that the proposed SPEBT scheme is capable of providing precise pose estimation information and accurate beam tracking output, while reducing the proportion of beam training overhead to…
-
2 Mar 2020 1 repository listedOur experimental results, on traversals of the Oxford RobotCar dataset with no GPS data, show that MVP can achieve 53% and 93% navigation success rate using VO and RO, respectively, compared to 7% for a vision-only…
-
DNOI-4DRO: Deep 4D Radar Odometry with Differentiable Neural-Optimization Iterations18 May 2025 0 repositories listedA novel learning-optimization-combined 4D radar odometry model, named DNOI-4DRO, is proposed in this paper.
-
RadarLCD: Learnable Radar-based Loop Closure Detection Pipeline13 Sep 2023 0 repositories listedLoop Closure Detection (LCD) is an essential task in robotics and computer vision, serving as a fundamental component for various applications across diverse domains.
-
MIMO-SAR: A Hierarchical High-resolution Imaging Algorithm for mmWave FMCW Radar in Autonomous Driving22 Jan 2021 0 repositories listedMillimeter-wave radars are being increasingly integrated into commercial vehicles to support advanced driver-assistance system features.
-
Masking by Moving: Learning Distraction-Free Radar Odometry from Pose Information9 Sep 2019 0 repositories listedThis paper presents an end-to-end radar odometry system which delivers robust, real-time pose estimates based on a learned embedding space free of sensing artefacts and distractor objects.
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