Team Status Report 2/8

At this point, we think our ambition has pushed us to have diverse features, each being quite challenging. Even though we got rid of many components after receiving feedback from the initial meeting, since we strived for seamless integration and smooth gameplay, we ended up including new components, such as player motion detection and resistive sensor. As the complexity was added, we’re trying to split work as efficiently as possible and also start early. In case we’re short of resources(time), we have a set of features that we’re thinking of that are the minimum requirements of our project. As such, if we end up having short of time, we will dispose of those ideas and reinforce our already-implemented features.

We opened the possibility of using a screen as output for communicating with the players. We thought that it may be easier to implement than an audio output. We also narrowed down to work with 4 players at maximum (not 8), which avoid us from struggling with blind spot for using a display as our communication. 

Based on the feedback we received during the presentation, we thought that pressing buttons for check/raise/fold could be tiresome to the players. We’ve come closer to the idea of attaching an additional camera to the machine for detecting raise/fold and putting resistive sensors for detecting checks (double tapping). 

No change in schedule yet. Everything is on track.

Justin’s Status Report 2/8

Based on the feedback we received during the presentation, I thought that pressing buttons for check/raise/fold could be tiresome to the players. After discussing with my teammates, I’ve come closer to the idea of attaching an additional camera to the machine for detecting raise/fold and putting resistive sensors for detecting checks (double tapping). The resistive sensors I decided to use are Interlink Electronics FSR 402 Round (8.9 dollars each). The camera that will be used is the Raspberry Pi Camera module 3 (26.26 dollars).

Large, zoomable image of Raspberry Pi Camera 3 SC0872. 1 of 8

 

MFG_34-00015

Interlink Electronics FSR 402 Round

  • 0.5″ (12.7mm) diameter sensing area
  • Perfect for tap detection
  • Very durable (10+ million actuations)
  • Fast response time (<1ms)

I have personally spent time researching what could be improved in our user interface. Besides attending group presentations (4 hours), I spent about 6 hours researching and planning. I spent around 2 hours on group meetings.

My schedule is not behind. The schedule for this week was only to prepare for the presentation and research. The planning and researching part has become more clear and decisive after getting the feedback from the presentation. The plan for next week will be to focus on actually getting started on implementing. (code for detecting hand motions)

.

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.