FusionCore as a natural next step after imu_filter_madgwick?

[manankharwar]

hey,

I made FusionCore: a ROS 2 UKF that takes a filtered IMU (like the output of imu_filter_madgwick) and fuses it with wheel odometry and optional GPS to produce a full odom->base_link state estimate. basically the next step in the pipeline after you've filtered your IMU.

it's on apt for Jazzy and Humble (ros-jazzy-fusioncore-ros).

a lot of people using imu_tools are asking 'okay I have a filtered IMU, now what?': would you be open to adding a small pointer to FusionCore in the README or wiki as a suggested next step? even a one-liner would be helpful.

happy to open a PR if yes.

[mintar]

Hi!

I'd welcome any addition to the README that helps users understand the role that this repo plays in the bigger picture of going from raw sensor data to a localization estimate, including answering the question "what's the next step in the pipeline". Of course we should take separation of concerns into account (so the README here shouldn't go too deep into another package), but pointers are welcome. And also we shouldn't be biased towards a single approach, so if we mention FusionCore, we should at least also mention robot_localization as another alternative (since it's more of a default).

Maybe a good place would be after the "More info" section in the README, before the housekeeping stuff.

[manankharwar]

Thanks for the quick response! That makes a lot of sense. Happy to mention robot_localization alongside FusionCore.... it's genuinely the other main option and users should know about both.

I'll open a PR with a short "what's next" section after the More info block. Will keep it brief, just a pointer with a one-liner on each.

[mintar]

Closed via #232