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

Figure out CGAN's condition label #20

Open
daa233 opened this issue Jan 3, 2020 · 1 comment
Open

Figure out CGAN's condition label #20

daa233 opened this issue Jan 3, 2020 · 1 comment

Comments

@daa233
Copy link

daa233 commented Jan 3, 2020

Hi @kozistr, Thanks for your great work!

In your CGAN implementation, you feed G and D with the same real label from the dataset as the condition.However, I have a question about this since several other implementations feed G with a sampled label as the condition.

I have seen several CGAN implementations. There are two ways to use the condition labels:

  1. feed G with a random label, feed D with the real label
  2. feed both G and D with the same real label

Here are my questions:

  • Which way is used by the CGAN paper in 2014?
  • When training the CGAN, should we use the same condition label for both G and D?

The same issue has been asked here. I hope we can figure out it together.

@kozistr
Copy link
Owner

kozistr commented Jan 19, 2020

thank you for your interest!

  1. As i know, specific implementation is not referred in the cGAN paper. But the Figure 1 at page 3, y vector is used as the same manner. so, i guess the author maybe used the same condition label for both of them.

  2. actually, i think there's no need to be trained with the same condition label for both G and D. In the aspect of the implementing the code, using the same condition label is easier than the different condition label (cuz we need to generate another sample for D). and i also think using the same condition label can lead more stable training and is more make sense for the purpose of D (it is not sure 100%).

thank you in advance!

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