Memory coruption when running lsd_slam_core

[boonflies]

Memory coruption when running lsd_slam_core

[kungfrank]

Hello @boonflies,
Memory corruption error in lsd_slam cause by input image resolution isn't multiple-of-16. That why we modified ardrone output image resolution to 640x352(see video.h in ardrone_autonomy, you should replace the same file in your ardrone_autonomy package with it ). But at the same time, don't forget to modify parameter of resolution in camera calibration file too(that is similar to ardrone_front.yaml, which is ardrone's default camera calibration file).

[haochihlin]

Hi @boonflies
It is great to know you have solved the issue!
About the resolution, well, based on my experience, there is no performance difference.
The only thing you need to take care is to do the camera calibration after modifying the image size!

[haochihlin]

@kungfrank
I think you could answer this ~

[boonflies]

Thanks.
When I used the raw image and made the camera configuration file as,
640 360
Crop
640 320
the error got resolved.

Does it make a difference in slam, to set the image size to 640x320 rather than 640x352 which is the drone's output image resolution?

[axelfar]

Hi @boonflies,
I have a quesiton about your camera calibration.
Do you have a good result with lsd_slam and your calibration file?
For me the resulting pointcloud is really bad.
I try to calibrate my drone with 'camera_calibration' it's better but i have a flat pointcloud.

[boonflies]

I did not properly calibrate the camera, but I just got some calibration file from net. I am using this calibration file,
0.50355332 0.894045767 0.494061013 0.509863 -0.466013 0.176685 0.032364 -0.010129 0.000000
640 360
crop
400 288

I have not visualized the point cloud in RViz yet. I can only see it in lsd_slam's point cloud viewer.

Is it right, that we get point cloud when we press 'l' followed by 'p' on the lsd_slam's pointcloud viewer and a tmp.ply file is generated. How is the point cloud topic published and visualized in RViz?