Coming on April 1, there will be an undergraduate research symposium at Georgia Tech, with opportunities for both presenting at poster sessions and a 20 minute oral presentation. Part of the application for the presentation is a 250-word abstract of the research thus far, so this was the first time that I’ve had the chance (or had a good reason to) write more about the project. We have recommendations working great now, and are now getting to increasing the size of our music database from 500 tracks to roughly 1700. Soon we’ll also have tempo incorporated into the recommendations, which we think will be a good discriminating feature for tracks. It’s still in the early stages of customizing the CBR algorithm to our specific body of music (Indian music) so there are a lot more improvements to make.
What’s been holding me up recently is unicode text in Python 2.4.4. There are all sorts of funky characters in some of the tracks we’re using, both for filenames and id3 tags. For getting tracks into the databse, we try to have artist, album, year, and filepath. Since filepath is often a function of artist, album, and track number, it is filled with funky characters too. I’m in the process of debugging to figure out what’s going on, and am experimenting with the unicode method, bash language settings, python language settings, and vim language settings in ways I never have before. Hopefully I’ll be able to post my fix soon!
Post a Comment