-
Notifications
You must be signed in to change notification settings - Fork 42
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
"interact with in the next week" #16
Comments
Well this is a little hypothetical :). We held out the interaction data of the one week after the dataset ends. Hope that helps Daniel |
Hi Daniel, Does it mean that it is the same weeknumber for everybody? Maybe the each Thanks again :) Tales Tenorio de Souza Pimentel |
@dkohlsdorf |
The data you can access and learn on is extracted from Aug - Nov 2015. Daniel |
One followup question -- is it possible those "interactions in the next week" already appear in the users' interaction history? or we only need to predict "new ones"? From the description, it seems to be the former, but we would like to confirm. Thanks ! |
No the interactions for the test set are not in the data |
@dkohlsdorf To be more specific you say that there are no user_id + item_id present in the test interactions and train interactions. I did a quick check in which I created a submission with only training interactions and it scores 154890.45. Assuming that I didn't didn't make a mistake is this something to be expected? For example this query returns 35999 interactions. SELECT COUNT(*) FROM (
SELECT DISTINCT user_id, item_id FROM interactions WHERE week = 45 AND interaction_type in (1,2,3)
INTERSECT
SELECT DISTINCT user_id, item_id FROM interactions WHERE week < 45 AND interaction_type in (1,2,3)
) as T So I assume that a similar number is for the week 46 (test week). |
Hi data people,
I didn't understand this "next week"
"the recommender should predict those job postings (items) that the user will interact with in the next week."
Thanks :)
The text was updated successfully, but these errors were encountered: