Skip to content
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

offset & code #32

Open
shangchengPKU opened this issue May 6, 2020 · 3 comments
Open

offset & code #32

shangchengPKU opened this issue May 6, 2020 · 3 comments

Comments

@shangchengPKU
Copy link

Thank you very much for your excellent code, but I would like to ask you a few questions:

  1. What is the purpose of introducing offset?
  2. In the code file, you have center point, boundary box, mean / standard deviation
    What are the specific functions of GT key point documents?
@zhangboshen
Copy link
Owner

@shangchengPKU Hi,

  1. The idea of predicting offset instead of pixel-wise probability is wide-applied recently (e.g., "Dense 3D Regression for Hand Pose Estimation", "AWR: Adaptive Weighting Regression for 3D Hand Pose Estimation", "Point-to-Point Regression PointNet for 3D Hand Pose Estimation").
    In my opinion, predicting offset makes the output joints more accurate.
  2. Sorry I don't understand your question very clearly. We use center point and bndbox to crop the hand/human-centered sub-image, mean/std normalize the original data.

@shangchengPKU
Copy link
Author

@zhangboshen
I understand the first question, the second question I read the relevant code, also understand, thank you very much, and I love you this article! Thank you again!

@zhangboshen
Copy link
Owner

@shangchengPKU
Glad to hear that. And thank you for your kind attention to our work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants