no, scaling is of help but its hard to quantify how. i have two other observations we can discuss then
ruaok
scaling, not full normalization?
_lucifer
ruaok: i only tried scaling till now, as we discussed the other day
ruaok
do you think we'll get an improvement going further?
_lucifer
1) i got scores like 0.4 and 0.2 so on on a scale of 0 to 1 when i used a smaller set of listens
2) these scores are somewhat in line with using the ones we got when we were using counts directly
hard to say ruaok, the question is how to tell if the recs became better
pristine___
_lucifer: what is mean is say I have two rec A and B, before scaling if the scores were 1, 2 and after scaling they are 10 and 20, does this mean any improvement?
_lucifer
pristine___: the scores are relative and not an indication of whether the user will like it, so a strong maybe
the scores make sense relatively but absolutely they are just a bunch of number
pristine___
I understand they are relative, just trying to understand if we really need to scale/normalize
:)
_lucifer
pristine___: imo we probably should because that theoretically brings all users on a same scale but practically to decide that we need some way to see if tell whether the recs have become better or not
pristine___: what is the usual rmse for the model ?
pristine___
I don't remember :( You can generate model HTML file for that it had a table
Has*
_lucifer
i did, its 0.12
i wanted to know the value without scaling
pristine___
I get that, but I don't remember:( I will search for the html in my pc once I reach hotel :)
_lucifer
np, thanks
shivam-kapila
_lucifer: any talks you preparing
_lucifer
no, shivam-kapila , you ?
shivam-kapila
Wanted to, but couldnt find anything interesting
pristine___
> imo we probably should because that theoretically brings all users on a same scale but practically to decide that we need some way to see if tell whether the recs have become better or not
Yeah _lucifer. Even if they theoretically bring all users to same scale, I think we should only work on this further if recs are actually improved for that we need a way to determine if recs have improved or not.
shivam-kapila
Improved recs is rather a user dependent term
Feedback is the best here
pristine___
shivam-kapila: of course! Didn't pay attention to the best term here but I guess _lucifer understood 😉
shivam-kapila: Hi! About the folow button, I think it looks nice. If you want to try to hide text until the user hovers (you'll need to add icons there surely), check out the existing code: https://github.com/metabrainz/listenbrainz-serv...
yvanzo
I filled Saturday’s timetable with “State of stuff” topics, Sunday can be for more sessions but there are only MB ones for now, more can be added to the wiki.
imdeni has quit
imdeni joined the channel
alastairp clones troi
shivam-kapila
Mr_Monkey: hi
yvanzo
updating beta.mb.o
shivam-kapila
I wanted to know what you prefer
Those icons ones or only text ones
CatQuest
I thikn riker would dsilike that
(or possibly *like* who knows :3)
shivam-kapila
I was confused as new ux concepts say to put less transitions
So that it doesnt steal focus
diru1100
is anyone into pictionary? or only sticking to among us
shivam-kapila: Ah, I see. Well, personally I like the transitions, and that the button is small when not hovered. But you could also just resize your follow button and have a similar result without the need for transitions.
shivam-kapila
Lets stick to what iliekcomputers suggested
ruaok
Mr_Monkey: was it you who brought the projector last year?
shivam-kapila
Thanks for feedback
Mr_Monkey
ruaok: Yis
ruaok
planning on bringing it again?
Mr_Monkey
Oh, shivam-kapila, one more thing: the button doesn't look vertically centered with the user name, as far as I can tell from a quick look
ruaok: sure, if we need it no problem
ruaok
I think it might be nice to have, if you dont mind.
shivam-kapila
Mr_Monkey: old one or proposed one
Mr_Monkey
The screen you shared yesterday (was it yesterday?)
iliekcomputers suggested not to change the button near username
But only in feed list
Mr_Monkey
Ah, I see
alastairp
ruaok: do you want review feedback on troi too? I feel the answer to most of my questions of the form "why did you do it like this?" will be "because that's how it organically grew"
I can contribute changes in, but I'm not sure how much of it is in flux
ruaok
yes, I'd like that feedback. there are a lot of things still in flux, but I think things are starting to stabilize.
I forgot that I had already added troi.acousticbrainz.annoy -- so that part is already done.
alastairp
yep, I just have a few parameters to change there
ruaok
I'm writing a manage.py-like entry script as we speak.
alastairp
and I'm just putting in a new distance metric now
I remember that we had this discussion about BPM. for reasons, we currently treat integer multiples of a bpm as the same (e.g. I just tried with a 71bpm track and got back a 142bpm track as very similar)
ruaok
peak finding in frequency space?
alastairp
yeah, basically
people aren't really good at distinguishing them in many situations either
kieto joined the channel
ruaok
I wonder how many real world scenarios that will go wrong in.
I look forward to discovering that bug.
alastairp
I'm trying to remember where I encountered this, I think someone I know was building a dataset of known tempos in order to evaluate an algorithm
get many people to annotate each song, etc, in order to be sure that the annotation is good
and some songs there was a 50% split between people who thought it was 60 and who thought it was 120
I'm trying to look it up
ruaok
and these weird mutliples started showing up...
alastairp
anyway, I think that when asking for songs of bpm 120, people would rather have a song _not_ show up (because the algorithm incorrectly chose 60 instead of 120) instead of having a bunch of obviously 60bpm tracks show up as "close"
ruaok
agreed.
alastairp
ah, some interesting feedback from MTG
> you should take other variables into account then. tempo is highly correlated with genre
> don’t recommend techno 60BPM to people who listen to ambient with 60BPM
sounds like our hybrid similarities (that include more than 1 feature) are going to be necessary soon
_lucifer
like building a content profile ?
ruaok
alastairp: that's totally duh in hindsight. :)
alastairp
yeah, but you can see how starting with an observation (tempo octave errors happen), and going down a particular path gets you in trouble
I would stay that there are many many paths in recommendation work... most of them get you into trouble.
alastairp
(it's 200 pages, you don't need to read it all)
in section 6.6.3 he proposes a new metric for comparing tempo estimation error by using log2 scale, so that the scale of the error is the same in different octaves
most people evaluate algorithms using "if it's within 4%, it's good". but 4% of 60 is not the same as 4% of 120!
ruaok
ding
alastairp
I'm getting some good suggestions in another chat, which I'll note down
it also depends on if we want to do "similarity", or just plain search
I wonder if it makes sense for these features with fewer dimensions to use annoy, or if we actually just need solr
ruaok
BPM and key?
alastairp
yeah. "get me things with feature x" should just be search
ruaok
I think they are a poor fit for annoy. the results end up in too few buckets.
+1
alastairp
when you need to introduce fuzzyness into it, that's where it excels
ruaok
yep, with range data.
CatQuest
diru1100: I'd love some other game than fightinggame tbh
"why did you do it like this?" will be "because that's how it organically grew"
this needs to be quoted for truth. mb 20 yr history, that is the answer to a lot of newer users question :D
diru1100: https://skribbl.io/#collapseHow does look liek fun! reosarevok wanna play this isntead/inaddition to this among us thing?
diru1100
It's pictionary
You draw the word that you got and others will guess