Facemap Pose Estimation Inference #24
Conversation
sidhulyalkar
commented
Sep 21, 2023
sidhulyalkar
commented
- Add facial_pose_model.py. Contains new facemap_model_schema with classes BodyPart, FacemapModel, FacemapPoseEstimationTask, and FacemapPoseEstimation.
- Explanatory Jupyter notebook not included for now. (Using LuLab data, and local testing pipeline). Includes functions ingest_model, and generate_pose_estimation_task, which insert into the FacemapModel, FacemapPoseEstimationTask, and fbe.VideoRecording tables.
…map pose inference
Co-authored-by: Thinh Nguyen <[email protected]>
Co-authored-by: Thinh Nguyen <[email protected]>
…hulyalkar/element-facemap into new_facemap_integration_test
…nk to facemap model table --> make into a secondary attr
…efault model is intially inserted
There was a problem hiding this comment.
Just a small consideration before merging. @ttngu207, do you agree that the table should be renamed here? Facemap's documentation uses keypoints and body parts interchangeably in their tutorials.
|
|
||
| # ----------------------------- Table declarations ---------------------- | ||
| @schema | ||
| class BodyPart(dj.Lookup): |
There was a problem hiding this comment.
Is this table better identified as KeyPoints?
There was a problem hiding this comment.
I agree but then I believe Facemap itself still refers to those as bodyparts, right?
The results are orofacial features, calling it body parts seems wrong. But if this is the terminology used in facemap, we should stick to the same term.
There was a problem hiding this comment.
Yes agreed, Facemap incorrectly uses the term 'BodyParts' to define their keypoints, but we should stick with their convention.
| model_description='' : varchar(1000) # optional model description | ||
| """ | ||
|
|
||
| class BodyPart(dj.Part): |
There was a problem hiding this comment.
This table could also be renamed KeyPoints if the Lookup table above is renamed
|
|
||
| # ----------------------------- Table declarations ---------------------- | ||
| @schema | ||
| class BodyPart(dj.Lookup): |
There was a problem hiding this comment.
I agree but then I believe Facemap itself still refers to those as bodyparts, right?
The results are orofacial features, calling it body parts seems wrong. But if this is the terminology used in facemap, we should stick to the same term.
