ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2023-05-29 00:33:38 -0500 | received badge | ● Nice Question (source) |
2022-08-27 08:53:53 -0500 | received badge | ● Famous Question (source) |
2021-11-15 02:39:05 -0500 | received badge | ● Notable Question (source) |
2021-07-16 14:51:12 -0500 | received badge | ● Popular Question (source) |
2021-06-25 02:11:36 -0500 | received badge | ● Famous Question (source) |
2021-06-09 04:21:43 -0500 | received badge | ● Famous Question (source) |
2021-05-21 13:16:31 -0500 | received badge | ● Supporter (source) |
2021-05-14 17:10:30 -0500 | received badge | ● Enthusiast |
2021-05-10 07:16:28 -0500 | received badge | ● Notable Question (source) |
2021-05-06 12:35:11 -0500 | commented question | robot_localization: visual odom + imu + gps /odometry/gps is being published at 4Hz pretty consistently until it crashes and then I get: average rate: 1.587 mi |
2021-05-06 07:14:01 -0500 | received badge | ● Popular Question (source) |
2021-05-05 19:06:43 -0500 | asked a question | robot_localization: visual odom + imu + gps robot_localization: visual odom + imu + gps I'm running into some challenges with my robot_localization setup. I have vi |
2021-05-05 15:08:49 -0500 | answered a question | robot_localization: Delay in node startup causes odom drift I was able to solve this by modifying the process_noise_covariance matrix. I changed the default value for az from 0.015 |
2021-05-05 15:08:49 -0500 | received badge | ● Rapid Responder (source) |
2021-05-05 13:35:58 -0500 | asked a question | robot_localization: Delay in node startup causes odom drift robot_localization: Delay in node startup causes odom drift I am using a simple implementation with visual odometry (ZED |
2021-04-13 15:09:48 -0500 | commented answer | Fusing IMU and GPS to the map frame using robot_localization Thank you for the answer. My application is marine, so neither visual nor wheel odometry are reliable. I will be using t |
2021-04-13 15:05:43 -0500 | received badge | ● Notable Question (source) |
2021-04-01 12:54:10 -0500 | received badge | ● Favorite Question (source) |
2021-03-31 08:30:43 -0500 | received badge | ● Popular Question (source) |
2021-03-26 21:51:43 -0500 | asked a question | Fusing IMU and GPS to the map frame using robot_localization Fusing IMU and GPS to the map frame using robot_localization Similar to the question asked here with respect to fusing G |
2021-03-25 06:54:32 -0500 | received badge | ● Student (source) |
2021-03-24 17:26:30 -0500 | edited question | Fusing IMU and GPS to the map frame using robot_localization Fusing IMU and GPS to the map frame using robot_localization Similar to the question asked here with respect to fusing G |
2021-03-24 17:26:30 -0500 | received badge | ● Editor (source) |
2021-03-24 17:26:16 -0500 | edited question | Fusing IMU and GPS to the map frame using robot_localization Fusing IMU and GPS to the map frame using robot_localization Similar to the question asked here with respect to fusing G |
2021-03-24 17:25:11 -0500 | asked a question | Fusing IMU and GPS to the map frame using robot_localization Fusing IMU and GPS to the map frame using robot_localization Similar to the question asked here with respect to fusing G |
2021-03-19 16:10:51 -0500 | commented answer | How to fuse IMU & GPS using robot_localization Hi Tom, The setup that you have captured would require another ekf_localization_node correct? To establish the odom-> |