-
Notifications
You must be signed in to change notification settings - Fork 40
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
Implement non-accuracy metrics #58
Comments
If @saulvargas has the time to spend on this, it would be great! 👍 |
I think we should strive to have some basic metrics, e.g. ILS earlier than 0.5. Definitively no later than 0.5 at least. |
Hi! I'd be happy to contribute. Implementing the basic version of some common*** diversity and novelty metrics is easy and straightforward. I propose to implement the following:
|
@saulvargas awesome! 👍
|
Btw @saulvargas, if during this process you have any suggestion to improve the evaluation module, please, let us know and we can discuss about it (a comment here should be enough). |
@saulvargas any progress here? Can we (me and/or @abellogin) do anything to help you? |
Done! I implemented the basic version of some novelty and diversity metrics, that is, without relevance or rank discount. If you were interested in these functionalities, then we would have to talk... |
👍 |
Current iteration closed in 47b2347 |
I would like to release an implementation of the "binomial diversity" metric of the paper in RecSys 2014 (http://ir.ii.uam.es/saul/pubs/recsys2014-vargas-tid.pdf). Do you think it could be included in RiVal? |
Sure, go for it. |
I suggest you open an issue with the metric you want to implement and assign it to yourself. If you have timeline for when you think you might have it done, assign it to one of the milestones that fits your time estimate |
Awesome! Besides, this would give more publicity to the framework, which is great ;) |
Like novelty, diversity, etc.
We should try to involve someone else that already measured them (e.g., Saúl Vargas @saulvargas)
Milestone: later than 0.5?
The text was updated successfully, but these errors were encountered: