cornac icon indicating copy to clipboard operation
cornac copied to clipboard

[FEATURE] Time-wise wrapper for all models

Open vlainic opened this issue 4 years ago • 3 comments

Description

I have used your UIRT data format, but this did not help for my case at all even though I would expect it does. But I have found an interesting framework/wrapper approach that could be implemented with any model. So it might sound interesting for you guys.

Expected behavior with the suggested feature

The idea is very simple - using SLRC paper and it's github implementation to make time-wrapper for better leveraging of time information.

Other Comments

If you want, I could help coding part too :)

vlainic avatar Jan 03 '22 09:01 vlainic

Thanks for pointing out the interesting resources. We will try to take a look, and of course we welcome your contributions.

qtuantruong avatar Jan 09 '22 06:01 qtuantruong

Hi, thanks for this suggestion.

  • Could you please clarify what is the connection between the UIRT format and the SLRC method?
  • How does SLRC work, and how does it affect existing recommender models? For instance, given a recommender model (e.g., BPR) do we need to change its objective functions? Meanwhile we are taking a look at the paper. Thank you.

saghiles avatar Jan 09 '22 12:01 saghiles

Hi, thanks for this suggestion.

  • Could you please clarify what is the connection between the UIRT format and the SLRC method?
  • How does SLRC work, and how does it affect existing recommender models? For instance, given a recommender model (e.g., BPR) do we need to change its objective functions? Meanwhile we are taking a look at the paper. Thank you.

Hello,

In my understanding (that might be wrong) of your UIRT is that adds the time dimension to the training, OR is it just a time-wise dataset sorting/split? In the latter case, there is no connection :)

For cornac the key sentence from the SLRC paper would be the one from the conclusion "Generally, our model is able to be leveraged as a framework that utilizes repeat consumption information to enhance existing recommender systems based on collaborative filtering...". Henceforth it can be seen as the time-wise wrapper for any recommender and I don't think that any objective functions should be changed, i.e. model is flexible around that. The "only" relevant thing (IMO) is that there might be some careful implementation of the SLRC as the wrapper to make it compatible with all the tools in cornac.

Thank you for the replies and consideration.

vlainic avatar Jan 10 '22 06:01 vlainic