Posted on

Wonho’s Status Report for 2/12

This week I worked on the proposal presentations slides with my team. The tasks were divided up into more specific and modular tasks so that we would be able to plan ahead accordingly. This also helped us create a more detailed schedule that allowed multiple parts of the project to be developed simultaneously while the team works together.

We also had internal discussions to determine what direction we want to take regarding the software language and we determined that C++ would be more useful after receiving some feedback after our presentation.

In terms of the hardware aspect of the project, I was able to secure the Jetson Xavier NX as well as an 12MP Arducam that is compatible with the Xavier. Next week, I’ll be researching the specific materials we need for the smart mirror and plan on putting in the order forms for the one-way mirror and a monitor for our smart mirror display.

Posted on

Yun’s Status Report for 2/12

I personally worked on improving the proposal presentation slides, revising the schedule (Gantt chart), and doing more research on which software languages and tools to use for the implementations. We realized that each modular task was in larger pieces than we wanted; thus, I worked on making tasks more modular so that each task can be completed in about a week.

My team has been working on specifying details for design choices by considering which languages to use to meet latency requirements and how the user experience would be. I believe that the team is on track in accordance with the planned schedule now. However, it is early in the project, so I am planning to work ahead if time allows, so that we can have some buffer time in the future when unexpected situations that are not planned occur.

In the following week, I am planning to do some research on finding resources for outfit color matching, and ideate what kind of format we would want to store such data. In addition, if time allows, I will also be studying app development briefly.

Posted on

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.

Posted on

Jeremy’s Status Report for 2/12

This week I was mostly working on our team’s proposal presentation slides. Our project is still in the early stages, so I also went ahead and polished some of our preliminary ideas so that we could design our project in a much more modular fashion.

This includes: attaching white LED lights around our mirror to fix the variable of minimizing shadows for each of our users, being able to analyze solid colors, having a tag to each of the clothes that the user fills out to make it easier to grab the correct matching clothes from the database.

In doing so, we were able to set an MVP for our project. I believe our project is on schedule, but we should be aware of the possible complications that could come from a new tech stack. Next week, I hope to be able to test out some of the software tools that our team is planning to use for the color detection and come up with an overall design strategy for our project by deciding on which tools we plan to utilize.