kalibr icon indicating copy to clipboard operation
kalibr copied to clipboard

AttributeError: 'AslamCamera object has no attribute 'geometry'

Open Enes1097 opened this issue 2 years ago • 4 comments

Thanks for providing this package, it seems to be very useful-

I was just trying out the Camera-IMU Calibration with a Rolling-Shutter Camera and an IMU, but encountered some problems. I read through a few issues already talking about calibrating a rolling-shutter camera with an imu instead of a global shutter camera and realized that it's harder to do than it seems. I also tried to implement every hint mentioned in these issues (f.e. minimum exposure time, high fps, slow movements), but it still didn't work.

This is what my system puts out after the starting the calibration: Kalibr_error1

I suspect that the Corner Detection of the Aprilgrid doesn't work with the images my camera puts out, that's why I attached an example picture from the rosbag here: 1629499935611201156

P.S.: The Camera I'm using is an Azure Kinect DK Camera which makes use of a rational-polynomial distortion model. This model is not supported by kalibr which is why I was using the famous image-proc package to undistorted it and then fill the rosbag with the monochrome undistorted image (/rgb/image_mono) which the image_proc puts out.

If anyone could help me, I would really appreciate it.

Enes1097 avatar Aug 24 '21 14:08 Enes1097

Hi,

Have you tried calibrating your camera-IMU system, using the global shutter process? Although it is not perfect, it must give you acceptable results.

I faced the error you encountered quite a while ago, but the problem was that some of the images were not recorded successfully, which does not seem to be your case.

Regards

mhyoosefian avatar Oct 19 '21 13:10 mhyoosefian

Hi,

Have you tried calibrating your camera-IMU system, using the global shutter process? Although it is not perfect, it must give you acceptable results.

I faced the error you encountered quite a while ago, but the problem was that some of the images were not recorded successfully, which does not seem to be your case.

Regards

Hey,

The only camera that I was able to use in that period of time was the Azure Kinect DK camera, which has a rolling-shutter sensor. That way I couldn't make use of the global shutter process, as you pointed out.

By using this package https://github.com/JzHuai0108/kalibr, a Kalibr ROS-Package for RS-cameras, I did not get this error message and the calculation succeeded.

Cheers

Enes1097 avatar Dec 13 '21 14:12 Enes1097

Hi, Have you tried calibrating your camera-IMU system, using the global shutter process? Although it is not perfect, it must give you acceptable results. I faced the error you encountered quite a while ago, but the problem was that some of the images were not recorded successfully, which does not seem to be your case. Regards

Hey,

The only camera that I was able to use in that period of time was the Azure Kinect DK camera, which has a rolling-shutter sensor. That way I couldn't make use of the global shutter process, as you pointed out.

By using this package https://github.com/JzHuai0108/kalibr, a Kalibr ROS-Package for RS-cameras, I did not get this error message and the calculation succeeded.

Cheers

Glad to hear that you successfully ran the Kalibr. I have done the calibration using the global-shutter scheme, even though my camera was a rolling-shutter. However, it worked properly.

mhyoosefian avatar Dec 13 '21 15:12 mhyoosefian

I also ran into this issue, which happens when you try to use distortion_model: none (in my case I'm trying to run it on already undistorted images), so for anyone else having this issue, the fix is to simply go to aslam_offline_calibration/kalibr/python/kalibr_common/ConfigReader.py and change the one instance of self.camera to self.geometry.

jacobly0 avatar Mar 12 '22 00:03 jacobly0