Author: gcarom

Geronimo’s Status Report February 21

This week I made some great progress on the UI of the app. I worked on setting up the different data separation for Rally and Serving. Demonstrating how the resulting data would show up after processing. I also updated the 2d grid into a 3d grid to demonstrate the swing paths.

Progress is currently on schedule and I do not have any blockers.

This coming week I hope to keep updating the UI as needed and start working on creating calculations that will be used with the incoming data to make predictions on some of the statistics.

Geronimo’s Status Report February 14

This week I made some progress on the UI of the app. I also read through two research papers of similar projects that professor Quinn provided us. I mainly focused on the serve path part of the UI and getting more adept and understanding how to use the JS and React frameworks. I found a great resource that provides a lot of help and guidance for creating the app.

(I had a video going through the UI but the file was too large)

My progress is currently on schedule

Next week I hope to have finalized the base UI set up with some false data as well so I can start to test out how it will look properly once we have data being streamed in.

Team Status Report for 02/07/2026

We think that one of the most significant risks would be if parts have long lead times or if the ordering process takes a super long time. We are mitigating this by choosing parts that are in stock on DigiKey, and also finding alternatives on Amazon where applicable. If we run into serious issues here, we can always choose different hardware components to prototype with and then switch over to the actual components we want to use for our final product later on. It is important to get data flowing asap so we can begin some initial testing, data characterization, and data analysis. We plan to order parts early this coming week, hopefully get them in by the end of the week or early next week, and have a working hardware setup by the end of next week.

 

Some metrics could not be as easy to read as we might think, and could lead to metric calculations being poor. These risks are being managed by having the base idea for the metrics be more general or by having range values instead of giving specific values. As a contingency, we have a few other metrics that we could try to calculate instead.

No significant changes have been made, we are still working on choosing the specific hardware components, but no major changes, just part selection. 

 

No schedule updates at the moment. Still following the original schedule.

Basic UI setup has started: