News for hackers. Stuff that matters.
Re:Tensorflow implementation of Adversarial Autoencoders by polynomial on Tuesday August 28, 2018 @02:23AM (#17856915)
For this particular implementation, what are the advantages of using it for supervised or unsupervised learning? (in general?)

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?

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 amelius on Tuesday August 28, 2018 @08:56AM (#17858425)
Question: what framework is used mostly by academic researchers these days for DL?
Re:Tensorflow implementation of Adversarial Autoencoders by nabla9 on Tuesday August 28, 2018 @09:02AM (#17858470)
Tensorflow, although PyTorch is gaining popularity.
Re:Tensorflow implementation of Adversarial Autoencoders by amelius on Tuesday August 28, 2018 @09:34AM (#17858637)
Ok. I guess in this case the authors used TF because three of the authors work at Google.
Re:Tensorflow implementation of Adversarial Autoencoders by jingleheimer on Tuesday August 28, 2018 @01:15AM (#17856676)
This code is really good.
Re:Tensorflow implementation of Adversarial Autoencoders by AstralStorm on Tuesday August 28, 2018 @04:16AM (#17857306)
And impossible to use thanks to no license information.
Re:Tensorflow implementation of Adversarial Autoencoders by edtruji on Tuesday August 28, 2018 @08:22AM (#17858205)
MIT License, it was added after your post https://github.com/conan7882/adversarial-autoencoders-tf/blo...
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.

(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.

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.