News for hackers. Stuff that matters.
Re:Show HN: Gorse – A recommender system back end based on c... by DonaldFisk on Wednesday November 27, 2019 @05:43PM (#21652905)
Maybe it's just coincidence, but the name Gorse resembles Go+Morse (http://www.fmjlang.co.uk/morse/MORSE.html), and the name Steamlens resembles like Steam+Movielens (https://movielens.org), both early recommendation systems.
Re:Show HN: Gorse – A recommender system back end based on c... by lutun on Wednesday November 27, 2019 @08:16PM (#21653869)
Yep. SteamLens is the combination of Steam and MovieLens. However, gorse means Go recommender system engine :D
Re:Show HN: Gorse – A recommender system back end based on c... by DonaldFisk on Thursday November 28, 2019 @07:23AM (#21656721)
You might want to have a look at the Morse paper. It describes an algorithm which worked well, significantly better than KNN, at least on movies, using, by today's standards, a small data set. Unfortunately, when I inquired about open sourcing the code, I was told that BT had lost it. But the algorithm is described in detail in the paper.
Re:Show HN: Gorse – A recommender system back end based on c... by lutun on Friday November 29, 2019 @12:22AM (#21662251)
I'll have a look at it. :)
Re:Show HN: Gorse – A recommender system back end based on c... by Reubend on Wednesday November 27, 2019 @05:01PM (#21652602)
Looks good, I'll keep an eye on this as development goes on. One thing I'm particularly curious about: the project page emphasizes optimization through SIMD instructions and multi-threading. Are there any benchmarks versus other recommendation engines to demonstrate what type of performance improvement one should expect?
Re:Show HN: Gorse – A recommender system back end based on c... by lutun on Wednesday November 27, 2019 @08:19PM (#21653873)
Thanks for your feedback. More benchmarks should be added later.
Re:Show HN: Gorse – A recommender system back end based on c... by bdibs on Wednesday November 27, 2019 @12:23AM (#21645474)
I’ve been looking for a recommender system, how does this compare to something like Apache’s PredictionIO?
Re:Show HN: Gorse – A recommender system back end based on c... by lutun on Wednesday November 27, 2019 @08:01AM (#21647456)
PredictionIO is built for the large scale recommender system based on Spark. But gorse is designed for datasets that fit a single PC. :D
Re:Show HN: Gorse – A recommender system back end based on c... by anotheryou on Friday November 29, 2019 @11:18AM (#21665185)
I get an error 500 on steamlense :/
Re:Show HN: Gorse – A recommender system back end based on c... by lutun on Friday November 29, 2019 @11:32PM (#21668522)
It might happen when Steam API requests exceed limits :O
Re:Show HN: Gorse – A recommender system back end based on c... by anotheryou on Monday December 02, 2019 @02:47AM (#21680624)
sadly persistent...
Re:Show HN: Gorse – A recommender system back end based on c... by dang on Tuesday November 26, 2019 @11:31PM (#21645264)
We changed the URL from https://github.com/zhenghaoz/gorse to the project page.
Re:Show HN: Gorse – A recommender system back end based on c... by nighthawk648 on Wednesday November 27, 2019 @07:20AM (#21647248)
An followed by a word starting with a constant is grammatically incorrect, can you fix this as well?
Re:Show HN: Gorse – A recommender system back end based on c... by teh_klev on Wednesday November 27, 2019 @01:19PM (#21650406)
Well if we're going to get nitpicky I think you meant "consonant" instead of "constant" ;)
Re:Show HN: Gorse – A recommender system back end based on c... by nighthawk648 on Wednesday November 27, 2019 @02:49PM (#21651334)
Ooops
Re:Show HN: Gorse – A recommender system back end based on c... by lutun on Wednesday November 27, 2019 @07:47AM (#21647381)
Sorry. I forgot to change the quantifier when I shorten the title.
Re:Show HN: Gorse – A recommender system back end based on c... by nighthawk648 on Wednesday November 27, 2019 @02:49PM (#21651331)
Do not apologize :)
Re:Show HN: Gorse – A recommender system back end based on c... by dang on Wednesday November 27, 2019 @05:05PM (#21652642)
Fixed now!