-
Notifications
You must be signed in to change notification settings - Fork 24
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
What happened to the "skeleton" part of the bodyPose
?
#85
Comments
I'm looking at the @tfjs-model now and I'm not seeing any equivalent to the
|
Ah yes, I think we decided not to include this since it wasn't part of what the native model anymore. I can see how it could be nice to bring back! From my own experience, I very rarely had students use the skeleton connections, the actual points are almost always what they focused on. @MOQN I know you taught quite a bit with PoseNet, what do you think? Is it worth the extra effort and maintenance required to add this data into the model output? @ziyuan-linn also, if you recall anything different from our conversations, let us know! |
Yes, I also remember that we decided to not include it. If I recall correctly we were also planning on making an example p5 sketch that draws the skeleton connections manually. |
I agree with the approach! Since many students tend to visualize the skeleton using their own aesthetics, providing an example of manually drawing individual skeletal parts could be helpful for our students. |
I was looking at the migrating one of the examples that I wrote for the old
poseNet
model (ml5 #1386) and I realized that the newbodyPose
model does not return theskeleton
data -- telling us which pairs of keypoints should be connected. Should we add this in somehow? Do we get this data from the TensorFlow model?We were previously getting these pairs from from a
getAdjacentKeyPoints
function on the TensorFlowposenet
model.https://github.com/ml5js/ml5-library/blob/f80f95aa6b31191ab7e79ff466e8506f5e48a172/src/PoseNet/index.js#L120
JSON from the old ml5 version:
JSON from the new ml5 version:
The text was updated successfully, but these errors were encountered: