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

disparity transform using python wrapper #1778

Closed
ghost opened this issue May 26, 2018 · 6 comments
Closed

disparity transform using python wrapper #1778

ghost opened this issue May 26, 2018 · 6 comments
Assignees

Comments

@ghost
Copy link

ghost commented May 26, 2018

Required Info
Camera Model D400
Firmware Version 05.09.11.00
Operating System & Version Win10
Platform PC
SDK Version 2.11.1

i am trying to use disparity transform with python according to c++ API, but without success
How can I use this filter?
self.disparity = rs.disparity_transform(True)
self.disparity.update_transformation_profile(filtered)

@lramati
Copy link
Contributor

lramati commented May 28, 2018

Like in the C++ API, you create the filter with disparity = pyrealsense2.disparity_transform().
The frames are then processed via new_frame = disparity.process(old_frame)

@ghost
Copy link
Author

ghost commented May 28, 2018

thanks, what is the meaning of those depth values after using this method?
image

@dorodnic
Copy link
Contributor

Usually this block is used before spatial and temporal filters and the "rolled-back" using another disparity transform with rs.disparity_transform(False).
If you want to use these values directly, you should cast data to float, and interpret the results as displacement of every pixel between left and right views, in pixels.

@RealSense-Customer-Engineering
Copy link
Collaborator

[Realsense Customer Engineering Team Comment]
Hi @iramati,

Is above answer resolve your issue?

@RealSense-Customer-Engineering
Copy link
Collaborator

[Realsense Customer Engineering Team Comment]
Hi @adarvit,

Does above answer resolve your issue?

@ghost
Copy link
Author

ghost commented Jun 20, 2018

yes, thank you

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

No branches or pull requests

3 participants