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 GeometryEncoder instead GlobalGenerator #3

Open
Michel-liu opened this issue May 27, 2021 · 3 comments
Open

Why GeometryEncoder instead GlobalGenerator #3

Michel-liu opened this issue May 27, 2021 · 3 comments

Comments

@Michel-liu
Copy link

Hello, nice job! I have a question, why don't use the encoder(including downsample and resnet-blocks) part of GlobalGenerator with ngf=32 as Geometry Encoder directly, but train a GeometryEncoder with ngf=64. Thanks.

@ty625911724
Copy link

Dear Michel:
Since sketches and images are encoded into a share space, there are two GeometryEncoder for sketch and image individually. GlobalGenerator just translates images to sketches.
Thanks!

@Michel-liu
Copy link
Author

Thanks for your answer! Is the 32.2k images list used in FFHQ public available? And I wonder about your strategy for selecting training image pairs in the disentanglement process, for example, gender, age, facial covering, etc. Thanks.

@ty625911724
Copy link

Thanks for your interests. We will release the training list in the future.

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