-
Notifications
You must be signed in to change notification settings - Fork 564
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
How long should it take to preprocess for global direction? #95
Comments
Would you mind checking you gpu usage when you run the 'SingleChannel.py'? |
you are using TensorFlow, version 1.14 or 1.15? |
I should add that I am using google colab to train. It is using Tensorflow 1.15.2 |
To be honest, this never happens to me. I use a gtx 1080 gpu on my local computer. It takes around 4 hours. Your gpu is better than mine, it should be faster. Could you provide the log when you run the codes?
The 'SingleChannel.py' will take 4 hours.
'PlayInteractively.py' is for the GUI, I am not sure if the GUI could be run in Colab. Which dataset or SyleGAN model you are using? |
Yes, I was surprised too when it is taking more than 4 hours. I am running exactly the same set of codes, just in Google Colab:
The StyleGAN model should be whatever is the default one (i.e. StyleGAN2) |
The log is long. But here it is:
|
The log seems to be correct. Maybe this is related to colab. Maybe colab allocate the same gpu to multiple users? I am not an experter in colab. |
I recently tried to preprocess in my own pc which has 1080 gpu (tf 1.14). I am facing two problems... with the current settings of 100 images, it is facing out of memories when it tried to calculate features using clip. Second problem: when I don't calculate features and only generate images, it shows me per layer it will take 2 hours...and there are 11 layers...and so back to ~24 hours 😅 Just out of curiosity how many images and steps were you able to run for in 1080? |
actually, my 2080ti ran for about 24 hours |
which code can i use to find the global directions on a custom dataset? |
I think in the paper it is mentioned it takes ~4 hours to preprocess the global direction for FFHQ. However, when I tried to proprocess for the same FFHQ model, it is taking ~24 hours (using V100 GPU). I did not change any settings. Is it expected? Or am I missing something?
The text was updated successfully, but these errors were encountered: