Fix bug in computing gradient penalty #22
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a shameful bug... Obviously the part I edited was copied directly from the Github repo of improved training for Wasserstein GANs. However, in the author's code, the image was first flatten to a matrix, that's why the reduction axis was only for [1]. In this implementation, we should use reduction axis [1, 2, 3] because we don't flatten images.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a shameful bug... Obviously the part I edited was copied directly from the Github repo of improved training for Wasserstein GANs. However, in the author's code, the image was first flatten to a matrix, that's why the reduction axis was only for [1]. In this implementation, we should use reduction axis [1, 2, 3] because we don't flatten images.