Team Status Report 4/27/24

Team Status Report 4/27/24

Potential Risks and Mitigation Strategies At this point, really the only issues we could potentially encounter are if the fixed version of the PCBs don’t actually work as intended and if the overall latency for the integrated system is higher than we had planned for 

Team Status Report for 4/20/24

Team Status Report for 4/20/24

Potential Risks and Mitigation Strategies The concurrent videos we took at the intersection this week involve a lot of hand-shake, so hardcoded lane boundaries are not an option. Currently, code that detects the lane boundaries using Canny edge detection is not working, so we ordered 

Team Status Report for 4/6/24

Team Status Report for 4/6/24

Potential Risks and Mitigation Strategies Some risks we currently have are that the additional code we need to add to the object detection model to only identify cars that are waiting at one side of the intersection may add additional delays to our system — 

Updated Schedule for Interim Demo 4/3/24

Updated Schedule for Interim Demo 4/3/24

Here is our updated Schedule as of 4/2/2024. We have cut into our slack time, with our current testing plans now falling on the week after Carnival (starting April 15) (around the time when we’ll be working on our final presentation.) Each subsystem is close to being 

Team Status Report for 3/30/24

Team Status Report for 3/30/24

Potential Risks and Mitigation Strategies The new YOLO car detection model is working a lot better and way more accurate than our previous model with the Haar cascades, however it is very slow and takes about 11 seconds to detect the cars, so we are 

Team Status Report for 3/23/24

Team Status Report for 3/23/24

Potential Risks and Mitigation Strategies We had some setbacks with the object detection model and wireless camera setup this week. For object detection, the original plan was to use Haar cascade classifiers to identify the number of traffic objects (cars, buses, pedestrians, etc.), but some 

Team Status Report for 3/16/24

Team Status Report for 3/16/24

Potential Risks and Mitigation Strategies The biggest thing we are uncertain about right now is whether or not the videos we are taking at the actual intersection we want to model (Fifth and Craig) will be sufficient to train the model. It could be challenging 

Team Status Report for 3/9/24

Team Status Report for 3/9/24

Potential Risks and Mitigation Strategies Currently we are having challenges setting up the RPi to work with the CMU-Secure WiFi. In case that does not work out, we will instead use a mobile hotspot to provide internet access to our RPi to perform the necessary 

Team Status Report for 2/24/24

Team Status Report for 2/24/24

Potential Risks and Mitigation Strategies While we are feeling more confident with the optimization algorithm and the SUMO simulation platform, our camera situation is still uncertain due to an inability to connect to CMU-SECURE. We’ll be ordering a BLE camera to test our vehicle detection 

Team Status Report for 2/17/24

Team Status Report for 2/17/24

Potential Risks and Mitigation Strategies At this time we feel more confident in our solution and we were able to finalize most of our solution approach with specific hardware and software we are using. Earlier in the week we were hesitant on how we can