KumarRobotics / kr_autonomous_flight

KR (KumarRobotics) autonomous flight system for GPS-denied quadrotors
Other
654 stars 110 forks source link

Reliable integration of LIDAR odometry into autonomy stack #146

Closed XuRobotics closed 1 year ago

XuRobotics commented 2 years ago

We have tried the integration of LIDAR odometry into UKF, using LLOL. We successfully flew waypoint missions, using LIDAR only for both odometry and mapping (i.e. no cameras were needed for the autonomous flight).

However, this is still in an early stage and we have not done large-scale tests. It would be good to test and compare the odometry performance with different combinations of sensors, including (1) stereo-VIO-only (2) LIDAR-odom-only (3) stereo-VIO + LIDAR-odom. Also it would be good to idenfy degenerative cases for different combinations.

The interfaces to support different sensors are all available in the UKF package included in this repo.

Should test this extensively on the large-scale forest datasets we've collected, which can be challenging for LIDAR-odom.

versatran01 commented 2 years ago

This requires a thorough review of the ukf code, potentially some refactors.

nvhungv2k commented 1 week ago

@XuRobotics You said "We successfully flew waypoint missions, using LIDAR only for both odometry and mapping (i.e. no cameras were needed for the autonomous flight)". Doing it again, following the instruction here, isn't it? If TRUE, I followed it as:

XuRobotics commented 1 week ago

Make sure you follow instructions here: https://github.com/KumarRobotics/kr_autonomous_flight/wiki/Gazebo-Simulation-Setup

Specifically, make sure ouster ros repo is on the simulator branch

Also you’re using the wrong launch file, it should be full_sim.launch as specified by the link above

Another additional change you can try, if you still have problems with the stimulator experiments, is to reduce map resolution (increase the voxel size in the corresponding mapper.yaml file), and make sure you did build the code in release mode, to avoid any computation related problems.

XuRobotics commented 1 week ago

PS: FYI, I pasted the relevant command in the exteral_all.yaml that allows you to use the simulator branch of ouster ros

ouster_example: type: git url: http://github.com/XuRobotics/ouster_example.git version: os-sim

nvhungv2k commented 1 week ago

PS: FYI, I pasted the relevant command in the exteral_all.yaml that allows you to use the simulator branch of ouster ros

ouster_example: type: git url: http://github.com/XuRobotics/ouster_example.git version: os-sim

I just check ouster_example as you said, it already was in os-sim branch: image

XuRobotics commented 1 week ago

By the way, we never did experiments with lidar odom in simulation, we have been using our robot with Ouster OS1-64 lidar to do these experiments directly

nvhungv2k commented 1 week ago

By the way, we never did experiments with lidar odom in simulation, we have been using our robot with Ouster OS1-64 lidar to do these experiments directly

I had been trying it in simulation. I have new issue #193 @XuRobotics pls view. Thanks

nvhungv2k commented 1 week ago

However, this is still in an early stage and we have not done large-scale tests. It would be good to test and compare the odometry performance with different combinations of sensors, including (1) stereo-VIO-only (2) LIDAR-odom-only (3) stereo-VIO + LIDAR-odom. Also it would be good to idenfy degenerative cases for different combinations.

@XuRobotics I have been doing different combinations of sensors as you said. But I am in stage of running them in gazebo simulation. So what factors do you use to compare them? Can you share it or refer to any paper related to? THANKS!