fix masking issue in interpolate#161
Merged
AmitMY merged 2 commits intosign-language-processing:masterfrom Mar 22, 2025
Merged
Conversation
Collaborator
|
J22Melody
commented
Mar 17, 2025
AmitMY
requested changes
Mar 17, 2025
Contributor
Author
|
ready for review and merge |
AmitMY
approved these changes
Mar 22, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have found this strange bug: when the x, y, z, and confidence are all 0s for a point in a pose (everything should be masked), but the current implementation on line 342 would not consider it masked when reading the first dimension (the x is 0).
I did not have this issue before, so I assume the pose data should always have masked x, y, and z values when the confidence is 0, @AmitMY is it what we should expect for a "normal" pose?