Posted on

Maddie’s Status Report for 4/24/2021

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.

Posted on

Zixuan’s Status Report for 4/24/2021

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.

Posted on

Team Status Report for 4/24/2021

A risk to our project is not being able to run the UI on the board. It could possibly run differently on it. Another risk is the pose comparison being too slow or the UI lagging once we get both on the board. To mitigate any problems from integrating all of our software on the board, we will get it on the board by Monday so we can start testing how everything works together.

One change was made to our materials. We bought a second camera (same model as the one we already have) because we ran into issues with recreating bugs (we encountered on the Xavier) locally on Zixuan’s laptop. We found that the difference in frame rates of the laptop camera and web cam on the Xavier was affecting the behavior of the pose comparison code. This only increased our project budget by $30.50.

Posted on

Sarah’s Status Report for 4/24/2021

This week, I added the evaluation workout to the UI loop. Now, it comes directly after the instructions screen. Once the user finishes the evaluation workout and is show their score, it’ll take them to a workout instructions screen (to inform them that the next workout will be a personalized based on the score they received on the evaluation workout). Then, they can choose when to start that workout.

I also made the rest screen look the same as the exercise gif screens. So, now all of the screens have the demo gif on the left and the user live video feed on the right. The label of the current exercise is on the top left corner and the label of the next exercise is on the top right corner. On the rest screen, there is also a label in between the current and next exercise labels that displays the rest countdown.

Lastly, I created a help screen that lists the quit, return-to-home, and pause commands. This help screen can be accessed from anytime in the UI except for the actual workout. So, the user can press “H” on their keyboard for help if they are on the home screen, any instructions screens, exercise preview screens, and scoring screens. I only allow the user to press quit the entire UI program, return to the home screen, and pause their workout once the workout is running. If the user isn’t doing their workout and goes to the help screen, they can press enter to return to where they left off.

I’m on schedule (we’re currently in our buffer time).

I’m planning on uploading the UI code to the Xavier board so I can integrate it with the pose comparison for scoring. I also am planning to add more exercises to our exercise library so we’ll have at least 100 exercises.