-
Notifications
You must be signed in to change notification settings - Fork 25
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
About Downloading with PyDrive #10
Comments
Hi @xuedue, It looks like Google have updated that page. Just follow these instructions in the prerequisites section: Specifically bullets 3 & 4. What PyDrive really needs is the credentials files. I will update the readme file accordingly soon, sorry about the confusion |
These errors seem like local connection or firewall issues, there is nothing I can do about it. |
The script downloads the in-the-wild images of the original FFHQ dataset, because we take slightly larger crops than the original FFHQ dataset. The downloaded in-the-wild images are deleted after processing and aren't saved, but their overall size is indeed 0.93TB. The Final dataset size depends on the final resolution of the image (defined by the user), if you save 1024x1024 images the size will be about 90GB, slightly larger than the original FFHQ dataset because of the segmentation maps. For 256x256 resolution, the final size should indeed be around 7.5GB |
Thank you for your reply. I just run the get_ffhq_aging.bat without any modification. So the size of data set should be 7.5GB after downloading. I am sorry to confirm again. I wanna to know if my disk space only needs to be greater than 7.5GB. And Except for the 256*256 pictures that need to be saved, no other pictures will be downloaded to my disk? I am a little afraid that all 0.93TB of data will be stored on my disk. |
Your disk space shouldn't be larger than 7.5 GB. You can look at the download script and see that each thread deletes the in-the-wild image right after processing is done. FFHQ-Aging-Dataset/download_ffhq_aging.py Lines 223 to 241 in e10e2de
So during download, the maximum number of in-the-wild images on your disk will be |
I am sorry to ask again. When I used PyDrive to download, I encountered a problem. In the middle of downloading, the program will report the following error. I am confused that the program does not report an error at the beginning but reports an error during the download. I spent two days trying to download and search for solutions to this problem. But this problem is still unsolved. |
Hi @xuedue, This also seems like a local machine issue that doesn't relate to the downloading code. Google-ing your error message suggests it might be a proxy issue. Here is the most relevant result: |
Well, but I just use the school network. I want to know that 256x256 resolution dataset has any difference with the origin NVIDIA FFHQ dataset except for the resolution? Could you provide the resize code for me? If I resize the original FFHQ dataset image to 256*256, does it mean that I have obtained the image data and annotation data(ffhq_aging_labels.csv) of your paper? Sorry to bother you again. |
It might be an issue with your school's network than
There are differences in the dataset, we take larger crops, that's why we start from the in-the-wild images.
The alignment code is this function: FFHQ-Aging-Dataset/download_ffhq_aging.py Line 245 in e10e2de
No, since the crops are different, If you wish, you can run the segmentation code on the original FFHQ dataset to get the correct segmentation maps. The annotation data is correct regardless of the image size or cropping method (the age, gender and the rest of the labels don't change). However, since the crop size is different you won't get the exact same results that we got in the paper. That's because tighter crops don't capture the change in head shape through the years so well. |
我也遇到了同样问题,请问您是如何解决的? |
@woshixiaozhou, please use english in comments |
Hi there! |
Hi @ahripanto, What we saw initially, which led us to write the pydrive optionality, was that we got a quota limit error with the original download script (which matches the script provided by Nvidia) even though we were able to manually download the same file from Nvidia's google drive. Using pydrive eliminated this issue, because it is using exactly the same API as in google drive. However, if the quota limit is indeed exceeded and you can't download a file manually, pydrive would not solve the issue. In that case that's a hard limit put by Google and there's nothing that can be done about it except waiting for the quota to be released. The script indeed tries to access Nvidia's google drive and not your own. The dataset is just shared with you, it's not actually located on your personal google drive, there are 2 reasons for that:
|
Hi @ royorel, |
@woshixiaozhou I'm asking once again to use English. |
@xuedue It seems that you have downloaded the dataset successfully. Could you please share the image (50958.png 256x256 pixel) with me because there is something wrong with this image (0 bytes) in my case. Thanks lot! |
Hi @wangtingwei1993, We cannot directly share images. However, the non cropped in-the-wild image can be found at: After downloading it you can apply the rest of the script to it |
Hello author, thank you for sharing.
I met "quota exceeded" error and I wanna download with pydrive. But in Step2, after click on enable drive API, I can't find the destop App,
I wanna know how to Select Desktop app and Download client configuration.
Thanks again.
The text was updated successfully, but these errors were encountered: