Re:Tensorflow implementation of Adversarial Autoencoders
by locuscoeruleus on Tuesday August 28, 2018 @09:20AM
(#17858570)
From what I can gather the supervised approach allows you to only learn the representation for style rather than which digit it is. The only reason to use one over the other is to demonstrate that it works, I guess?
Re:Tensorflow implementation of Adversarial Autoencoders
by Lorkki on Tuesday August 28, 2018 @05:12PM
(#17862932)
Though, in the finest academic tradition, once you try to actually run it, you'll find that it silently depends on a separate library written by the author, which you'll have to find yourself.
Re:Tensorflow implementation of Adversarial Autoencoders
by conan7882 on Thursday August 30, 2018 @04:02PM
(#17880217)
I though I have removed all the dependency on 'tensorcv'. It turns out I forgot the dataflow part. Now it should be run without 'tensorcv'. Thanks for pointing out.
And if it's just being used for the MNIST dataset, is there a particular reason for using it in one or the other fashion?
(In this case "tensorcv", which is in a separate repository: https://github.com/conan7882/DeepVision-tensorflow )
That aside, I agree that it's an easier read than most ML code.