Skip to content

Wrong name of body tracking 34 joint (naval->navel) #244

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

Open
2 tasks done
StephanHasler opened this issue Feb 24, 2025 · 0 comments
Open
2 tasks done

Wrong name of body tracking 34 joint (naval->navel) #244

StephanHasler opened this issue Feb 24, 2025 · 0 comments

Comments

@StephanHasler
Copy link

Preliminary Checks

  • This issue is not a duplicate. Before opening a new issue, please search existing issues.
  • This issue is not a question, bug report, or anything other than a feature request directly related to this project.

Proposal

I think the joint BODY_34_PARTS.NAVAL_SPINE should be named NAVEL_SPINE.
I stumbled about this when switching from an Azure Kinect to the ZED camera. Both provide a very similar body tracking model. Only that for the Azure the joint is called NAVEL_SPINE while the ZED calls it NAVAL_SPINE.
This makes it hard for me to write camera-agnostic downstream code.

Use-Case

No response

Anything else?

No response

@StephanHasler StephanHasler changed the title Wrong name body tracking 34 joint (naval->navel) Wrong name of body tracking 34 joint (naval->navel) Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant