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

LFW Preprocessing details. #4

Open
black-puppydog opened this issue Sep 18, 2017 · 1 comment
Open

LFW Preprocessing details. #4

black-puppydog opened this issue Sep 18, 2017 · 1 comment
Assignees

Comments

@black-puppydog
Copy link

black-puppydog commented Sep 18, 2017

In the paper, you write that you use dlib to preprocess data.

Given that the images in this file:

url='https://www.dropbox.com/s/isz4ske2kheuwgr/lfw_aegan.tar.gz?dl=1'

all differ from the originals, and from all the aligned datasets provided on the LFW website, could you elaborate on how it was created?
The filename seems to imply a connection with AEGAN, but the aegan repo doesn't use dlib at all. So I'm not sure how to go from the original lfw dataset to the one you used, and I don't find this in this repo either, at least not for the data used in demo1.py.

Oh and by the way, the file contains 13238 .jpg files (and some extra ._xxx.jpg files that OS X put in there).
The five extra images are Ralf_Schumacher_0005_* images that are actually results, not inputs.

@paulu
Copy link
Owner

paulu commented Sep 18, 2017

Dlib is not used in demo1. We use the same alignment as AEGAN in order to control for that factor in our comparison. Specifically, this means we used the images from DeepPy. The images in lfw_aegan.tar.gz were created by running AEGAN and extracting the individual images from the cache files generated by DeepPy.

Thanks for pointing out the extra files.

@paulu paulu self-assigned this Sep 19, 2017
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