The first part of this week was dedicated to the proposal presentation. Together, we determined the user requirements and the design requirements, as well as general ideas for implementation. Our presentation was given on Monday. We have also attached the slide deck to the website for perusal. Overall, as long as we can maintain some closeness to schedule, we feel that this is a viable project.
Here’s a sketch of our current project design:
Currently, we are on schedule to complete our design by the deadline with one week of slack time. In the next week, we are looking to begin to determine the final packages and equipment we will be using for this project for all three portions of the project. There are several risks associated with this project that we are looking to mitigate at the moment:
- Determining which packages we need to use for beat tracking. With our latency constraints, we are worried about the usage of base packages like numpy to iterate through the song, which was explained more in the personal sections.
- Slow delivery of the hardware components. Given that they are currently expected to arrive on 2/17 (with 2-day shipping), there will only be 2 days before the next status update to assess the feasibility of our hardware plans and decide if we need to make any changes going forward. As such, we’ve ordered several different piezoresistive sensors as a precaution against this, as if our currently targeted sensor is not satisfactory for our needs, we’ll have a backup set of piezoresistors to allow us to continue testing while we spec out a preferable alternative (assuming the backups are also not satisfactory).
No changes have occurred to the design project as of yet. The schedule will remain consistent with the next weeks being dedicated to determining if our individual solutions are viable as well as determining the final packages we want to use in our design project.
Here is the current version of our Gantt chart:
