-
Notifications
You must be signed in to change notification settings - Fork 52
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
karras2019stylegan-ffhq-1024x1024.pt #18
Comments
You can download the official styleGAN weights at this time. You can find stylegan-ffhq-1024x1024.pkl in the Resource section of the README below. If you can't use google drive, I can't help you because the way I provide it is also google drive. Sorry about that. |
Thank you very much for your reply. I've got the file. The weight_convert.py file frequently displays “no attribute ‘XXX’“ errors, so I want to know which version of your TensorFlow is? Does expression transfer correspond to facial_exchange.py file? Thanks again for your reply. |
The environment at the time of development has been discarded, but it should be possible to convert it using tensorflow-gpu==1.15. |
Thank you very much for your answer. I encountered the following problem when running the facial_exchange.py file. The problem is with the line "loss_2.Backward ()". After querying, it is found that if the "optimizer.step()" after "loss_1.backward ()" is removed, it can run normally, so does removing this line have any effect? Is the result still correct?In addition, what are the meanings of the four folders of program running results: a, e, result1 and result2 respectively? I am very sorry that I did not observe the corresponding relationship in the result, so I ask you for help. I am looking forward to your reply. |
Hmmm. Maybe it's the version of pyotrch. I'm sorry but I can't experiment right away in my environment. is it possible to try with an older version such as pytoch 1.4.0? |
Can anyone share weight files? The link provided by the author cannot be downloaded at this time.
The text was updated successfully, but these errors were encountered: