google-deepmind / google-deepmind/Temporal-3D-Pose-Kinetics
Facing issues with custom regressor
- Dominant language
- Python
- Stars
- 225
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
Hi there,
I am trying to replicate this paper's work which is why I am using the custom regressor that is provided. However, I am unable to generate the correct results.

In the image above, the yellow points are the ground truths, the blue points are generated using the Cocoplus Regressor provided in the HMR GitHub repository and the red points are generated when I use the Custom Regressor that you provided. I just used the Custom Regressor in place of the Cocoplus Regressor without changing any code (as it is a drop-in replacement).
I am not quite sure about the issue behind getting the wrong results. Is there anything that needs to be altered that I am missing (for eg: something is normalized that needs to be changed before usage)? I will be looking forward to hearing back from you. Thanks!
Note: I have tried using other joint regressors as well, and those work fine.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported comparison between the Cocoplus Regressor from the HMR GitHub repository and the provided Custom Regressor, using the linked image as the expected-result context. Check whether the regressors differ in normalization or input handling, and confirm completion by matching the custom regressor's generated points to the ground truths and the working alternative regressors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100