[mlpack-git] [mlpack] [Proposal]Add a function to visualize the results of sparse_autoencoder (#452)

stereomatchingkiss notifications at github.com
Fri Oct 23 02:53:19 EDT 2015

>I think eventually SparseAutoencoder should be refactored to fit inside of

This remind me, there are other types of autoencoder, like transforming autoencoder, tied autoencoder, and maybe there will be more families of autoencoder pop out, and they could be sparse too. Maybe we should factor out the sparse constraint as another policy? That is, provide an Autoencoder class which allowed to add the sparsity as constraint, then this autoencoder will become SparseAutoencoder.

By the way, any interesting to implement those autoencoder?

Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.cc.gatech.edu/pipermail/mlpack-git/attachments/20151022/5a89f63e/attachment.html>

More information about the mlpack-git mailing list