Skip to content

Meetings

Jonathan Wallach edited this page Jun 6, 2021 · 16 revisions

Meeting 1 (4/27), @ 12 PM:

Scrum master: Brendan

Agenda:

  • finish up set up of Git Hub
  • construct backlog of tasks as issues
  • assign firsts tasks for sprint
  • make sure everyone is clear on tasks and what needs to get done

Attendees:

Jonathan Wallach (Note Taker)

Brendan Corr

Michael Moschitto

Notes:

  1. We've established that the optimal use for our prediction model will involve allowing a user to directly link to their personal Spotify
  2. Created a backlog of ~30 issues
  3. Of these issues we have placed all set-up related tasks into the first sprint
  4. To assign these tasks to different team members we have reviewed each members strengths/weaknesses. Jonathan and Michael are both Computer Science majors so they will be handling tasks related to research / set up of Spotify API. Brendan will be handing tasks that are related to initial data cleaning / graphing.
  5. Brendan's tasks are reliant on the completion of tasks by Michael and Jonathan, which is important to be aware of for the sprint.
  6. While discussing tasks related to storing data we've decided that we should not create an SQL database, but rather just keep our data in a CSV file
  7. The GitHub link is now ready to be submitted and everyone is on the same page with tasks.

Meeting 2 (5/4), @ 12 PM:

Scrum master: Brendan

Agenda:

  • check in on progress of everyone's tasks
  • Identify any projected problems or changes original plan
  • work on troubling tasks together
  • make sure everyone is clear on what should be done by the end of the week

Attendees:

Jonathan Wallach

Brendan Corr

Michael Moschitto (note taker)

Notes

  1. Mike was able to finish up the ground work for much of the data pulling and spotipy API
  2. Everything looks set up on our git hub and everyone on the same page on pulling/pushing to git hub
  3. Figure out how to work in the genre of the song since it is not readily available on spotipy
  4. Jonathan took over task to figure that out while Mike and Brendan continue to work on visualizations and analysis of data
  5. Next steps to finish up the data exploration and make sure data is all in correct format for modeling
  6. If get that far, start to build model

Meeting 3 (5/16) @ 5:30 PM

Scrum master: Michael Moschitto

Agenda:

  • Review current state of project
  • Establish plan for moving forward

Attendees:

Jonathan Wallach (Note Taker)

Brendan Corr

Michael Moschitto

Notes:

  1. The spiderweb graphs for each mood looks as expected
  2. Random Forest model predicted song moods with 74% accuracy
  3. Could be beneficial to collect feature importance values (shuffle each column, see effect)
  4. Going to look into training a neural network to see if we can beat the accuracy of the random forest model
  5. It may be too difficult to add a recommended playlist directly to a user's playlist, so we may just have to output the songs to our UI

Meeting 4 (5/20) @1:00 PM

Scrum master: Michael Moschitto

Agenda:

  • Discuss challenges with neural network
  • Discuss goal for final deliverable

Attendees:

Jonathan Wallach (Note Taker)

Brendan Corr

Michael Moschitto

Notes:

  1. Original neural network is around 72% accuracy
  2. Struggles with indexing predictions
  3. Need a way for user to interact with what we create so that they can gather their song recommendations
  4. Still thinking a website is possible

Meeting 5 (5/25) @3:00 PM

Scrum master: Jonathan Wallach

Agenda:

  • Update on plan for final deliverable

Attendees:

Jonathan Wallach (Note Taker)

Brendan Corr

Michael Moschitto

Notes:

  1. There's a lot going on with lab/assignment deadlines and lots of remaining work to do for the write ups for the project
  2. As a result we may not be able to do the website
  3. Instead of website we can make a terminal interface
  4. Users can enter the mood they would like and we can output a list of songs.

Meeting 6 (5/27) @2:00 PM

Agenda:

  • Figure out what to do with neural network results

Attendees:

Jonathan Wallach (Note Taker)

Brendan Corr

Michael Moschitto

Notes:

  1. Our accuracy is not exactly as high as we'd like it to be
  2. Unfortunately not sure if we're realistically gonna be able to get it much higher
  3. This is because there is a lot of overlap in features for the different moods
  4. Listened to some songs to see how they were sounding
  5. Happy with state, think we're content with the state of predictions

Meeting 7 (5/29) @1:00 PM

Scrum master: Jonathan Wallach

Agenda:

  • Go over current state of neural network
  • Come up with a plan for handling which songs we will choose to recommend

Attendees:

Jonathan Wallach (Note Taker)

Brendan Corr

Michael Moschitto

Notes:

  1. Got neural network accuracy to 77%
  2. Even if a song has been identified as a certain mood, there are varying levels of each mood
  3. To handle this we can make our model output what percentage of each mood the song fit so that we can figure out which songs are the 'most' of their mood

Meeting 8 (5/30) @1:30 PM

Scrum master: Jonathan Wallach

Agenda:

  • Go over roles for final project

Attendees:

Jonathan Wallach (Note Taker)

Brendan Corr

Michael Moschitto

Notes:

How are we going to format final report?

  • Medium article, discussing findings and methods, but with larger emphasis on proposal for future work w/ callouts

Michael:

  • Format the notebook / python files
  • write about classifier / data eng
  • Challenges with model accuracy, getting our own data

Jonathan:

  • Future work and how we use turn this into a web/mobile application (why we didn't get to that)
  • Preliminary results and discussion of what they mean within context

Brendan:

  • Visualization and initial data exploration
  • Explain why we believe our training set is valid (GIGO)
  • Why we chose the classifiers we did <-- use stats
  • DO STATS