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

train model for different $w$ #4

Closed
betterze opened this issue Apr 16, 2020 · 5 comments
Closed

train model for different $w$ #4

betterze opened this issue Apr 16, 2020 · 5 comments

Comments

@betterze
Copy link

Thank you for your great work. I have a simple question.

In the training section, you mention that 'change repleated $w$ for all layers to different $w$s'. There are a few pretrained models in stylegan which use repleated $w$, could I just adapt the weights from them or I need to retrain the model?

Thank you for your help.

@betterze
Copy link
Author

And would you mind uploading the manipulation boundary for face? Thank you again for your help.

@betterze
Copy link
Author

any response?

@ShenYujun
Copy link
Contributor

And would you mind uploading the manipulation boundary for face? Thank you again for your help.

Sorry, but the npy boundaries are ignored by git before. Now, all boundaries are uploaded.

@ShenYujun
Copy link
Contributor

Thank you for your great work. I have a simple question.

In the training section, you mention that 'change repleated $w$ for all layers to different $w$s'. There are a few pretrained models in stylegan which use repleated $w$, could I just adapt the weights from them or I need to retrain the model?

Thank you for your help.

Although we recommend using different ws for different layers, using same w (i.e., the official StyleGAN) also works. You can use the official StyleGAN model and then use IDInvert to train your own encoder and use InterFaceGAN to find your own boundaries.

@betterze
Copy link
Author

And would you mind uploading the manipulation boundary for face? Thank you again for your help.

Sorry, but the npy boundaries are ignored by git before. Now, all boundaries are uploaded.

Thanks a lot, I will try it.

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