Nii-Okaitey Tetteh, Chi Nguyen, Likhitha Chintareddy | Carnegie Mellon ECE Capstone, Spring 2023
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 …
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 performance of our program as we haven’t had the chance to test our program on the Jetson Nano. Our risk mitigation plan is to run and test our software side on a virtual environment such as Google Colab that provides support for hardware accelerator GPU and to optimize it on this architecture. Even though we have been testing our CV algorithm on a virtual environment that is somewhat similar to Jetson Nano, we are unsure about the final performance as they might have different architecture that will optimize the speed of computation differently. The same applies for the web application as currently, it uses dummy data for displaying information but we need the system to be integrated to actually test whether it works as necessary. As discussed in our previous meeting, this is our main concern and we need to resolve this as soon as possible before interim demo. Our team members have been working together to resolve this issue with the hardware side so that we can improve our progress.
There were no changes to the existing design of the system. The design was very well thought out and it’s unlikely that we will change it at any point in the near future. The budget for the project remains the same as before.
Our goal for this upcoming week is to integrate our system and have everything ready for the interim demo. We’ll actively test our system against datasets collected in a lab setting and monitor any rising issue.
We are behind on our schedule due to these issues and have therefore updated our schedule to reflect these changes and our current plan here.
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 …
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 the first priority is to get the registration and login working and then introducing OAuth that will enable users to login using their Google accounts at a later time after implementing most other UI features. The rough mockup of our updated UI is attached below.
The left half that displays the time of arrival has been implemented. However, the barometric needle on the right side has been a challenge to implement due to the complexities of the angle of the needle which has to change with dynamic data (which we do not have, at the moment), and I’m currently working on it. I’m still on schedule, it’s just that I’m working on both UI and AJAX simultaneously so I should be able to finish both by the end of the AJAX implementation part of the schedule.
I’ve finished fixing the errors on the CV side and fine-tuning it so the code should be ready to run on the Jetson Nano. Testing the code is not a one-time task and it’s something that I will keep doing every week. As we’ve finally …
This week I received the rest of the parts I ordered before break. Now that I have all the hardware components, I began setting up the Jetson. I got the OS working on the Jetson, and cloned our github repo onto the board. Additionally, I …
In the earlier week, I went through the results of the user studies conducted with various design ideas and came across an interesting paper [linked HERE] that led to a massive redesign of our initial idea. This resulted in our idea going from a simple line-based representation of the number of people waiting to a more visually informative design inspired by the study
Further information on how and why this design is interesting and fits our users’ needs was given in the Design Report. Later in the week, I laid down some preliminary work to rewrite the code for the UI (as our design has been changed). However, due to the nature of spring break and a flu I caught in the earlier part of the week, work has been delayed. I’m currently still working on the UI but will have to simultaneously start working on the AJAX implementation in the later part of the week. This gives me about 4-5 days to finish major sections of the UI where I can focus solely on it. So I’m delayed from the schedule by 4-5 days but working on the AJAX in the later part of the week including the weekends should hopefully make sure I will still be on track without necessarily having to push anything in the schedule.
To answer the question for report #4, as a team, we will all need to become comfortable with using Replit which we have never used.
As a team, the week was mostly spent on doing the design review report. We were still waiting on some hardware components to arrive so that we could finally start setting them up in public space. We think the risks that could jeopardize the success …