Skip to content
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

Open
zhangzscn opened this issue Sep 6, 2024 · 1 comment
Open

Bad result in Aeve AeriesII Lidar #74

zhangzscn opened this issue Sep 6, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@zhangzscn
Copy link

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",

@zhangzscn zhangzscn added the bug Something isn't working label Sep 6, 2024
@koide3
Copy link
Owner

koide3 commented Sep 21, 2024

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.

[2024-09-22 07:54:15.319] [odom] [warning] t_last=1568806761.555775 t_current=1568806761.655773 num_imu=1
[2024-09-22 07:54:15.325] [submap] [warning] insufficient IMU data between LiDAR frames!! (sub_mapping)
[2024-09-22 07:54:15.368] [odom] [warning] insufficient number of IMU data between LiDAR scans!! (odometry_estimation)
[2024-09-22 07:54:15.368] [odom] [warning] t_last=1568806761.855804 t_current=1568806761.955818 num_imu=1
[2024-09-22 07:54:15.387] [submap] [warning] insufficient IMU data between LiDAR frames!! (sub_mapping)
[2024-09-22 07:54:15.398] [submap] [warning] insufficient IMU data between LiDAR frames!! (sub_mapping)
[2024-09-22 07:54:15.418] [submap] [warning] insufficient IMU data between LiDAR frames!! (sub_mapping)                              
[2024-09-22 07:54:15.460] [odom] [warning] insufficient number of IMU data between LiDAR scans!! (odometry_estimation)
[2024-09-22 07:54:15.460] [odom] [warning] t_last=1568806762.455785 t_current=1568806762.555799 num_imu=1
[2024-09-22 07:54:15.463] [submap] [warning] insufficient IMU data between LiDAR frames!! (sub_mapping)
[2024-09-22 07:54:15.476] [odom] [warning] insufficient number of IMU data between LiDAR scans!! (odometry_estimation)
[2024-09-22 07:54:15.476] [odom] [warning] t_last=1568806762.555799 t_current=1568806762.655793 num_imu=1
[2024-09-22 07:54:15.484] [submap] [warning] insufficient IMU data between LiDAR frames!! (sub_mapping)
[2024-09-22 07:54:15.491] [glim] [warning] large time gap between consecutive IMU data!!
[2024-09-22 07:54:15.491] [glim] [warning] current=1568806762.941422 last=1568806762.831433 diff=0.109989             
[2024-09-22 07:54:15.495] [submap] [warning] insufficient IMU data between LiDAR frames!! (sub_mapping)  
[2024-09-22 07:54:15.515] [submap] [warning] insufficient IMU data between LiDAR frames!! (sub_mapping)
[2024-09-22 07:54:15.522] [odom] [warning] insufficient number of IMU data between LiDAR scans!! (odometry_estimation)                                      
[2024-09-22 07:54:15.522] [odom] [warning] t_last=1568806762.855791 t_current=1568806762.955785 num_imu=1
[2024-09-22 07:54:15.526] [submap] [warning] insufficient IMU data between LiDAR frames!! (sub_mapping)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants