Skip to content

Commit 921dd41

Browse files
docs: add next-steps section for state estimation after IMU filtering (#232)
Refs #231 (suggested and approved by maintainer mintar) Co-authored-by: Manan Kharwar <manan.kharwar@ansys.com>
1 parent da75cec commit 921dd41

1 file changed

Lines changed: 20 additions & 0 deletions

File tree

README.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -72,6 +72,26 @@ All nodes, topics and parameters are documented on [this repo's ROS wiki
7272
page](https://wiki.ros.org/imu_tools).
7373

7474

75+
What's next after filtering your IMU?
76+
--------------------------------------
77+
78+
Once you have a filtered orientation from `imu_filter_madgwick` or
79+
`imu_complementary_filter`, a common next step is fusing it with wheel odometry
80+
(and optionally GPS) to produce a full `odom -> base_link` state estimate. Two
81+
ROS 2 packages that do this:
82+
83+
* **[robot_localization](https://github.com/cra-ros-pkg/robot_localization)**:
84+
well-established EKF/UKF state estimator, widely used across the ROS ecosystem.
85+
86+
* **[FusionCore](https://github.com/manankharwar/fusioncore)**:
87+
UKF with online gyro bias estimation (yaw drift compounds slower over long
88+
runs), native GPS fusion for outdoor robots, and a numerically stable filter
89+
that handles aggressive maneuvers without diverging. Available on apt for
90+
Jazzy and Humble (`ros-jazzy-fusioncore`).
91+
92+
Both take a filtered IMU topic as input.
93+
94+
7595
pre-commit formatting checks
7696
----------------------------
7797

0 commit comments

Comments
 (0)