Author: rlin2

• The most significant risk right now is bringing all the parts together. Especially with constructing the hardware, we have hit many situations similar to deadlock in real life. For example, we want to test out a component by attaching it to our rack, but then attaching to the rack is permanent so we want to test the component. This has slowed down a bit of our final parts list compilation. We plan to work dedicate most of our time in testing our components as well as possible next week. As for contingency plans, plan to be very flexible on researching and ordering new and different components in the event that our existing items do not work out.
• There are no changes to the existing design at this time
• Progress on the software has been a bit slow due to some unexpected business, but a countdown has been added to facial recognition to give the user some time to prepare themselves to get scanned, and a way to register new faces is currently in the works.

Current progress on the rack!

 

• A was written by Ryan Lin, B was written by Doreen Valmyr and C was written by Surafel Tsadik.

Part A: Our product solution is universal across global factors. There really isn’t specific skill or knowledge on how to use our system because we designed the system to be easy to use with limited user interaction. People all over the world go to events and need their items to be stored quickly and securely. One possible way that our product solution may not work with global factors is if our implementation is not all-encompassing. For example, faces in different countries around the world will look different and will be a challenge for our facial recognition system.

Part B: Our innovative product streamlines the often cumbersome process of checking in and retrieving personal belongings, particularly at events attended by large crowds. By leveraging facial recognition technology integrated with a physical coat rack system, individuals can swiftly deposit and retrieve their items, freeing up valuable time for social interaction. Crucially, our solution is designed to be inclusive and culturally sensitive, accommodating users from diverse backgrounds and belief systems. With no barriers to access, individuals of any cultural or religious affiliations can seamlessly utilize our product at events. Additionally, the non-invasive nature of our technology ensures widespread acceptance, as it simply relies on facial recognition for item storage, devoid of any controversial features.

Part C: Currently, many coat checks use a physical ticket system to store and retrieve items. Paper is usually used to print these tickets, and if the event has a large audience a lot of paper will be used and later thrown away. With our system, it will eliminate the need for physical tickets, meaning no more paper needs to be used to print said tickets. Less paper wasted means a positive impact on tree preservation, decreasing the number of trees we need to cut down to produce the paper that goes into the physical tickets.

• We still have some hardware risks for our project. We need to create or buy a gear that is strong enough to rotate our rack. Also, though some testing has been done on some components, other components cannot be tested due to them not being ordered or delivered yet. Secondly, all team members have a midterm on Wednesday next week, which could slow down some progress. To mitigate this risk, we plan to double down on work immediately after the exams. This allows the same amount of work to be done while also allowing us to wait for components.
• Overall, there weren’t any big changes to the design, except for some minor adjustments in the hardware design of the rack during construction. For example, changing the number of legs from 3 to 4 or reducing the height of some sections. The change just simplified some construction work. The schedule has not changed at all though.
• We tested out the load cells with an Arduino and it works exactly as expected
• We are almost done with the non-electronic component of the rack
• Shout out to Justin from TechSpark
• Faces are being recognized live with manually inputted images, next is to add new faces to the model through a video stream

• One of the risks is access to machines in TechSpark for the construction of our hardware rack. This risk is lessened from last weak because of some design changes. We plan to CNC cut sheets of plywood and join them with glue instead of cutting wood with other machines and screwing them together. This reduces the amount of training or oversight needed because a CNC machine is relatively easier to use. We have also found some potential people with training to help us with using the machine.
• If we are not able to use the CNC machine, our contingency plan is to use the TechSpark provided quarter-inch plywood and the laser cutters, because those machines do not require formal training to use.
• Some of the ordered components may not work, so we ordered spares and plan to test them out within the next week.
• The only thing that really changed was the design of our hardware rack after going into the specifics on how to handle weight imbalance and robustness.
• Current rack design!

• A was written by Ryan Lin, B was written by Doreen Valmyr and C was written by Surafel Tsadik.

Part A: This product solution in general does not apply to the need of public health, safety, and welfare.  However, there may be some small factors of our project that contributes to this topic. For example, perhaps the removal of a ticket system and the ease of checking in their personal items brings a sense of ease to people that may be stressed attending an event. Our product also allows customers to feel safe in knowing that their items are kept track of and kept in a specific position on our item stand. In terms of meeting physical safety and public health there isn’t much of a connection. This product also doesn’t provides for the basic needs of people because it is primarily used for events that usually don’t support people’s basic needs.

Part B: Our facial recognition algorithm will use tools like OpenCV to characterize and distinguish different faces, so things involving a person’s social group, whether cultural, political, or economic, will not be taken into consideration when checking in or checking out a user. In addition to this, our product can be used in a variety of social contexts and within all types of social gatherings that necessitate a attendee having to set aside particular personal items when attending that particular event. Without strict rules being set on the items that can be on the rack, simply the assumption that it will mostly be used for coats, users will not be limited to the items they can set aside, but mostly the weights of those items. As a result, users are able use our product for their required social gatherings without limitations.

Part C: Coat checks at large events currently puts too much responsibility on the attendees. Attendees usually have to keep track of a ticket/number throughout the event, which adds a whole layer of complexity during a time when attendees may not want a complex experience (a more relaxed event, a very formal event). It becomes worse when people begin to lose/forget their identifier, leading to a messy (and potentially malicious) retrieval of checked-in coats. Our product eliminates the need for external identifiers like a ticket or number as you can check in using your face (which everyone will always have). Without the need to keep track of an external identifier, attendees can focus more on the event they’re attending and have a seamless process of retrieving their coats.