Andrew’s Status Report 2/8

This week was mostly finalizing the design and preparing for the actual building and coding. I worked on taking in feedbacks from Proposal and deciding on the final design. Then I searched for appropriate parts to use for the design. Then I realized that there was an inventory that we can use to borrow parts. So I checked the list and found that there existed lots of Raspberry Pis that we could use. Unfortunately, there wasn’t an Arduino.

Our goal this week was to purchase parts and do some research, so I can we are on track. Next week, I need to start coding the motor control logic for our dispenser.

Martin’s Status Report for 2/8

Personally for me, after I received some feedback on the proposal presentation, I shared my thoughts with the team and we managed to have some constructive discussion. 

  1. Need to have Arduino in addition to Raspberry Pi?

A: Utilizing arduino along with raspberry pi will further empower Raspberry Pi by sharing workload and reducing the bottleneck.

  1. 99% accuracy card detection is not enough

A: We definitely agreed upon this and we also thought it wouldn’t be too hard to make the accuracy 100%, as there are only 52 cards for the model to learn, which wouldn’t be too complex.

  1. Using resistive sensor for player input (player move)?

A: We reached the conclusion to ultimately conform to this suggestion and embrace a resistive sensor for the “check” move. Furthermore, for other moves, we slightly changed our approach and are trying to attach a camera on the dealer system which could track the player’s motion and identify if it’s a “all-in”, “raise”, or “fold”

Created & Prepared for the proposal presentation!

Our team and my own progress is on schedule, where we discussed and finalized the parts to buy and submit purchase orders.

By next week, my goal is to start learning how to make object detection model to be functional on a raspberry pi by referring to online tutorials.