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

Why not train a non-linear landmark estimator? #16

Open
hallwaypzh opened this issue Jan 13, 2022 · 1 comment
Open

Why not train a non-linear landmark estimator? #16

hallwaypzh opened this issue Jan 13, 2022 · 1 comment

Comments

@hallwaypzh
Copy link

No description provided.

@universome
Copy link
Owner

We wanted to show that for our model, the geometry information is stored in a very "disentangled" manner in the latent code. If your keypoints estimator is very powerful (in the extreme case it can be equivalent to [generator + off-the-shelf keypoints detector on top of it]) then it will also be able to recover the geometry information, but it will not say anything about how difficult it is to manipulate this information by editing a latent code (since it might be very entangled)

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