Chi Nguyen’s status report for 03/25

Since we were having some trouble setting up the hardware, I’ve been continuing working on the software code and test it with my own test cases that I made. To be more specific, I’ve been writing the code for the wait time algorithm and I am currently testing it against dummy test files that have the same data representation as the outputs from the YOLO algorithm. I’ll update my code and results here shortly after finalizing it locally. I am definitely concerned about running my code on the Jetson Nano though, which is why I’ve been running my code on a virtual environment like Google Colab with Roboflow API. Even though it’s not the same as Jetson Nano, I believe that the better the software side performs on there, the better it performs on the Jetson Nano. I’ve also started setting things up on Replit so that can be ready to have a mock interim demo this upcoming week. I’ve also been looking into how data could be transferred from the Jetson Nano to our database SQLite on our web server, what the data transfer package should be like and what data representation will look like on there. We want to store the date and time information and the number of people at that time so the the table should have 3 columns: (1) date (format type: string), (2) time (format type: string), (3) number of people (format type: integer).
My progress is a little behind because there is a lot to finish for the interim demo. I am estimating that we will spend a lot of time on making the performance of our software side meet our goals. Actions to catch up is to meet more over the next 2 weeks as a group and actively integrating our system and test our system against actual test cases.
The goal for this upcoming week is definitely to gather more data in the lab which has a similar environment to our interim and final demo and focus on testing our system against these datasets. We aim to have our system integrated and work well against test cases. Performance wise, I do not expect our system to meet the performance by Friday of next week but we are aiming to meet it before the start of the interim demo week.