Team Status Report for February 24, 2024

Right now, our biggest risk that could jeopardize our project is not getting approval for our people counting module being set up in the U.C. gym. We are managing this risk by staying in contact with UC gym administrators, and in the case we have it rejected we have data that UC gym employees have given us access to that can be used to train a rough model. We also plan on relying on surveying people on the time they use the gym in the worst-case scenario.

 

After meeting with gym administrators this week, we have eliminated the camera system from our project. Our proposal for the system up for our people counting model was rejected.  We are currently waiting for approval from gym administrators with a new approach using two proximity sensors to count people entering the gym.  As of now, no costs have been incurred from this change.

 

Our schedule change is pending the approval of the two-sensor people counter from gym administrators. 

Derek’s Status Report for February 24, 2024

This week, I worked on specifying the details of the software implementation. More specifically, I decided on Flask to host our backend API and after further research, ditched MySQL as our database. I came to this decision because I realized that we did not need the database. Since historical occupancy data is only needed to make new predictions on occupancy, I plan on having a local machine (where our predictive model is) fetch occupancy data from the EC2 instance via hourly API call to Flask. This way, there is no need to query from the database and information can be directly sent to our local machine. 

 

In addition to finalizing the specific software tools we plan on using, I also specified how these different software components will communicate with each other. I plan on using WebSockets to establish a long-running connection between the mobile app and the EC2 instance to push occupancy updates to our mobile app in real-time via this connection. Finally, I created an app mock-up on Figma that I plan to follow closely when designing the actual app using Flutter. 

 

I think I am currently on track. Next week I want to start on implementation. My personal goal is to get our EC2 instance working and start learning how to use Flutter to design our mobile app. Within our team, I will work on writing up the software side of our design report and help my team finalize their parts of the design process.

 

Team Status Report for February 17, 2024

After meeting with gym administrators this week, we have eliminated the camera system from our project. Our proposal for the system up for our people counting model was rejected.  We are currently waiting for approval from gym administrators with a new approach using two proximity sensors to count people entering the gym.  As of now, no costs have been incurred from this change. Our schedule change is pending the approval of the two-sensor people counter from gym administrators. 

Right now, our biggest risk that could jeopardize our project is not getting approval for our people counting module being set up in the U.C. gym. We are managing this risk by staying in contact with UC gym administrators, and in the case we have it rejected we have data that UC gym employees have given us access to that can be used to train a rough model. We also plan on relying on surveying people on the time they use the gym in the worst-case scenario.

 

Part A was written by Max Adams

Considering public health, our product solution addresses the problems of overcrowding in the gym and the effects it has on aspiring and current gym goers. Current gym goers will be able to pick better times to exercise, improving their physical fitness. Our solution also applies to those who may be reluctant to go to the gym because they are anxious about it being crowded, providing a medium where they can see how crowded it is and pick times when they may feel less anxious when it is not crowded. This will help them both physiologically and psychologically, enabling them to exercise while providing the comfort of knowledge in the crowding state of the gym space. 

 

Part B was written by Sid Sapra

Our gym tracking app meets the need for real-time insights into gym occupancy and equipment usage which allows it to have a large social impact on individuals focusing on fitness. By predicting crowd levels and machine availability, it enables users to plan their workouts efficiently, fostering a sense of community by promoting collaborative sharing of equipment. This not only streamlines the workout experience but also addresses social factors such as varying cultural attitudes towards exercise and socioeconomic backgrounds, contributing to a more inclusive and connected fitness community.

 

Part C was written by Derek Kim

Our solution addresses the need for efficient gym space management by displaying real-time gym occupancy data to users. By integrating sensors into gym benches and leveraging machine learning algorithms to analyze occupancy patterns, our solution optimizes the use of gym facilities and enhances the overall experience for gym-goers. However, in our specific case, this would be a service that we would be providing to CMU students which means that it is not a product that we are selling. 

However, this solution can be scaled to fit the needs of commercial gyms since commercial gyms often have occupancy issues. In this case, our solution offers several economic benefits. Making real-time gym data available to consumers can help combat congestion in the gym space which will allow for an increase in gym capacity each day. Additionally, this service would be very helpful for people who are busy and need to plan their gym sessions during the day; this service would attract many more customers who often find it hard to make time to go to the gym, especially during high occupancy hours. Finally, our product would give access to historical data on gym usage which allows gym management to make more data-driven decisions to further improve their efficiency. Overall, our solution provides economic benefits by optimizing resource utilization and improving consumer experience.

