HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
manankharwar
fusioncore
C++2026–2026
manankharwar / fusioncore

fusioncore

ROS 2 localization for outdoor robots: IMU, wheel encoders and GPS fused in a 23-state UKF at 100 Hz. When the estimate goes wrong it reports which sensor and why, instead of drifting silently. Apache 2.0.

2Distinct people
5Mentions
0Explicit recommenders
384GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

ROS 2 localization for outdoor robots: IMU, wheel encoders and GPS fused in a 23-state UKF at 100 Hz. When the estimate goes wrong it reports which sensor and why, instead of drifting silently. Apache 2.0.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day5 dated mentions

Observed mentions: 2026-04-12 02:04:10 UTC to 2026-04-30 22:36:06 UTC.

012026-04-12 00:00:00 UTC to 2026-04-13 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsApr 122026-04-13 00:00:00 UTC to 2026-04-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-14 00:00:00 UTC to 2026-04-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-15 00:00:00 UTC to 2026-04-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-16 00:00:00 UTC to 2026-04-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-17 00:00:00 UTC to 2026-04-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-18 00:00:00 UTC to 2026-04-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-19 00:00:00 UTC to 2026-04-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-20 00:00:00 UTC to 2026-04-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-21 00:00:00 UTC to 2026-04-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 212026-04-22 00:00:00 UTC to 2026-04-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-23 00:00:00 UTC to 2026-04-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-24 00:00:00 UTC to 2026-04-25 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-04-25 00:00:00 UTC to 2026-04-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-26 00:00:00 UTC to 2026-04-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-27 00:00:00 UTC to 2026-04-28 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-04-28 00:00:00 UTC to 2026-04-29 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-04-29 00:00:00 UTC to 2026-04-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-30 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsApr 30

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 122026-04-12 00:00:00 UTC2026-04-13 00:00:00 UTC110
Apr 132026-04-13 00:00:00 UTC2026-04-14 00:00:00 UTC000
Apr 142026-04-14 00:00:00 UTC2026-04-15 00:00:00 UTC000
Apr 152026-04-15 00:00:00 UTC2026-04-16 00:00:00 UTC000
Apr 162026-04-16 00:00:00 UTC2026-04-17 00:00:00 UTC000
Apr 172026-04-17 00:00:00 UTC2026-04-18 00:00:00 UTC000
Apr 182026-04-18 00:00:00 UTC2026-04-19 00:00:00 UTC000
Apr 192026-04-19 00:00:00 UTC2026-04-20 00:00:00 UTC000
Apr 202026-04-20 00:00:00 UTC2026-04-21 00:00:00 UTC000
Apr 212026-04-21 00:00:00 UTC2026-04-22 00:00:00 UTC000
Apr 222026-04-22 00:00:00 UTC2026-04-23 00:00:00 UTC000
Apr 232026-04-23 00:00:00 UTC2026-04-24 00:00:00 UTC000
Apr 242026-04-24 00:00:00 UTC2026-04-25 00:00:00 UTC110
Apr 252026-04-25 00:00:00 UTC2026-04-26 00:00:00 UTC000
Apr 262026-04-26 00:00:00 UTC2026-04-27 00:00:00 UTC000
Apr 272026-04-27 00:00:00 UTC2026-04-28 00:00:00 UTC110
Apr 282026-04-28 00:00:00 UTC2026-04-29 00:00:00 UTC110
Apr 292026-04-29 00:00:00 UTC2026-04-30 00:00:00 UTC000
Apr 302026-04-30 00:00:00 UTC2026-05-01 00:00:00 UTC110

What Hacker News says

5 sources
kharwarm·Apr 28, 2026Submission

Show HN: FusionCore: ROS 2 sensor fusion that outperforms robot_localization

I built sensor fusion for a mobile robot and reached for robot_localization like everyone does. After spending too long fighting navsat_transform, UTM zone boundaries, and YAML covariance tuning, I wrote my own. FusionCore is a 22 state UKF that fuses IMU, wheel encoders, and GPS in ECEF directly (no coordinate projection, no extra node). It estimates IMU bias, adapts its noise covariance automatically from the innovation sequence, and gates outliers with a chi squared test on every sensor. I benchmarked it against robot_localization EKF on 6 sequences from the NCLT public dataset (University of Michigan, real robot, real GPS, RTK ground truth). It wins 5 of 6. On the 6th sequence (fall, degraded GPS over a long period) it loses badly. RL UKF diverged to NaN on all six. Configs, methodology, and full reproduce instructions are in the benc
Read the rest
hmarks/ folder.
11 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.