What are the most significant risks that could jeopardize the success of the project? How are these risks being managed? What contingency plans are ready?
The main risks to the project are the complexity of each subsystem. For the music scanning element, due to the diversity and complexity of sheet music, it is possible that the accuracy of this system (which is already a challenge to piece together using the existing open source libraries) is not sufficient to meet the overall needs of our system. The contingency is to use MIDI inputs instead of a PDF which have a well defined library in multiple languages. For the algorithm, the risk is dealing with similar edge cases. Music is inherently subjective but focusing on beginner and intermediate musicians means the algorithm can be more strict to focus on more rigid timing than would be needed for more advanced musicians who already posses the skill and play with tempo (and cause more musical variation difficult to process). Overall, once a basic iteration is developed, it will simply continue to be optimized as the semester continues. Lastly, the audio processing itself seems to be challenged by real-time input. Since real-time DSP is its own challenge, the starting place to mitigate risk is to use pre-recorded audio files as the initial input. Should real-time fail to be successful, musicians could still upload their recordings into the system and receive feedback. It would be an extra step on the part of the user, but still work as a functional system.
Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?
No changes since last week.
Provide an updated schedule if changes have occurred.
No schedule changes.
Our current Gantt Chart: https://docs.google.com/spreadsheets/d/1w5bFU-YbyqIHIdWTXLG7f4z9ygEWPRjl9v7tBey53n8/edit?usp=sharing