Team Status Report for 2/10

Team Status Report for 2/10

This week, we presented our Proposal Presentation to the class and received feedback. The overall feedback was positive, with constructive criticism to be addressed, such as the camera pole impacting the portability, and having different testing environments to make our CV algorithm more robust.

After the presentations, we focused on drilling down on the initial design as we prepare for the Design Presentation. For example, we started asking questions such as “what is the minimum torque that we need for the stepper motor?”, “How many frames of images can we capture in the ball’s trajectory, and is that enough to assess where the ball will land?” As we start to consider these questions, we are starting to have a specific technical requirements for the parts we will order.

We are also approaching individual subsystems with an iterative improvement in mind. For example, Mike will be focusing on making the website and communication protocol functioning first before jumping into Figma. Alex is starting with assumptions such as “no other objects moving except for the ball” to hone in the ball trajectory calculation algorithm first, then slowly remove the assumptions to perfect the ball landing detection. Seung Yun is considering the pros and cons of fish-line design and linear actuator design for the vertical aiming, and how quickly we can go from one design to the other in case the first one doesn’t pan out.

Leave a Reply

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