Dataset `update_interactions` method

Aberta
  • Algo errado?
#240 2 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Estagnada
Stack de tecnologia
pandas, python
Domínio
data, machine-learning

Direção de pesquisa

Read the discussion in issue #176 and review the Dataset implementation to understand how interactions, user and item ID maps, and feature rows are represented. Decide the intended API and whether to implement add or replace; the issue leaves both the method name and first release scope open. Done means interaction updates preserve the required ID map and feature row ordering, with behavior for duplicate pairs defined.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

enhancement
Feature Description

Draft functionality (to be discussed):

update_interactions method of the Dataset accepts:

  • interactions_df : pd.DataFrame
  • method: tp.Literal["add", "replace"]

The main goal is to get old dataset id maps, extend them to new users and items. Then convert new interactions to internal ids and append those new interactions to the old ones.

We have one very important thing to remember: dataset id_map always has hot users (who have interactions) before warm users (who don't have interactions but have features). New hot users should start from the last id that was relevant for the old hot users.
But previously these id belonged to warm users. So warm users will have their ids changed. So user_features array should also be changed. Row numbers in user_features correspond to internal user ids.
Same for items.

In the first PR we can implement just one of the methods.
"add" method should just append new interactions to the old ones. (duplicate user-item pairs will have multiple entries, this will result in their weights summed in user-item matrix)
"replace" method should remove old interactions.

Why this feature?

This allows for incremental training for models that support fit_partial.

Additional context

Discussed here: https://github.com/MobileTeleSystems/RecTools/issues/176

Updating user and item features should be done in next PRs.

Maybe we should call this method update_data or smth like that to create only one method for interactions and features with optional arguments.

To be discussed

Linguagem predominante
Python
Estrelas
457
Forks
55
Nenhum PR com merge em 30d

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de MTSWebServices/RecTools

Todas as issues de MTSWebServices/RecTools

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.