Team Status Report for 04/1

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 most significant risk as of right now is linking the backend PDA with the front end web application. This has been accomplished to the extent that we are able to display pitches from the users real time input on our web app frontend, but a lot more work needs to be done. 

We will need to preprocess the signals more to cut out invalid pitches (i.e. < 100 Hz and >1000Hz), figure out a good way to splice the incoming .wav files, and test that the integration provides timely real time feedback. 

These risks are being managed by taking integration with our PDA and frontend slowly with thorough testing before adding in a complicated scoring algorithm or more advanced graphics to display the pitches. By taking this integration a step at a time, we can pinpoint failures more easily and correct them as they come up.

An obvious contingency plan for us is having the pitch detection and scoring algorithms run on the full user audio after it has been recorded. 

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 additional changes have been made to our design this week.

This is also the place to put some photos of your progress or to brag about a component you got working.

A huge accomplishment for us this week was integrating our frontend to our backend and displaying the users pitches in Hz on the screen!

Additionally, Anna spent a lot of time on figuring out how the user pitch would display on screen and was able to make a lovely demo of these graphics!

And Anita has been working hard on writing a scoring/feedback algorithm to integrate with our PDA and frontend!

Here is our updated Gantt Chart.