-
Notifications
You must be signed in to change notification settings - Fork 68
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
Getting IndexError while Running run_metrics.py with Places2 #43
Comments
Oh, you need to specify '--resolution=512' |
Thanks for the reply, it now worked! However, I was not able to replicate the results of the paper. In the paper, the followings were reported for Places2 dataset.
What I got:
Running it several times also led to the same slightly inaccurate results. I have the same issue with FFHQ Dataset, too. One more point is that I got very similar results to paper when I specified the masked ratio between 0 and 0.2 Any idea why this happens? |
Quite strange. What is your result for FFHQ? |
For the metric
For the metric
|
What is your numpy and tf version? |
My TF version is "1.15.0", and my Numpy version is "1.17.3". I am using the provided Dockerfile. However, metric evaluation was not working, therefore, I changed it a bit:
If it helps, here is my log.txt:
|
I still have no idea what causes this error... One hypothesis is that the randomness of the mask generator's behavior has changed, which may slightly bias the difficulty of the task |
Hi,
Thanks for sharing this great work!
I have a question about running
run_metrics.py
with Places2 dataset.As it is indicated in Datasets section, I downloaded the validation set of Places2, and converted into TFRecords with
--shuffle --compressed
flags.However, when I try to run `run_metrics.py' (I set metrics=idk36k5), I got the following:
When I debug the code, I realized that
tfr_shapes=[[74989]]
intraining/dataset.py
line 82. Here is the "features" dictionary without bytes_list:I am using the provided Docker image.
The text was updated successfully, but these errors were encountered: