Heethesh Vhavle

- What was the total number of correspondences you used for calibration? - Place the calibration target in multiple positions such that the target covers all regions and extremes of...

@Bsting118 > How would you check to make sure the image is not rectified twice? After you have performed your camera calibration, ROS will auto save this data in `~/.ros/your_camera.yaml`...

Since you manually pick 3D/2D correspondences here, you can re-project the picked 3D points to the image after you have the extrinsics estimate and compute the pixel error with the...

See my comment [here](https://github.com/heethesh/lidar_camera_calibration/issues/22#issuecomment-715589902)

If the number of points in your point cloud is too large, it might be a performance issue as Matplotlib does not handle this well. For this reason, I have...

There is no `world` frame during the calibration. You are estimating the camera -> velodyne transformation. The `world` frame is just a dummy base frame used to transform the point...

Yes it should work, you can still launch the GUI and pick (and save) corresponding 2D/3D points. Make sure the camera is calibrated and `camera_info` topic is updated properly with...

Yes, if you save it in `/home/.ros` folder (not sure) - which is the default save path, I believe ROS will automatically pick the data from here for a given...

No problem, you may want to update the point-cloud visible ranges for the GUI [here](https://github.com/heethesh/lidar_camera_calibration/blob/master/scripts/calibrate_camera_lidar.py#L232). Working on a new update that uses Rviz GUI instead of Matplotlib which should be...

yes it should work