As of now our team sees no greatly significant risks to achieving our MVP, having not really changed since last week. We still have a couple potential blockers or issues to tackle in the next weeks. Firstly is the design of the case for our embedded system. We are currently iterating on different approaches for attaching our system to the handle of the racket without impeding on the user’s experience. This may or may not take longer than 3 weeks to get in an acceptable range. Secondly is designing the ML pipeline for this system. We have done substantial outside research to give us confidence that our design can succeed. However, we will undoubtedly need to make changes to some parameters as is reasonable with our own hardware and data flow.
In order to mitigate risk 1: we will be constantly iterating our design to minimize user impact. We will be reaching out to collegiate tennis players that we know in order to get feedback on our ideas and implementation as we go.
In order to mitigate risk 2: we will be working on creating a baseline pipeline that works structurally the same but with less expected accuracy. We want to uncover unexpected issues as quickly as possible to make needed changes. We will additionally be doing testing and verification of our data flow to ensure data integrity as it goes through our ML pipeline. This will be pivotal in ensuring accurate results when testing the ML.
We made successful improvements to the application to make the user experience better. This weeks work largely involved continuing to improve the things we started last week. We further streamlined data capture this week for example. Next week we will be connecting all parts of the system including the application to be ready for interim demo. We should have surface level data analytics ready and swing path visualization for the demo, including our 3rd iteration of the physical attachment.
