The biggest risk is the same as it has been the past two weeks and that is the integration of the Jetson and the CV code. The bluetooth connection between the Jetson and the game has not been set up yet, but Henry is going to try to get that done tomorrow, and Logan should have the CV code done by Monday. However, we have a new contingency plan in case we are unable to integrate the CV code. In this case, we would make the game similar to Wii Sports Tennis, where the paddle will follow the ball automatically and the game then becomes more timing and swing-type oriented.
As mentioned in Henry and William’s report, the biggest change to the system is how much the game is going to depend on the data inputs of the Jetson and rPi. As of last week, the plan was to set the orientation and position of the paddle in the game with the orientation and position data from the sensors. The problem with this is that is that we worried about the possibilities of lag and having sudden movements not be registered. We also ran into the problem of determining the velocity of the ball after it has been hit with a paddle because of the inaccurate velocity deductions from the IMU. To solve both of these problems, we decided to simplify the game to only read the data from the rPi and Jetson during a specific time interval after the ball hits the table and using this data to determine what type of swing a player is performing from a set of predefined swing types. Once a swing type is determined, it triggers an animation that Henry has already programmed and if the ball collides with the paddle, the paddle adds a velocity vector to the ball based on the swing type.
The biggest goals for next week are the refine the graphics, integrate the rPi and Jetson with the game, and finish fabrication of the paddles. We have a lighter workload next week compared to this week, but we still have a bit of catching up to do to produce a quality final product.