Team Status Report for 2/12

The most significant risks that we came across over the past few weeks were figuring out the focus of our project and how exactly we would be able to recommend outfits to the user in a suitable fashion. We have managed both risks by centralizing our project on outfit recommendations rather than our original plan to include heart rate monitors and daily schedule reminders on our mirror. We have also decided to push through with the idea of having users take pictures of their own clothes and input it into a database which would then be used for outfit recommendations based on a color wheel. This makes the overall project much more straightforward and simple.

We have made some changes to our use-case requirements and system spec after our project proposal presentation. Using the students’ feedback, we decided to lower the time it takes for and outfit recommendation from 10s to 4s. This change was necessary and viable because we were successfully able to acquire the Jetson Xavier and because we realized that 10s may be too long to maintain the user’s attention. We have also decided to switch from using OpenCV with Python to C++. This change was necessary because our team realized that the documentation available is similar for both languages and C++ is much faster in terms of runtime which will directly help our use case requirement of fast outfit recommendations.

We have also started to think about how to connect our mobile app to the mirror for turning on/off the mirror and we realized that the Jetson Xavier that we received from the 18-500 inventory already has a built-in WIFI+BT chip that we can use which is very useful and saves us a lot of money and time.

Leave a Reply

Your email address will not be published. Required fields are marked *