-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bad result in Aeve AeriesII Lidar #74
Labels
bug
Something isn't working
Comments
It seems there are many drops of IMU and LiDAR data frames. This is a common issue related to bag recording in ROS2. Please try using components to run the sensor driver and the bag recorder in a single node manager to improve the recording performance.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the laboratory, we tested glim algorithm with Aeve AeriesII Lidar. In the first small part of data, glim performed well, but in the subsequent data, attitude estimation was not very accurate. Could you please help analyze the specific reasons? And is there a solution?
data:https://drive.google.com/file/d/1j65q7E8nM8g4Mfd6lIXmfC-C6A--E7Gb/view?usp=sharing
For Aeve AeriesII LiDAR, we have modified some configurations:
"T_lidar_imu": [
0,
0,
0,
0.0,
0.0,
0.0,
1.0
].
"imu_topic": "/aeva/aeva/imu",
"points_topic": "/aeva/aeva/point_cloud_compensated",
The text was updated successfully, but these errors were encountered: