You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 on user_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 train b1 b2, validation b3, and test b4 while the history baskets for validation is b1 b2 and the history baskets for test is b1 b2 b3.
The text was updated successfully, but these errors were encountered:
Do we need it to preserve the order of b3 for validation and b4 for testing, or it can be arbitrary?
@tqtg I think we should preserve the order of b3 and b4 for validation and testing as validation data can be included in the historical baskets for test.
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.
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: