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.

Jeanette’s Status Report 3/27

This Week:

  • helped Yasaswini debug the AWS set up
  • Notified TA of delayed shipping of parts
  • Research steps to set up raspberry pi to speed up process
  • Download the OS into the mini sd card

Next Week:

  • Finish and connect OS system set up for raspberry pi
  • Connect the camera
  • Take photos with camera and send to Ricky in order to test quality
  • Connect amplifier and speaker to the raspberry pi

Our parts were delayed a week more than expected so my progress was halted until then. Therefore, assembly is behind schedule but research should help speed thing sup next week.

Shayan’s Status Report for 3/27

Progress Made

My sole focus area this week was the Look Light traffic light detection algorithm. This image processing / pattern recognition based algorithm is based on the Hough transform, which returns the positions of circles of radii within a specified range as found within an input image.

My work was broken up into the following areas:

  • Detecting circles in general
    • It took no time to detect a sole circle in a picture of a single circle. Detecting circles got harder with multiple circles in the picture. I was surprised to learn that the Hough Transform sometimes misses a circle within a group of concentric circles. I learned to optimize Hough transform radii parameters to detect all circles in images with multiple circles.
  • Detecting circles in traffic light images
    • My learnings and parameterization of the Hough Transform for pictures of circles were transferred to use on images of traffic lights as well as traffic lights side-by-side (if you can imagine differently-facing traffic lights for perpendicular directions being hung right next to each other).
  • Increasing accuracy in traffic light circle detection
    • I found out that the Hough Transform, in certain lighting conditions, sometimes “detects” curved edges as part of a circle and therefore “detects” circles that aren’t in the image. I am currently trying to determine, through empirical means, how to isolate just the physical light within the traffic light. I am leveraging the fact that the light of interest is illuminated, meaning that the respective pixels are of higher intensity (aka I can use some kind of filtering / thresholding). This allows me to run the Hough Transform on the isolated light portion of an image.
Progress

Reasonable progress made towards having a robust look light detection algorithm, so I believe I’m still on track. 🙂

Deliverables for Next Week
  • Main priority: Keep optimizing the look light algorithm. Figure out how to best filter/threshold the traffic light image to isolate the light. Then, reassess and fine tune the Hough Transform parameters as needed.

Yasaswini’s Status Report for 3/27

Things done this week:

  • Created EC2 Instances necessary for training on the cloud
  • Set up AWS CodeDeploy instance
  • Established a successful ssh connection to the instance on the cloud
  • Downloaded the necessary tools in the cloud environment

For Next Week:

  • Make sure that automatic deployments are occurring
  • Need to import the training model in
  • Make changes to the training model to better fit the images we are given
  • Feed the training images into the model and see what the accuracy will be

Jeanette’s Status Report for 3/15

Things done this week:

For the first half of the week, I helped my team prep for the presentation, making sure everything was prepared for Monday. After, we worked on the design report and taking advice from our presentation. Then, we began to do working session to start on the project. I worked on gathering the mailed in parts and setting up the raspberry pi. However, I forgot to order some miscellaneous cords in order to set up the pi. Therefore, I am going to be delayed until those parts come in which will be Thursday.

 

Things for next week:

  • Help out Yasaswini and Ricky with any coding they need help with until Thursday
  • Work on the design report
  • Set up the raspberry pi
  • Connect the camera and speaker to the raspberry pi

Shayan’s Status Report for 3/13

Progress Made

My main focus this week was working with the traffic light detection algorithm’s validation set. A lot of the work was going in and hand tagging traffic lights – and with the suggestion of detecting more than just traffic lights (from our Design Review feedback) – crossing lights, cars, and other pedestrians. 

Additionally, I began working on the look direction traffic light detection algorithm, which takes in a cropped image of all the traffic lights in a scene and deduces which of the lights, if any, is the light the user is facing. My current implementation is by using the Hough circle transform (available in the opencv library) and looking for the traffic lights in which the more of the lights’ circular shapes are present given the angle at which the user is facing the light.

Progress

On a changed schedule – instead of myself and Yasaswini working on the traffic light detection algorithm first, I am working on the separate light state detection and look direction algorithms while Yasaswini, with Jeanette’s assistance, works on the light detection.

Deliverables for Next Week
  • Zeroth priority: further refine (and FINALIZE) our requirements when meeting with Tom and Rashmi
  • First priority: Continue working on and debugging the look direction algorithm

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

Yasaswini’s Status Report for 3/13

Completed for this week:

  • Worked on specific sections of the Design Proposal Document
  • Set up tensorflow and the environment in python
    • Downloaded all the necessary tools and libraries
  • Started to download the C0C0 dataset
    • Had storage issues so need to wait to deploy to the cloud when we get access
  • Looked into which algorithm to train on once the data comes in

For next week:

  • Need to get the training algorithm up and running
  • Test the training algorithm using the validation set
  • Deploy our code to the cloud so we have more space

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

Shayan’s Status Report for 3/6

Progress Made

My main focus this week was with prepping and structuring the CV algorithm. I’ve been coding the training algorithm using the TensorFlow library and mainly debugging on smaller datasets (so I can run locally). 

I also helped the team finalize our parts order, which was sent out!

Progress

On Schedule! 🙂

Deliverables for Next Week
  • Procure AWS credits and find out how to train model using AWS
  • Train CV model on COCO dataset using TensorFlow
  • Hopefully be able to do some validation with the photos I took too