You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
StephanHasler
changed the title
Wrong name body tracking 34 joint (naval->navel)
Wrong name of body tracking 34 joint (naval->navel)
Feb 24, 2025
Preliminary Checks
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
The text was updated successfully, but these errors were encountered: