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

Zero values in Kinect original z-image end up in non-zero values #204

Open
mischastik opened this issue Aug 22, 2019 · 3 comments
Open

Zero values in Kinect original z-image end up in non-zero values #204

mischastik opened this issue Aug 22, 2019 · 3 comments

Comments

@mischastik
Copy link
Contributor

Very likely a numeric problem.
This can lead to zero-checks missing invalid distance pixels.
Potential solution: Check for very small distances (e. g. <10-4) and set them to zero.

@sisiplac
Copy link
Contributor

sisiplac commented Sep 3, 2019

Is this issue related to Kinect V2 or Kinect4Azure?

@jangernert
Copy link
Collaborator

As far as I remember and understood from listening in on Micheals conversation it was Kinectv2

@sisiplac
Copy link
Contributor

sisiplac commented Mar 3, 2020

I'm pretty sure that this issue is not related to MetriCam2. I guess that the distance image has been processed with a spatial filter causing the close-to-zero data.
@mischastik
Can we close this issue?

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

3 participants