Nii-Okaitey Tetteh, Chi Nguyen, Likhitha Chintareddy | Carnegie Mellon ECE Capstone, Spring 2023
This week I was finally able to figure out why our Jetson was not working. It turned out to be an issue with the board, which I was able to figure out after trying another group’s (A5) board. With a new working board, I was able …
This week, I continued to tweak the CSS of the web app and attempted to test the AJAX functioning. I simplified some of the more dynamic UI elements and made them static – instead of a carousel of cards to choose dining halls, there will …
The most significant risks that could jeopardize the success of the project is probably the hardware component because we received the Jetson Nano so close to the interim demo and was experiencing trouble setting it up in the beginning of the week (this problem has been resolved as of now and we’ve been working on next steps). Integrating the system is another challenge we are experiencing due to the shipping delay of the Jetson Nano. We also experienced technical issues with the Jetson Nano and had to replace it early in the week (luckily another group had a board they didn’t use and was very kind to give it to us). However, our team member has been working very hard to speed up his progress due to this unforeseen circumstance. Our members have also been taking aside time to learn about incorporating SQLite database into our system, specifically about the data transfer process between the Jetson Nano and the website server. Even though these risks are somewhat concerning, our team members have been making good progress towards solving these problems. We also know people who have been working on these components and we would reach out to them if these problems continue to be unresolved.
Another update: Our team members have figured out how to set up the camera and Jetson Nano and tested them with a face detection module which worked well with those hardware components. All we have to do left after the interim demo is to connect these components together as we already have working pieces.
There were no changes in our design as everything was very well thought out and hence no additional cost was incurred.
We have updated our schedule here as required for interim demo.
The goal of this past week has been obviously to work on our product to showcase at the interim demo. I’ve been working on polishing my parts to make sure that the CV algorithm is able to process videos and output the bounding boxes of …
This week was challenging for the Jetson board. The majority of this week was spent debugging the boot up of our board, with it continuing to hang on the NVIDIA logo screen upon starting up. For debugging I’ve been reading a lot of forums online, …
Over the past week, I updated the UI and the AJAX required to update live wait time information: https://github.com/santacalculus/No-Time-to-Dine-capstone. I’m working on refining the CSS design at the moment to make the webpage appear cleaner, and debugging the code for the main menu page where users choose which restaurant to go to (menu.html file in templates folder and base.css file in static folder) – there is an issue with the alignment of cards for dining halls that I’m trying to figure out how to fix. The icons that represent individuals in line are not rendering on the page, which is another problem I’m planning on debugging. But because the AJAX has been implemented, once we integrate the system for testing i.e. the Jetson Nano and CV algorithm, it should be able to update live wait time every 2 seconds – and I will be able to assess any errors in the event of it not working.
Over the next week, my aim is to make sure the web app does its part of the job wrt interim demo – display wait time information and update in the given constraints. This means by the end of the week, I need to test whether there are any issues with my AJAX implementation and fix the problem with the icons not rendering.
Because I’m currently debugging the code, I’m slightly behind the schedule and have updated it accordingly: https://docs.google.com/spreadsheets/d/172baIWKtfkJjnvyUFb2y0nYx2lQU0aVvdxOXiqKtKBI/edit?usp=sharing
The most significant risks that could jeopardize the success of the project is that we have trouble setting up the hardware side which leads to us having trouble integrating the whole system together. We are concerned about this because it’s difficult to estimate the current …
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 …
The most significant risks which could jeopardize the success of our project thus far are a lack of integration of parts too late in the semester. Currently we are all developing our parts individually, but bringing it all together is what is most important for our project. This integration should mostly be completed by Nii, and since we were able to receive the rest of our parts this week we were able to start doing this early.
No changes were made to the existing design of the system. Because the parts just arrived this week the only schedule change that’s been made is to Nii’s schedule. Here is the updated schedule:
This week, I continued implementing the UI while simultaneously working on AJAX with some dummy hardcoded data. The login page and registration page have been implemented without OAuth and only using Django’s authentication package for now – I’m a little unfamiliar with implementing OAuth so …