Sid’s Status Report for February 17, 2024

This week, I focused on understanding how to build our new version of the people counter, as well as what would be the optimal way to train the Machine Learning Model for predicting crowdedness. For the counter, I noted down a bill of materials, and worked on understanding how to get the sensor to interact with the raspberry pi. For the Model, I gathered the appropriate data, and researched previously developed models for similar predictions. I have begun writing a script to determine other factors such as temperature that can be included in the training data to increase the model’s accuracy.

By next week, I primarily hope to have the people counter ready, so that I can begin working on collecting more data for the model. I would also like to have the current dataset fully completed by then.

I believe I am currently on schedule, although some of the previous progress was nullified due to the fact that we will no longer be using a CV model for counting people.

Derek’s Status Report for February 17, 2024

This week I decided on specific components that we will be using for the software/mobile app part of our project. For the mobile app, I plan on using Flutter. Flutter is a good choice for our project because our mobile app will be relatively simple and Flutter provides ready-made widgets and high performance. Additionally, I decided on using an AWS EC2 instance to host the backend server. Since we need a way to store and manage data, I planned for us to use MySQL for our database. I chose MySQL because of its ease of use and performance; we want our system to be real-time so performance was a high priority aspect. MySQL is also an established database so there are a lot of resources and support available. 

I think I am on the right track right now since a lot of our group’s focus is currently on the hardware. However, for this week, I plan on doing more research on how to integrate all of the different software components together. Additionally, I want to create a mockup of the app on Figma. Aside from my personal deliverables, I plan on working on the design report with my group.

Max’s Status Report For February 17th, 2024

This week, I was able to finalize an overall list of components for my part of the project. Currently, the sensor module will consist of a battery pack, a NodeMCU, and an active IR sensor with a 100-550cm range (within what we need for our use case).  I was debating trading the IR sensor for an ultrasonic sensor in our design for the sensor module because an ultrasonic sensor module was said to be more reliable from my research and is also much cheaper per sensor. Still, the UC gym is very noisy and would very likely interfere with it. I also concluded that it would make me more susceptible to outside activity because of its wide detection field. (I was looking more closely at the HC-SR04 for ultrasonic) . I also brainstormed a potential detection algorithm for the NodeMCU software with the IR sensor. This is something I’d like to test and continue to develop when I receive the sensor so I can abide it by the sensor.

My progress is on schedule according to our current chart, but I would like to order my components this week. My main concern is the IR sensor, and ensuring that it abides by the range of 100cm-550cm. I’d like to also finish our design presentation and will be working on the report this upcoming week.

Max’s Status Report for February 10, 2024

I worked on the proposal presentation with my teammates and researched possible components for our idea. I am looking at how we could get wifi on a Jetson, and I have also been refining areas where we can set up both our sensors and camera module. I am currently on schedule, and in the next week I’d like to have our design flushed through and some parts ordered. I also look to finish talking to the gym administrators and get a final answer from them.

Team Status Report for February 10, 2024

As of now, our most significant risk is not being able to set up our camera in the UC gym. We plan on meeting with gym administration this upcoming week to settle this. In our meeting, we plan to introduce our project and our intentions with using a camera. In the case that they reject the camera, we have a few alternative solutions for the role that it fills. (Collecting data for predictive models)

Sid’s Status Report for February 10, 2024

This week I worked with the team to build the project proposal. For this, I added the technical information regarding the Computer Vision Pipeline as well as the prediction software that we will be building. I researched an effective way to build a people counter using OpenCV and am on schedule for the same. Furthermore, the team and I set up a time to meet with the gym administrator to talk about setting up our project.

Derek’s Status Report for February 10, 2024

This week I did more research and specified more details of our project. I worked on creating the block diagram and preliminary user interface design for the proposal presentation. Additionally, I contacted the UC administration to schedule a meeting to discuss our project and request approval for camera usage and setting up our sensors in the gym space. I am on schedule and I plan on working with my team to specify more parts of our project. Specifically, I would like to research and decide on the web application framework for our mobile application. Finally, our team will be meeting with the UC administration this week.