Team Status Report for 11/2

Integration of the glasses and the web app is a risk, we plan to have the two raspberry pis communicate via wifi, but it may be more involved or take longer to implement than we expect. The contingency plan for the integration is to host the web app in AWS (AWS Amplify or EC2) and use HTTP calls for communication between the web app and the raspberry pi pico w on the glasses. No schedule changes.

Team Status Report for 10/26

What are the most significant risks that could jeopardize the success of theproject? How are these risks being managed? What contingency plans are ready?

Latency continues to be a risk, HTTP requests with the web app is not a big concern but algorithmic processing may be slow, this is mitigated by the tools we are using, which are efficient, and the categorization of data so that it can be more easily queried.

Were any changes made to the existing design of the system (requirements,block diagram, system spec, etc)? Why was this change necessary, what costsdoes the change incur, and how will these costs be mitigated going forward?

No changes.

Team Status Report for 10/20

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 main risk continues to be latency, although so far it does not seem to be violating our requirements, with the voice commands and the web app latencies being below our thresholds right now.

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?

No changes

Part A (written by Kayla)

Hey CHEF! is designed to be user-friendly and provide convenient solutions to ease the cooking process for anyone who uses it. Aimed to help beginner and home cooks, Hey CHEF! can encourage people to cook more often than eat out and reduce food waste overall via custom recipe recommendations given the user’s available ingredients. Another crucial concern that Hey CHEF! helps to address is cleanliness in the kitchen, as the hands-free aspect of the product significantly reduces cross-contamination while cooking.

Part B (written by Alena)

Hey CHEF is designed to cater to a wide range of cultural factors by offering a solution that embraces diverse recipes and allows users to explore recipes from different cultural backgrounds. The recipe recommendation system is built to recommend recipes from different cultures that may use staple ingredients  in unique ways that users may not be aware of. A feature can be implemented for Hey CHEF such that it also can suggest culturally appropriate recipes that reflect the user’s culinary heritage, helping them prepare meals that align with their traditional cooking methods while also offering new options. Furthermore, by allowing users to input their own custom recipes and dietary preferences, the assistant can accommodate culturally specific diets, such as vegetarian, halal, or kosher cooking.

Part C (written by Michelle)

Hey CHEF is aimed to be a resource friendly cooking assistant with a goal to utilize items that users already have in their kitchen. It is often hard to utilize the last bits of food left in the refrigerator, and with so many recipes out there requiring specific ingredients, it may be hard to cook with what one has. We hope the Hey CHEF will minimize food waste in a user’s home.

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 biggest risk that could jeopardize the success of our project is the communication between the Pi and the pico, and also the integration of all the subcomponents after they are implemented individually. We will mitigate these risks by focusing on integration testing after initial unit testing of each component. For example, we’ll need to make sure that the code for microphone input processing works seamlessly with the initial voice command prototype.

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 decided to host the website on a Raspberry Pi instead of on AWS just to make communication between the Pi and the pico easier. Also, we’ve lowered our total voice command latency requirement from 8 seconds (4 sec input, 4 sec output) to 6 seconds (4 sec input, 2 sec output), because the voice command library we are using supports a faster response time.

Team Status Report for 9/28

What are the most significant risks that could jeopardize the success of theproject? How are these risks being managed? What contingency plans are ready?

Latency is a main concern for the project, as latency significantly affects user experience, which is a priority for the project’s success. We are mitigating this risk by hosting the web app on a Raspberry Pi which will communicate with the Raspberry Pi Pico W on the glasses via local network, which is lower latency than communication over the Internet if we were to host in AWS. We are also prototyping with the voice commands and believe they will be within expected latency bounds. Contingency plans are the same in that we will look into larger, more powerful hardware for the glasses.

Were any changes made to the existing design of the system (requirements,block diagram, system spec, etc)? Why was this change necessary, what costsdoes the change incur, and how will these costs be mitigated going forward?

No design changes and no changes to the schedule.

 

Part A (written by Kayla)

As a hands-free cooking assistant, our project is designed to ease the cooking process as well as improve cleanliness in users’ kitchens. By helping to make recipes more readily accessible with clear step-by-step guidance, our project can enable and encourage more people to cook for themselves and their families, which can lead to people having healthier meals, saving money by eating out less, and living a more sustainable and fulfilling lifestyle overall. Additionally, the hands-free nature of the product helps to reduce contamination between foods, handheld devices, and potentially other surfaces maintaining a cleaner workspace and cooking environment. Because the product is targeted mainly toward home or amateur cooks, these areas are often peoples’ own kitchens in their everyday living spaces, so improved cleanliness in these areas can also be beneficial for peoples’ overall health.

Part B: (written by Alena)

“Hey CHEF!” addresses a growing societal trend of convenience, multitasking, and technological integration in daily life. As we increasingly adopt busy lifestyles, the ability to prepare meals efficiently while minimizing the need for manual interaction with devices can enhance time management and also reduce chaos in the kitchen. Additionally, the product can cater to a range of cultural cuisines and dietary preferences, encouraging inclusivity by allowing users from various backgrounds to explore different recipes and share them socially. By recommending recipes based on what users already have, it encourages resourcefulness and economic mindfulness, while also exposing users to new recipes that they may not have heard of.

Part C: (written by Michelle)

We believe that “Hey CHEF!” will be a product desired by consumers around the world. For as long as the need for food exists, cooking will too. Hence, tools that facilitate cook/prep time will always be in demand. “Hey CHEF!” aims to utilize the desire to cook with the desire to make it an easier, simplified process. To make a product that has economic potential, we aim to make the glasses lightweight, cost-friendly, and modular, making production on a larger scale simple. The glasses will reach a large audience by eventually allowing for recipe addition, and the easy-to-use interface will allow a variety of people of different skill levels to use our product.

Team Status Report for 9/21

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 biggest risk that could jeopardize the success of our project is the unknown latency we may experience between sub-modules of our design. We will mitigate these risks by researching multiple options for the best way to communicate from our Raspberry Pi Pico W to our web server, and the best ways to communicate within the web server. In the event that we cannot find a suitable solution, we may look into better hardware while sacrificing some size/weight constraints.

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?

  • There were no changes made to the existing design of the system.