You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context: I have been using the rectify node to to undistort images and save them in a bag along with the TF and the camera info of the source image. For space considerations, the original image is not stored in the bag. Later, I have an offline process that read the bag and needs to back project 3D points to the rectified images (to add colour to a point cloud).
I initially assumed that I could use the initial camera info, with zero distortion, but this led to very inaccurate reprojections. I ultimately found that my reprojection was correct if I used the intrinsics computed by getOptimalNewCameraMatrix, with alpha = 0. The fact that there is this free parameter alpha, which is not explicitly mentioned in the rectify node, would justify publishing a rectified CameraInfo in my opinion.
Context: I have been using the rectify node to to undistort images and save them in a bag along with the TF and the camera info of the source image. For space considerations, the original image is not stored in the bag. Later, I have an offline process that read the bag and needs to back project 3D points to the rectified images (to add colour to a point cloud).
I initially assumed that I could use the initial camera info, with zero distortion, but this led to very inaccurate reprojections. I ultimately found that my reprojection was correct if I used the intrinsics computed by getOptimalNewCameraMatrix, with alpha = 0. The fact that there is this free parameter alpha, which is not explicitly mentioned in the rectify node, would justify publishing a rectified CameraInfo in my opinion.
I can implement it if this is deemed relevant but I only have access to a machine running humble right now.
The text was updated successfully, but these errors were encountered: