[mb-devel] Collaborative Filtering: Artist - Artist Relationships
(Summer of Code Proposal)
sharon myrtle
sharon.myrtle at gmail.com
Thu Mar 29 09:46:45 UTC 2007
>
>
> What about this method:
> keep two copies of the user rating count: the one used for the last
> vector computation, and the current count. The first would be updated
> only when the vector is computed again. The second would be updated
> each time a user changes his vote. Then trigger the computation only
> when the differences between the 2 counts is large enough to justify a
> new computation. This could be done immediately (when the user changes
> his vote) or by periodically browsing the counts. Of course this means
> that you are able to decide what is the minimum difference which
> should trigger a computation.
>
> --
> Frederic Da Vitoria
Yes, this would be a great way to get around the problem of excessive
computation as well as be up-to-date with any major change in the rating
values.
[actually, I implied something along these lines (of storing 2 copies) when
I mentioned about calculating correlation vector and then updating the
vector with the mean of the current ratings after a time lapse :-)]
--
Regards,
Sharon.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.musicbrainz.org/pipermail/musicbrainz-devel/attachments/20070329/b20794d3/attachment.htm
More information about the MusicBrainz-devel
mailing list