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

Question about Motion Supervision and Point Tracking #70

Open
tnarek opened this issue Aug 10, 2024 · 1 comment
Open

Question about Motion Supervision and Point Tracking #70

tnarek opened this issue Aug 10, 2024 · 1 comment

Comments

@tnarek
Copy link

tnarek commented Aug 10, 2024

Hello,

Thanks for sharing your great work!

I have 2 questions regarding motion supervision:

  1. Why do you normalize the direction vector $d_i$ in the loss (equation 3)? Can't we directly optimize for matching the position $g_i$ itself? Is it for making the latent optimization more gradual? If so, how important is it?
  2. Maybe related to the previous question -- why is the point tracking step necessary? I see that in equation 3 you are taking the target feature $sg(F_q(\hat{z}^k_t))$ from the optimized latent, which of course requires $q$ to be updated in the next steps by point tracking. But why can't the target feature be taken from the original latent, without having to update $q$?
@ivanpuhachov
Copy link

I was also wondering about the same. It seems like eq 3 has handle positions in pixel coordinates (not in natural image coordinates (0,1)^2 as I expected) so each update tries to move the point slightly. Also note that if handle position is already close to the target we skip corresponding loss term - see here

if (ti - pi).norm() < 2.:

As for 2 my guess is that we want to update features gradually. Some points in $\Omega$-region may change completely (think about the statue example - if the handle point is on the nose, under extreme rotations we want to have background pixels)

I would love to hear some confirmation from the authors

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