March 2023

Team Status Report for 3/11

A significant risk we identified was the real-time functionality of our system specifically the radar. We found that our current radar module didn’t support it, but using a different radar module (also from CyLab) would be more feasible. This radar is already procured, so this risk has been mitigated.

The radar change was necessary to support the real-time functionality of our system. This is driven by the use case requirement of our device helping in time-pressured search and rescue situations. No additional cost will be incurred, because it is the courtesy of CyLab. Because this radar is capturing the same data–range-Doppler and range-azimuth coordinates–from an integration viewpoint, it will be the same for the machine learning architecture.

The new radar is certainly a new tool. For the integration of the machine learning architecture with the web application, we identified that Django REST API, because it is compatible with supporting Python programs, which is how the machine learning architecture will be implemented. Lastly, while writing the design report, we realized that there was no clear delineation of when the radar would use the captured data, perform inference, and identify a human. Therefore, we established that we will use the IMU data to determine when the drone has zero horizontal acceleration and is upright and subsequently perform inference on the data by running the machine learning architecture.

By lszabo, ago

Linsey’s Status Report for 3/11

I have helped put together the design review report for its submission deadline and have continued working on the machine learning architecture. For the report, I wrote more general sections like the abstract, introduction, use case requirements, and related work. Much of this was expanding upon our presentation, but I carefully examine the requirements and made sure to hit all the discussion points and reviewed all these sections with my teammates. Additionally, in the other sections, I wrote material pertaining to the machine learning architecture. Again, I built off of the presentation. I did have to organize which of my references pertained to which parts of the architecture and really understand exactly how my part is integrating with Angie’s and Ayesha’s. I also drew out a whole system diagram for the report. For the machine learning architecture, with Angie’s help I labeled each data piece, so that they all have targets. Therefore, I was able to generate train and test sets. I started testing the architecture that I had written out with the training data, but I am working through dimension errors. This will take some shape examination but hopefully shouldn’t be that much of a barrier to further progress.

I am slightly behind, because I wanted to have the machine learning architecture fully training at this point. However, I truly took a break for spring break and will be back on track after overcoming the dimension errors.

I hope to deliver the machine learning architecture fully trained by the end of this week.

By lszabo, ago

Ayesha’s Status Report for 3/11

This past week (before spring break) I accomplished a few things. I worked a lot on the design report. Specifically, I worked on writing the web application portion for the requirements and implementation sections, as well as fleshing out a more clear integration portion for each section. I spent a lot of time writing, revising, and reviewing this document, and it took up the majority of the week since it had so much information packed in. I also wrote some miscellaneous sections like the schedule and created a more clear Gantt chart for the paper, compared to our previous schedule. This week I also looked into purchasing the Google Maps API. This took a lot of time because the educational coupon that was provided was not clear in how to purchase the API with it, and the way to purchase the API was very very complicated. None of the staff was able to help me figure out how to purchase it, so it took a lot of time, and unfortunately I will be paying for it on my own, since that was the only way to make an account and the price exceeds $50. However, I have figured out how to purchase it (I think) and will do that post-spring break so that I can use a 14 day free trial and decrease the price and the amount I have to spend.

 

I am a week behind schedule because I did not account for purchasing the API and having to deal with these minor roadblocks of payment to add so much time. I will make up for this in the week after spring break by just working a bit more. Also, I have prepared for next week by looking into code snippets for how to get the google maps API to work, specifically with the marker functionality. That should reduce the time I have to spend doing that next week.

 

Next week I hope to have successfully purchased the google maps API and tested out some code where I am able to add a marker. In addition, I would also like to clean up the page to display the map with the marker.

 

By ayeshag, ago