Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarity regarding the computation of Stereo point cloud #96

Open
hangzu-tech opened this issue Jul 17, 2024 · 1 comment
Open

Clarity regarding the computation of Stereo point cloud #96

hangzu-tech opened this issue Jul 17, 2024 · 1 comment

Comments

@hangzu-tech
Copy link

I have a clarification to make as follows:

I am susbcribing to the the topic /multisense/image_points2 - described as Grayscale stereo point cloud. Each point contains 4 fields (x, y, z, lumanince). in the documentation.

  1. So is this stereo point cloud aligned to the left image?
  2. Is the intensity (lumanince) value for each point taken directly from the corresponding pixel in left image?
  3. Can this be changed to align to the right image?

Thanks.

@mattalvarado
Copy link
Contributor

Thanks for reaching out @hangzu-tech

  1. The stereo point cloud published by the ROS driver is the result of a direct conversion between the MultiSense disparity image. The disparity image is computed using the left rectified image as the source. Details on that conversion can be found here https://docs.carnegierobotics.com/docs/cookbook/overview.html#reproject-disparity-images-to-3d-point-clouds .
  2. The luminance for each point is taken directly from the left rectified image pixel corresponding to the points disparity pixel.
  3. There is currently no way to have MultiSense use the right image as the disparity computation source. Could you provide more detail on your application, and why you are looking for disparity computed from the right rectified image?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants