Skip to content
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

Reorganize how recommendation engines are contstructed. #3

Open
rat-nick opened this issue Mar 4, 2024 · 0 comments
Open

Reorganize how recommendation engines are contstructed. #3

rat-nick opened this issue Mar 4, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@rat-nick
Copy link
Owner

rat-nick commented Mar 4, 2024

I have ran into an idea that a recommender engine is a composition of the model and the input adapter.

The model

It's an ML model that should only be concerned with performing a forward pass on data.
For KNN should be a vector in feature space, for VAE should be a vector of implicit user ratings etc.

The adapter

The adapter is responsible for bridging the gap between inner and outer IDs, converting item ratings into feature space vectors etc.

This way we can have a variety of different engines built upon a KNN model like content KNN with cosine similarity as the distance, CF KNN with cosine and jaccard distance and so on.

So my idea is that the Engine should be a composition of a Model object and an Adapter object.

@rat-nick rat-nick added the enhancement New feature or request label Mar 4, 2024
@rat-nick rat-nick changed the title Add item based CF KNN algorithm. Reorganize how recommendation engines are contstructed. Mar 4, 2024
@rat-nick rat-nick self-assigned this Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant