200 karma · joined June 14, 2012
But even the Hacker News audience does not have enough geekiness to understand my previous attempt at a movie recommender system: http://5000best.com/movie-galaxy/
I guess the right way to fix it is to hide some features and add a tutorial.
Edit: the stack is G-WAN and everything is written in plain ANSI C. I wrote my own HTTP servers in C/C++ for my previous websites, but this time I tried G-WAN. I think it saved me one week of work or two.
The website is running on the cheapest virtual dedicated server from 1&1 with 25% of one processor time. The total cost is less than $10 monthly.
Regarding the DBM - I also tried to use more than one layer, and without success. I tried out 3-layer and 4-layer autoencoders (can be called 1.5-layer and 2-layer DBM), with initialization by stacked RBMs or without it. It did not work well probably because: a) the model was inaccurate, and b) the learning method proposed for DBM was not completely correct. Intuitively, the right DBM-like model with the right learning method should have a chance to improve something on the Netflix task.
I found some improvement though (rather learning time than accuracy) in the standard RBMs. Instead of using CD, I split the weights into two sets, creating a directed RBM version. The "up" weights from the visible nodes to hidden are learned with CD with T=1. The "down" weights are learned to best fit the visible nodes, using the hidden nodes as predictors. The hidden nodes generated by CD T=1 are good enough, and we do not need additional iterations with increased T.
The ranking criteria - basically, I combined ratings from IMDb and Rotten Tomatoes, with additional heuristic tweaks. The ranking method I use for is different than the popular IMDb method aka "True Bayesian estimate", which is not really a Bayesian estimate. I wrote more about how I approach ranking in my e-book http://arek-paterek.com/book/ , for people who are really interested in such technical details.
the beauty of self-publishing