This week, we worked on finishing up the individual parts of our assignments that needed to be completed before we can reach MVP. For George, this meant getting the game to read the hits from the drum apparatus and the JSON from the beat mapper. For Stephen, this meant getting the drum module prototype into a functional state and sending its hit information to the game code in a way that was readable. For Shreya, this meant finishing up the beat tracker and working on sending the beat information to the game code to be integrated.
Ideally, we should be able to hit MVP in the coming week. These components are mostly finished and this weekend, we should be finishing up the integration as well.
We have several challenges/concerns over the next week:
- Scheduling – if integration is not finished this weekend, we may push our MVP to Friday of this week instead of Monday. This is not a large issue because MVP would suggest most of our game is done. The gantt chart does not need to be updated yet, but it may need to be next week if we do not meet our deadline.
- Accuracy of the beat tracker – because Librosa (the Python standard) is not necessarily as reliable as we originally believed, the accuracy of the beat tracker is still unknown. Shreya’s blog post has more details on the specific problem. However, if it is not as accurate as we need, there will need to be more specific time in testing and tweaking to ensure we get the needed results.