Open TakuOkawara opened 6 months ago
Unfortunately, the current version code does not support Livox.
Can you write in more detail? Are there any hardware limitations for example livox mid 360 lidar for use with LIW-OAM without ROS (directly using with SDK\driver livox)?
@ZikangYuan Thank you for your reply. I understand that the current version of this package does not support Livox AVIA.
Are the following changes enough to use Livox AVIA for liw_oam?
We can execute liw_oam with Livox AVIA by converting the livox custom message (livox_ros_driver::CustomMsg) into sensor_msgs::PointCloud2 message, and the estimation result is good even in an environment where point clouds degenerate. However, we are concerned about the validity of the result obtained by modifying liw_oam based on the above changes of setting. Could you answer our question?
@TakuOkawara Did you manage to launch LIW-OAM with the Livox AVIA lidar?
@TakuOkawara Did you manage to launch LIW-OAM with the Livox AVIA lidar?
Yes, we were able to launch LIW-OAM with the Livox AVIA lidar and wheel odometry. But as I said in the previous reply, we are not sure about the validity of the result.
Thank you for sharing your great project with us. We were able to run this package with the bag file obtained from your Google Drive.
We ask you whether this package supports for Livox LiDARs because we plan to cite your paper.
As seen in some codes such as kaist.yaml and lioOptimization.cpp, this package seems to support Livox LiDARs. kaist.yaml
lioOptimization.cpp
However, cloudProcessing.cpp shows that other than Velodyne LiDARs cannot be used currently such as the following image. cloudProcessing.cpp
Therefore, we are confused about whether we can use Livox LiDAR for this package.
If this package does not support Livox LiDAR (especially, Livox AVIA), can we use this package by Livox AVIA with some adjustments to the settings made for Velodyne?