Carnegie Mellon ECE Capstone, Spring2021 || Maddie M., Sarah T., Zixuan Z.
This week I worked on testing the threshold for more exercises and the pose comparison algorithm. Since some core exercises have relatively low detection accuracy, I removed them from the workout library. I recorded some demo videos for the final demo. We also discussed the structure of the final video.
We will continue to work on the video for the demo and the final report next week.
This week we continued to work on integration and started working on the demo video.
The most significant risk is that the accuracy for some core exercises is lower than we want. We decided to remove some exercises that are hard to detect (such as elbow to knee) from the workout library.
We will work on the final video and the report next week.
This week, I downloaded the latest version of the UI onto the board. I worked with Maddie to fix an “illegal instruction (core dumped)” error the board kept producing. It ended up being a NumPy error. We had to downgrade the version. But now the UI works on the board. It’s integrated with the pose comparison, scoring, and accounts now. Zixuan was able to get the UI to show while the pose comparison runs.
I was also able to finalize the exercise library.
I recorded a bunch of demo clips this week, too. Maddie will crop and stitch them together for the demo video. We also finished our poster.
We’re on schedule. We just need to finish the video by Monday night. Then, next week, we’ll just need to do the public demo on Thursday.
This week I finished up changes to the user accounts. Now the user is able to enter in their name and view a graph displaying their progress as they complete workouts. I also spent time recording footage for the video, as weak as putting together the poster for our presentations.
I also gave the final presentation for our team this week. Our project came together nicely.
This week, I downloaded all the dependencies necessary to run the UI on the Xavier board. The code didn’t run correctly on the board, but it wasn’t a dependency issue. I also had to resize the camera feed frames because the default size from the webcam was different from the default size on my laptop.
I’m behind schedule because I didn’t think I was going to be sick for that long after getting my second COVID vaccination shot.
Next week, I hope to download the new UI code on the board. Zixuan modified it so the UI could run at the same time as the pose comparison code. I also hope to finalize the exercise library.
This week I added more exercises into the metrics library and did some tests with the pose comparison algorithm. I also worked on the integration of the comparison algorithm and UI. Now we can run pose comparison with the UI. We have the gif of the exercise on the left and user’s video tracked by OpenPose on the right, and we get a result back which reflects the level of completion for each workout based on the angles.
Next week I will continue to work on the integration of the project, add more exercises into the metrics library, and try to improve the overall comparison accuracy.
This week we mainly worked on the integration of our project. Now we can run the pose comparison with the UI.
The most significant risk for us right now is the successful integration of the entire system on the board. We need to resolve some issues caused by our different configurations. We hope to have everything put together next week and test the entire system.
Next week we will work on the final presentation and continue to integrate our system.
This week my primary focus was the incorporation of user accounts and the leaderboard. I used pygame combined with sqlite databases to store tables that could keep track of the user’s scores and update their progress with a new score after completing another workout. I sometimes am running into issues with updating the scores properly as the identifier is the users name that they enter so I am sorting through that issue to be finalized with the other stretch goals.
We want to, as a stretch goal, add notes on which parts of the body are causing the most issues on which exercises, so this week I want to help add that to our final version of the project.
This week I spent my time working on the user profiles. I modified the code for the leaderboard so that a higher achieved score will replace the score on the leaderboard by default. I’m also working on modifying my individual user score tracking so that we can continuously update progress and display the data in a graph for easier user viewing.
Next week, I plan to finish my work on the user accounts, as well as returning to testing and debugging our exercise tracking code. Some of the exercises currently work better than others, so I want to continue testing all of the exercises to see which ones we need to focus our efforts on particularly.
This week I fixed some bugs of the pose comparison algorithm. One of the bugs was that since I was looking for 10 frames around each timestamp, an error would occur if 2 timestamps we were checking are less than 10 frames apart. I fixed it by setting the range of frames we use for comparison based on the timestamps of the exercise. I received the camera and did some test with it. I also collected the data for more exercises and added them into the comparison metrics library. I wrote another script to make the comparison algorithm work for a sequence of multiple workouts.
We are on schedule. Next week I will continue to add exercises into the metrics library and do more tests with the pose comparison algorithm.