You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to run experiments with the “historical” DCGAN architecture on CIFAR10, noting that, unlike the original paper by Radfort et al. (2015), the discrimination is not bounded to a [0,1]-classification, nor is it trained with the BinaryCrossEntropy loss. Instead, the sigmoid activation is replaced by the softplus function.
Investigating the code history revealed that older versions comply more with the original DCGAN, but were adapted with commit 3f875a9.
Maybe you could explain your design decision. Why was the original Binary-Classification with BCE-Loss replaced? Is there some work backing the current implementation?
I am very much in favor of a solution where the “vanilla” version actually contains the original loss to preserve consistency with the literature. I therefore suggest rolling back the change of the quoted commit and adding a new loss that contains the unbounded variant.
Nevertheless, many thanks for the code provided!
The text was updated successfully, but these errors were encountered:
Hello,
I wanted to run experiments with the “historical” DCGAN architecture on CIFAR10, noting that, unlike the original paper by Radfort et al. (2015), the discrimination is not bounded to a [0,1]-classification, nor is it trained with the BinaryCrossEntropy loss. Instead, the sigmoid activation is replaced by the softplus function.
Investigating the code history revealed that older versions comply more with the original DCGAN, but were adapted with commit 3f875a9.
Maybe you could explain your design decision. Why was the original Binary-Classification with BCE-Loss replaced? Is there some work backing the current implementation?
I am very much in favor of a solution where the “vanilla” version actually contains the original loss to preserve consistency with the literature. I therefore suggest rolling back the change of the quoted commit and adding a new loss that contains the unbounded variant.
Nevertheless, many thanks for the code provided!
The text was updated successfully, but these errors were encountered: