Team Status Report for 5/8

This week we focused on debugging our device and also assembling the belt and attaching it to our Raspberry Pi + camera. We tested it out at the stoplight again and found that in some cases it was having problems, so debugged those.

Risks and Mitigations

Current risks include the latency of our device and the accuracy. We had to settle for a minimum for the accuracy, but the latency is currently too long for a user to safely use it at a traffic light. We are looking into what else could be done to cut that time down.

Schedule

We need to just wrap up our final presentation requirements such as the video, poster, and final report. Last minute things include maybe any adjustments to the belt to make it more comfortable.

 

Team Status Report 5/1

This week we integrated all our parts and debugged any issues that arouse

Risks and Mitigations

We found that the raspberry pi processor does not work quickly with the tensor flow application. Our latency is ~26 seconds which is way above what we expected. We are going to prioritize latency over accuracy as of now.

Schedule

Down to the last week, we are going to clean up as many issues as possible. This includes latency and accuracy. We will finish up testing and prepare the powerpoint, poster, and video

Team Status Report for 4/24

StATUS
  • Traffic Light CV – Yasaswini
    • Functional CV model to detect boundaries of traffic lights in a scene (yay!)
  • Look Light Detection – Shayan
    • Improvements on traffic light detection
    • Work on detection using full scene in case CV doesn’t properly work
  • Raspberry Pi Interface – Jeanette
    • Validation testing of camera and button setup.
    • Beginning testing code integration with the code in the GitHub right now.
CHANGES TO THE SYSTEM
  • Nothing new this week 🙂
CURRENT RISKS AND MITIGATIONS
  • No new risks/mitigations this week. Shayan needs to validation of his algorithm with the outputs of the Yasaswini’s CV as input.

Team Status Report for 4/10

StATUS
  • Traffic Light CV – Yasaswini
    • Integrated git with the cloud so its all set up for the model to start training as soon as the current algorithm is done
  • Look Light Detection – Shayan
    • mostly working look light traffic light detection via the Traffic Light Color algorithm but may need some modifications
  • Raspberry Pi Interface – Jeanette
    • Set up camera and the button to the Raspberry Pi and the camera has been checked to be working. With the battery pack connected as well, it’s basically ready to go.
CHANGES TO THE SYSTEM
  • Nothing new this week
CURRENT RISKS AND MITIGATIONS
  • Yasaswini – need to see what the training accuracy is on the images and need this going into next week
  • Shayan – need to further experiment with the angle/light to make sure all situations are accounted for

Team Status Report for 4/3

THIS WEEK…
  • Traffic Light CV – Yasaswini
    • With AWS credits procured, need to finalize AWS integration with Git development to facilitate cloud computing
  • Look Light Detection – Shayan
    • With understanding of Hough Transform, need to optimize Look Light search with preprocessing input to Hough Transform
  • Raspberry Pi Interface – Jeanette
    • Now that we have the parts and components, need to set up RPi and interface components with it
STATUS…
  • Yasaswini – AWS cloud deployment setup finalized, integrated COCO dataset with AWS API, and began implementing training model with AWS setup in mind
  • Shayan – further optimized look light detection to more accurately search for the colored lights in traffic lights through image size regularization as well as red, yellow, and green color masks/filters
  • Jeanette – completed Raspberry Pi setup, RPi camera setup and verification, acquired remaining components
CHANGES TO THE SYSTEM
  • Nothing new this week 🙂
CURRENT RISKS AND MITIGATIONS
  • Yasaswini – when running the training next week and checking accuracy, we will be able to better determine shortcomings in the CV algorithm
  • Shayan – need to further preprocess images to account for excess light / saturation in photos

Team Status Report for 3/27

This week:

  • Begin to set up AWS network
  • Research image processing techniques for circle recognition
  • Set up raspberry pi

Risks:

  • We have had difficulty in setting up the AWS cloud
  • Delay in shipped goods (arrived on Thursday)

Mitigations:

  • Updated schedule

Now that we have finished set up and received supplies we hope to make significant progress on our algorithms this week.

Team Status Report for 3/13

THIS WEEK…
  • Wrote up the Design Proposal Document
  • Received all the ordered parts & started to put them together
  • Tagged the photos we took in order to feed them into the algorithm
  • Set up environment for the pictures to be fed into
STATUS…
  • Need to obtain AWS credits in order to move further with our algorithm
  • Are a bit behind schedule with the testing which was supposed to start this week but continue into next week
CHANGES TO THE SYSTEM
  • Changed the use case to helping visually impaired individuals in their training to cross intersections
CURRENT RISKS AND MITIGATIONS
  • Currently the accuracy rate is the biggest potential risk which we have yet to see the numbers for
    • Currently we are tagging all the stoplights in a given picture frame in order to mitigate this somewhat by accounting for this

Team Status Report for 3/6

This week…
  • Continued refreshed code for project, e.i. tensorflow, opencv and raspberry pi
    • Actually started implementing and debugging code
  • Prepared for the Design Review slide presentation
  • Got insights from visually impaired user, gained a broader understand of how the visually impaired cross intersections, and correspondingly amended our use case and end user
  • Finalized Bill of Materials and ordered hardware
    • Incl. finalizing the camera we’re using: a RPi camera
Status…
  • On time but still need to obtain AWS credits
Changes to the system
  • Altering mechanical form factor from headband to belt
Current risks and mitigations
  • None with development currently

Team Status Report for 2/27

This week…

  • Refreshed code for project, e.i. opencv and raspberry pi
  • Prepared for the proposal project
  • Presented the proposal project
  • Reached out to out interviewee
  • Took photos of intersection for data set
  • organized photos for dataset

Status…

  • On time but need to order components next week

Changes to the system

  • None at the moment

Current risks and mitigations

  • if there should be an enable button for our device
  • distractions from other attributes of the intersection
  • how all our devices will fit in the headband

Team Status Report for 2/20

Changes to the System:
  • We decided to change our product into a headband, which can be worn by the user, since that way the cameras will be positioned optimally. Also since a headband has the full circumference, we can easily place the processor in the back too.
  • While we do have datasets of traffic lights to train on, we decided to go with real live pictures of the Morewood/Elsworth Intersection (“ElMo”) as our main form
Current Risks and Mitigation: 
  • Making sure that the Raspberry Pi can stay powered portably for a lengthy duration and that it doesn’t get too heated. Since this is going on the user’s head, it’s important to develop some sort of barrier between the system and their head, such as padding.
  • Our current design definitely might need to be updated once the parts come in. While we have estimated as closely as possible with the sizes of the various parts online, it might be a different picture putting them together