Team Status Report for 10/5

Team Status Report for 10/5

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 that could jeopardize the success of the project is our ability to determine the usage of a piece of clothing(formal, casual, business casual). Our own model & the pretrained ResNet model both struggle to classify the usage and we believe this is due to the usage being less correlated with the image data (array of pixel values) and more determined by societal standards. This is discussed more in Alanis’ section. We have defined two possible ways of managing this risk—we thought about reverse google image searching the image and webscraping the formality, or, classifying the usage ourselves (with a low accuracy) and then having the user confirm. We are leaning towards having the user confirm but will concretely pick one of the solutions after discussing with an advisor on Monday.

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?

We will have changes to our block diagram and system specification once we pick one of the two alternative approaches defined in the section above. Since we will probably end up having the user confirm the usage type, our use-case requirements will likely lower for the usage classification accuracy and we will add some type of UI to allow the user to confirm/edit the usage type to our frontend, but everything else will stay the same.

Provide an updated schedule if changes have occurred.

Our schedule has not changed. 

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

Photos of our progress are located in our individual status reports.

Leave a Reply

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