-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UserKNN #10
Comments
Hi, Suresh! You're right. Items in u_list are represented as index. If you can, pull the request. Thanks for your attention! |
Problem fixed in the new version. |
Sorry for this, got busy with something else. I was thinking for creating the ensemble, the scores in each of the recommenders need to out a score in the same range. |
Hi, Suresh! How are you? I'm very busy this month. I just got back from a conference trip. I'll get organized and I'll get back to you soon to talk. Sorry for the delay. My skype: fortes-arthur@hotmail.com Regards. |
'Suggestion is to normalize the scores from 0 to 1 after sorting so the first item to be recommended by any of the algorithm would have a 1.' I did this in my ensemble algorithms, which I thought was more logical. Remembering that I make this approach to the ranking of each user isolated. |
in the method predict_similar_first_scores the common_users probably need to be looked at.
Currently with a small test data
[[0. 1. 1.]
[1. 1. 1.]
[1. 0. 0.]
[1. 1. 0.]]
Where 1 indicates seen item and zero indicates not seen. common_users is outputting a null list.
Correct me if i am wrong I thing it should be
common_users = list(set(self.users_id_viewed_item.get(self.items[item], [])).
intersection(neighbors[1:self.k_neighbors]))
common_users = list(set(self.users_id_viewed_item.get(item, [])).
intersection(neighbors[1:self.k_neighbors]))
The text was updated successfully, but these errors were encountered: