Weekly Status Reports

Gauri’s Status Report for 04/04

Gauri’s Status Report for 04/04

This week was too busy for me personally due to midterms, assignments and moving to another apartment on campus, so I didn’t get to spend as much time as I would have liked to on the control loop.  We met a couple times this week 

Neeti’s Status Report for 04/04

Neeti’s Status Report for 04/04

This week we all worked individually on our predetermined parts rather than meeting to discuss decisions. On Monday, we met briefly to discuss our progress on our respective parts. I spent the majority of this week working on the neural net classifier for the hand 

Shrutika’s Status Report for 04/04

Shrutika’s Status Report for 04/04

This week we made a lot of progress on manual mode – Neeti was working on the gesture classifier and training the models, and I worked on creating the simulation and figuring out how we can hook it up to output from the sensors. Matlab is kind of weird and their 3d World Editor is not very well documented. I have been able to receive external output (right now just from my keyboard keys) and pass that to Simulink, and I have been able to create something that looks like what our device would have looked like and made it rotate – but still working on how to connect those two parts.

I think we’re still on track to get manual working by Wednesday if we work hard this week – we plan on working for a while tomorrow to hopefully be able to test the gestures with the cameras I have. I think it is a good idea to start looking at the microphones this week as well – I have a ‘lab bench’ set up in my house in an area that no one will touch that I plan on setting up and testing the microphones.

We have the work split up pretty well right now, so I think as long as we continue to all work we’re on track to finish by the end of the semester.

Shrutika’s Status Report for 03/28

Shrutika’s Status Report for 03/28

We restructured last week, and this week we started working virtually on different parts of our project. It’s nice that most of our parts shipped really quickly, so I think we already have everything that we will need for the rest semester (hopefully). This week 

Neeti’s Status Report for 03/28

Neeti’s Status Report for 03/28

This week we met on Monday (03/23) to discuss what to do about the microphones and we finally ordered four of the cheap adafruit microphones as only one of our devices will display automatic mode. I worked on downloading the gesture dataset. We met on 

Team Status Update for 03/28

Team Status Update for 03/28

This week we began implementing based on our restructured plan.  Neeti is working on the gesture classifier, Shrutika is working on modelling the physical platform animation with Simulink and Gauri is working on the control loop.  We also ordered and received the mics.  So we have all the parts we need to complete our project.  The main changes we are making are with regards to animating a physical platform using Simulink instead of building a real one and rotating the animation based on the inputs received and processed by the RPis.  We overall seem to be on track to demo-ing at least a mostly full version of manual mode.

Updated Risk Analysis:

We have identified several risk factors for our project.  The first risk factor is related to the gesture detection input, taken by the Raspberry Pi Camera Module to classify left and right gestures, and forward them to the paired COMOVO.  The risk here is that the accuracy rate of identifying the gestures depends on the size and quality of our dataset.   Since we don’t have the resources to make our own datasets anymore, we are choosing an already available dataset and have changed the gestures to thumbs-up and thumbs-down for right and left.  We plan to narrow the scope for the purpose of the demo to recognizing a gesture with a specific background (against a plain black/white background).

The second risk factor is the accuracy of the sound localization.  We are planning for a very high accuracy rate of the COMOVO rotating towards the loudest speaker, and we have identified several risks regarding ambient sound, sound from the phone speaker and the accuracy of directional microphones.  We plan to use hand-made baffles around each mic to ensure that too much ambient noise is not picked up.  For the demo video we will demo in a quieter room so that there isn’t much distracting ambient noise.

The third risk factor is the potential for higher latency than is anticipated. Since our use case is for long distance video calls, our short distance testing might not accurately represent the latency for our original use case.

Finally, the performance of our device is heavily dependent on parameter tuning  – the classifiers will need to be tuned to accurately recognize heads and hands and the baffled omnidirectional microphones’ sensitivities need to be sufficient to offset the short distance between them.

Updated Gantt chart:

Gauri’s Status Report for 03/28

Gauri’s Status Report for 03/28

This week we met on Monday to research what to do about the microphones and finally ordered 4 cheaper omnidirectional ones.  We decided that making baffles around these would be a better idea than buying 4 super expensive cardioid singing mics.  On Wednesday we met 

03/25

03/25

Met with Professor Sullivan and Jens and went over our SOW and Design Review Report feedback. Professor Sullivan suggested a couple very useful things for the mics: Use egg cups + Styrofoam padding + plastic cup padding to make the baffles Try playing with the 

03/23

03/23

  • Ordered 4 Adafruit mics from Amazon, emailed Jens and Quinn requesting that they place order asap
  • Most online vendors have stopped shipping
  • Because of this we can only get 4 mics – change plan to hardcode one COMOVO as the one that can do automatic mode
  • Neeti – getting kaggle datasets
  • Shrutika – getting Matlab/Simulink
  • Gauri – starting control loop and integration
Shrutika’s Status Report for 03/21

Shrutika’s Status Report for 03/21

This week was our first week of virtual meetings. Definitely an adjustment, but I think we have a solid plan going forward. We’re definitely rushed for time since we lost a few weeks with restructuring project virtually and waiting for our parts to ship, but