#metabrainz

No zag :(

[listenbrainz-server] mayhem closed pull request #86: Docker nginx (master...docker-nginx) https://github.com/metabrainz/listenbrainz-serv...

Project listenbrainz-server build #100: SUCCESS in 1 min 8 sec: https://ci.metabrainz.org/job/listenbrainz-serv...

ruaok: whee, we got free schlager :D

ugh. that word stuffed into an english contexts sounds too much like a sexual disease. :)

Project acousticbrainz-server build #181: SUCCESS in 5 min 55 sec: https://ci.metabrainz.org/job/acousticbrainz-se...

Well, be happy it's just an auditory one then

Project listenbrainz-server build #101: SUCCESS in 1 min 15 sec: https://ci.metabrainz.org/job/listenbrainz-serv...

ruaok: QuoraUK: away until Monday since Thursday, just so you know!

ok.

I'll be away from monday - monday, just so you know. :)

hmm. did I have anything to talk to you about, ruaok ?

how am I supposed to know that? :)

electromatic waves

perhaps

yo que sé

thats the next festival.

hah, so it is

this is one is nordic hippies.

if everything goes according to plan we'll have full dataset + evaluation stuff working at the end of the month

nice. did anyone enter the challenge you posted?

me? I didn't post anything :)

but it sounds like we have a bunch currently:

we actually need to run the models. I should do that

also, we're waiting on my code for the actual evaluation, so we won't know results until that's done

that's really cool. it is nice to have a vision become reality.

not bad progress for under 2 years of progress. :)

yeah. there's a small handful of things that need to come together to make this easier to use

but it's definitely happening

I really want to get search going, really badly

now for nearly 2 years. :)

and Gentlecat wants to get feedback from the website going - "This feature is wrong, it should be x"

sigh

yeah

that is really necessary, yes.

I can't wait for 6-12 months past these things working when the data shows concrete improvements

unfortunately we still have no phd students working on it

that's my real dream

well, anyone, really

there was one, yes? that person done, now?

ruaok: Speaking of you being away, I replied to your "mattress" mail, but didn't get a reply back.

well, his work isn't "extend AB to do x"

it's "do this thing, which can be integrated into AB"

so I'll push to make sure the integration becomes a reality, but...

ah.

Freso: meh. the dsb.dk site is broken in chrome

Freso: my plan is roughly, this: Arrive at 15:30 at CPH, take the train to København H, hopefully meet you there, possibly shop for a few things, then take the train to Rødvig

I thought that was fixed.

armalcolite: it also occurs to me that I have no idea how to start using the api_compat branch. :)

ruaok: You'll want to use http://www.rejseplanen.dk/ rather than dsb.dlk

* dsb.dk

thx

you ok meeting me at københavn H with the mattress?

Sure. :) Valby would obviously be best for me (I live less than 1 km away), but Cph H is definitely doable and workable too.

Oh, and also re: a comment on your review at a meeting some weeks ago: "Each organization receives $500 USD per accepted student no matter whether the student passes or fails." So the two students we have had drop out should not impact what the org. gets from Google for money, AFAICT.

I was more referring to the student money going unused.

if a student drops out that is $5k that wasn't pulled out of Google's pocket. :)

Ah. Right.

ok, mbspotify seems to be working with docker too now

Gentlecat: I'm going to add a datasets section to /admin

for now it'll show the same stuff as the dataset list page, and have 3 options: mark from running->pedning, mark running->failed, promote finished to evaluation status

promoting to evaluation will compute highlevel against them and store in a temporary highlevel table

from this, we can do the cross-collection evaluation which you need

is that actually supported by hl extractor?

kind of

it is in https://github.com/metabrainz/acousticbrainz-se...

but that branch is very out of date

but I have a better way to do it, it shouldn't be much work to make the change from how it is currently

the difference is that I wanted to create a new temporary highlevel table per model to evaluate

now that we have the `model` table and `model.status`, we can add a new model based off an evaluation job, and keep track of the different highlevel files

I'll try and write it up in a ticket for you to give a look at it, if you want

I wonder if it makes sense to be able to first compute the lowlevel files that are a part of the evaluation set

that way we can do the evaluation more quickly, instead of having to wait for all 3 million to finish

Project acousticbrainz-server build #182: SUCCESS in 5 min 59 sec: https://ci.metabrainz.org/job/acousticbrainz-se...

reosarevok: not quite a single flag...there are a few hardcoded artist checks throughout the code

and I guess we might want to port the "rename credits" thing that artist merges have

maybe village-sized difficulty if those metaphors still hold

I liked the rock ones better

easier to stub your toe on?

Project acousticbrainz-server build #183: SUCCESS in 5 min 44 sec: https://ci.metabrainz.org/job/acousticbrainz-se...

Gentlecat: I got a really basic 'migrate' command working, which finds unapplied update files and runs them

currently only works for sql files, not python, and doesn't recover from sql errors

but seems OK for now

bitmap: Ping.

pong

Hi :)

oh, friday again. hi!

sorry I hadn't checked the code in a few days until now

Oh, that's fine.

Have a look whenever you find time. Though I've started working on the other dialog, on a separate branch.

I'll try to edit some stuff locally and see if I can fix that whitespace issue

good

the track one is starting to look fairly complete to me

I'll cc some other picard devs on the PR and see if they can take a look

I was thinking of reusing the `release_to_metadata` method from mbxml.py (https://github.com/metabrainz/picard/blob/maste...), so as to avoid writing a parsing method, but couldn't make it work till now.

Yeah. Sure.

ah, good idea, I hadn't thought of that

you have it working now though?

Nope. Not for release. I guess it wasn't meant for a release node from a release query. Rather for a release lookup through mbid. I am getting some attribute errors. But I think I can fix that.

I'll have to look more into it.

would it help to reuse those *_to_metadata functions in parse_tracks_from_xml?

our XML isn't very consistent between lookups and searches

ideally we have standard parsing code used everywhere but it might be tricky

Yes, it can be reused for tracks. But most of the information extracted is wasted. I'll try using it and see if it doesn't make much of a mess.

that's fine, it's not storing a lot of results in memory

Ok. I'll try that. See if I don't break things.

Another thing...

Should I be saving dialog state on pressing cancel (this includes advance query syntax, window size, and column sizes). As the "Load into Picard" button is disabled until an item is selected.

I would have the window and column sizes always persist (even across different tracks)

the advanced query syntax should persist anyway since it's using/modifying the actual setting, right?

Not if it's state is changed in dialog. If the user clicks cancel, it'll return to original state.

Hi all!

I work for the freemusic archive, we're really interested in checking out acousticbrainz in the FMA, just wanted to say hello

I guess the settings change should be reverted, since that's how the options dialog works

I would have the window/column sizes persist though since it doesn't make sense to cancel that

Umm. Ok. I'll do that.

the cancel button is canceling the form, not how it's displayed

people will resize things to how they like and expect that to stick