This week our group presented, and finished the presentation. However, I did not present, I worked on the programming for accepting information from a Raspberry Pi and will test it on a Raspberry Pi from lending this week. I will not be able to run it on the Raspberry Pi we will be using for our project as it is still not been delivered yet. We are not on schedule as our parts have not arrived yet so we have not begun assembling the glove. However I will continue to do as much work on the software without the hardware as I can. I will also be working on the Design document this week.
Teadora’s Status Report 2/21
This week I worked on the design presentation, then presented it on Monday. To get ready for the presentation, I had to confirm several details about our solution approach, like which protocols and languages we’ll use for the ASL glove. I also ordered more parts and worked with Quinn to handle a supply issue. The supply issue has me concerned that we won’t have parts before Spring Break, which would push us back 2 weeks. If the parts are here this week, I’ll test them to make sure I can get data out, attach them to the glove, and start figuring out what formulas we’ll use to convert sensor data into reasonable measurements / sign classification.
Katherine’s Status Report 2/14
This week, I worked on the design slideshow and the planning of our project. I started researching how we will accept and process serial information from the raspberry pi. We are behind schedule as we did not order the parts until this week but ideally our sensors and glove arrives soon so we can start the assembly of our glove. In the meantime as I stated I will continue to work on the data transmission to the machine learning model and determining which ML model we will use.
Nia’s Status Report 2/14
This week, I worked on ordering parts for our prototype. Specifically, I ordered the gloves and began research on what monitor we want to use to display our UI. I also created our GitHub and began planning our ML model system design.
Our progress is a bit behind schedule as we hope to begin collecting data before spring break. We are still waiting for our sensors to arrive and then we can begin test such as number of sensors per finger.
Teadora’s Status Report for 2/14
This week I ordered the first set of parts for the glove (Spectra Symbol Flex Sensors), and looked into other parts. For example, I looked at the datasheets for several different IMUs Adafruit sells to consider how much data we need (ex: do we need magnetic field sensing? Probably not, and it’ll save us $5 on budget). I’ve decided to use a Raspberry Pi Pico 2W since it’s lightweight and has WiFi and Bluetooth capability. We borrowed a Raspberry Pi 5 (8Gb) from lending, but it won’t work for the final model since it’s too big. We’ll also need a monitor and keyboard to interface with it, which we need to get from ITS. I also worked on the Design Presentation
Team Status Report for 2/14
Like last week, there are no significant risks at this stage. We’re in the process of ordering parts, trying to balance getting enough parts early while not blowing our budget if the parts aren’t right. However, we have a pretty good idea of which specific parts we need at this point. We need to look into software choices soon, including how to receive data and use it to build the model.
Part A was written by Nia
Our project aims to improve welfare by providing education to all for learning ASL and increasing fluency. We’re taking into account safety by ensuring batteries that won’t overheat during use.
Part B was written by Teadora
The product solution we’re designing meets needs for social factors. ASL (and other sign languages) are a large part of the deaf community, and it’s common for signed languages to be a child’s first language, especially if people in their family are hard of hearing. Learning sign language can also be useful for older adults since hearing loss can occur later in life, especially as a complication of other health concerns. In recent years, it’s become more common to see sign interpreters in everyday events, like concerts, government press briefings, and other events with live speakers. While sign language interpreting is a complicated skill that takes many years to master, learning sign language is an important way to connect with the deaf community and create accessible environments. Our solution will help people learn ASL and facilitate communication between different cultural groups.
https://www.asha.org/siteassets/ais/ais-comorbidities-and-hearing-loss.pdf
https://signhealth.org.uk/resources/learn-about-deafness/deaf-or-deaf/
Part C was written by Katherine
The economic factors are important as there are many versions of our product that are similar being built so it is very important we create a cheap and easily accessible one. Our production should be high quality and also cheaper than other products. As for distribution we want it to be easily accessible which we are demonstrating by creating ourselves with parts we order ourselves.
Nia’s Status Report 2/7
This week, I presented our project proposal. I mainly worked on preparing our slides to be readable for the audience. In addition, I worked on preliminary research on the available parts list. Lastly, I began brainstorming the user interface of our application and how e can create positive feedback loop to our machine learning algorithm.
Our progress is on schedule. We hope to have ordered parts by the end of next week and to have found public datasets for our model.
Team Status Report 2/7
There are no significant risks at this stage. We need to order parts soon and get moving quickly so we don’t experience delays. We’ll mitigate this risk by ordering from preferred suppliers and ordering enough materials in case something breaks. The things that could jeopardize us are not ordering the right parts or not ordering them soon enough. Therefore we are being very intentional about picking our parts while intended to order parts this upcoming week.
The plans that we are ready to execute are to order the flex sensors and IMU when we get access, and to decide on the specific model of Rasberry-Pi we are going to use. The features we are looking for are, bluetooth, wifi and lightweight. There are no changes that need to be made or that have been made for the existing design system. We are still using the same design that we presented on our proposal slides.
Kat’s Status Report 2/7
This week the team worked on the project proposal, I worked on the gaant chart and software requirements slides. We have not ordered our parts yet, however we have a good idea of the parts we need to order and will do soon at the beginning of next week. I specifically want to work on research of the machine learning datasets and classifying data of 3-dimension signaling. I also want to practice with some parts from inventory for the hardware to software communication.
Teadora’s Report for 2/7/2026
This week I contributed to the project proposal, specifically the slides explaining hardware. I also did the website setup. I think we are slightly behind schedule since we haven’t ordered parts yet. We will resolve this by ordering parts online and from the inventory in our Monday meeting. I want to work on board to computer console communication this week since we can get a RPi from inventory and play around with it while waiting for flex sensors.