mayhem: the recording similarity seems to work with window sizes as well. should i export and import it on wolf somehow or setup it be to inserted in main lb db/ts db?
2022-05-28 14800, 2022
mayhem
wolf would be good. but we need to get smarter about how we identify the runs of data that we create. last time I got lost in all the attempts. thoughts on how to do that?
2022-05-28 14812, 2022
lucifer
we could probably add a comment on the table in postgres, with the description of various parameters the data was generated on.
2022-05-28 14821, 2022
mayhem
or do we make a new dataset hoster query for each with the description properly filled out?
2022-05-28 14828, 2022
lucifer
we already had that last time, no?
2022-05-28 14840, 2022
mayhem
a bit more work, but then the end result is available to all
2022-05-28 14845, 2022
lucifer
specify the table name and it'll fetch the data from that table.
2022-05-28 14809, 2022
mayhem
yes, but we didn't have descriptions for each of the tables.
2022-05-28 14832, 2022
mayhem
I suppose something like a google doc with table definitions and how they were generated could work
2022-05-28 14847, 2022
lucifer
i think we could make 2-3 fields in 1 query and name our tables in a way so that the table name can be generated from the params. then have a general description of various params on the same page.
2022-05-28 14846, 2022
mayhem
clever, I like it
2022-05-28 14852, 2022
lucifer
yes that'll work too. if we want to experiment with how we define sessions or other parts of the algorithm then it makes more sense to do it that way.
2022-05-28 14809, 2022
lucifer
but if we are going to only change params then this table name idea should do
2022-05-28 14818, 2022
lucifer
(params as in only changing threshold, lookahead, session duration but keeping the algorithm always fixed)
2022-05-28 14830, 2022
mayhem
then lets do the doc, because we will need to change the alg too
2022-05-28 14844, 2022
lucifer
makes sense
2022-05-28 14828, 2022
MRiddickW joined the channel
2022-05-28 14806, 2022
lucifer
for sessions, we discussed 30 mins (configurable) of continuous listening iirc. i am wondering how to define it, is it the same as checking the difference between the timestamps of two listens is less than 30 mins?
2022-05-28 14819, 2022
mayhem
yes, that is a decent first order approximation.
2022-05-28 14836, 2022
mayhem
a better one would be to take the duration of the last track into account.
2022-05-28 14817, 2022
lucifer
i see, we don't have it in spark dumps so we'll need to import MB recordings/release dump for that. let's start with the approximation then later improve.
I really appreciate how each album has its type shown. makes loads of sense.
2022-05-28 14817, 2022
chinmay
Yes, that was the last thing that I thought of while designing the release card
2022-05-28 14819, 2022
mayhem
I think "Beautify releases" -> "only show releases with coverart" would be more clear.
2022-05-28 14821, 2022
chinmay
Did you like the sidebar filters? No more dropdowns
2022-05-28 14841, 2022
mayhem
yes, but clearly it need an "all" option, no?
2022-05-28 14813, 2022
chinmay
Yes, the "all" option is the default option.
2022-05-28 14813, 2022
chinmay
Like in the first mockup.
2022-05-28 14813, 2022
chinmay
They'll only get filtered out as you start selecting the release types. In the 2nd shot, you can see that I have selected Albums and EPs only, and only that's filtered out as you can see in the release type chips of the cards..
2022-05-28 14858, 2022
chinmay
Yes, the "beauty releases" -> "only show releases with cover arts" can be done
2022-05-28 14820, 2022
mayhem
ahh , I see, ok.
2022-05-28 14837, 2022
chinmay
Yeah, you can select and deselect multiple release types if you wish. And the "clear all" button on top will deselect all of the filters
