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

Ryan Curtin notifications at github.com
Fri Oct 23 09:19:52 EDT 2015

> why not just pass in the maximalInput?

Correct me if I've misunderstood---there is a maximal input for each hidden unit in the autoencoder.  So if your autoencoder has 40 hidden units, then that's 40 different maximal inputs that you want.  So you could get each of them by calling `MaximalInput()` with the indices 0 to 39.  Alternately, if the input type is a vector type (`arma:;vec` or `arma::sp_vec` or something like that), then it would be easy to create a `MaximalInputs()` function instead that returned each maximal input in a column of the given matrix.  If you want to implement one of those, either works.

> This remind me, there are other types of autoencoder, like transforming autoencoder, tied autoencoder, maybe there will be more families of autoencoder pop out in the futures, 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. If the sparsity is added, the tied autoencoder will become tied sparse autoencoder and so on.
> How should we factored out that sparse constraint is a problem.
> By the way, any interesting to implement other autoencoder?I would like to start from tied autoencoder first after SparseAutoencoder finished the refactor

Yeah, definitely I think more autoencoders is interesting, but I still think we should find a way to merge the codebase with the ANN code.  I haven't put sufficient thought into how to do that, though.  I think another one of the issues or pull requests you've opened has an idea for how to integrate the two.  Once the two were integrated, it would probably be a lot simpler to design arbitrary types of autoencoders.

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/20151023/25e8df4d/attachment.html>

More information about the mlpack-git mailing list