-
Notifications
You must be signed in to change notification settings - Fork 135
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
[FEATURE] Support chronological split for next-basket recommendation #604
Comments
Do we need it to preserve the order of |
@tqtg I think we should preserve the order of We can also add another option to specify whether we should keep the order or not. However, we need a motivating example for the arbitrary case. |
Using validation data for testing is also a debatable topic. I think it's good to include a couple of paper references as motivation for this feature. |
MMNR: Multi-view Multi-aspect Neural Networks for Next-basket Recommendation, code https://github.com/Hiiizhy/MMNR |
Description
Dataset can be split by the order of basket in user sequence.
NextBasketEvaluation
now supports splitting data by user sequence. The data will be split based onuser_id
, meaning users in training, validation, and testing do not overlap.In this requested feature, users in validation and test should be available in training data.
Expected behavior with the suggested feature
We can keep the last basket in sequence as testing, second last basket as validation, and the rest as training. For example, a sequence
b1 b2 b3 b4
can be split into trainb1 b2
, validationb3
, and testb4
while the history baskets for validation isb1 b2
and the history baskets for test isb1 b2 b3
.The text was updated successfully, but these errors were encountered: