Posted on

Yuma’s Status Report 4/27

Accomplishments This Week

This week I worked on finishing the final slides and presenting them. I was able to make a little progress on the UI though a few issues in terms of the shutting down modules started bugging out so I was distracted fixing them. This was mainly due to a compression issue in json which uncompressed, was not able to cast into the list I wanted it to be.

Project Schedule and Progress

Schedule moving fast, and I am making good progress. A main concern is about finishing all the deliverables on time before the demo while balancing finals studying for other classes.

Goals for the Next Week

I will work to complete the product in terms of software integration.

Posted on

Yuma’s Status Report for 4/20

Accomplishments This Week

I was able to figure out how to determine unique codes for each processor so that on times of restart, its respective data would be sent back. As of now, I am using the mac address to distinguish scanner modules, and it is working fine. I also have been integrating the UI with the system, which has been a roadblock. I have no experience, and it has taken a while refactoring code so that the UI display (using the tkinter package) would function. For example, the display needs to be on the primary thread whereas all the other threads (i.e. reader/writers) are on auxiliary threads. New listeners needed to be spun off for communicating with the display, which has taken a lot of time doing. I also fixed a couple bugs with the recommendation algorithm, which used to not properly calculate the timedelta value for the weights (i.e. ExpDate and ScanDate).

Project Schedule and Progress
Progress is strong, and I have accomplished what I expected. I have yet to fully integrate and create the UI and OCR, though the OCR is roadblocked by my fellow team mate. I have yet to integrate the temperature sensor as well since the other components take priority. The division of labor does feel very unfair when I clearly have a lot of work and my teammate is on his phone the entire capstone period. I will try my best, though.

Goals for the Next Week
I hope to keep integrating the UI, and hopefully the OCR once its API has been given to me.

Some new knowledge I needed to learn in order to complete the project was dealing with the UI. I think that like many things, immersing yourself in the subject matter is the best way to learn it. Therefore, I looked up youtube videos on how to do UI, looked up articles, and looked at the relevant information. I also talked about it with my friends and about smart strategies implementing listeners on the front end. I thought that this process helped me acquire the skills very rapidly, and was able to apply them to this project.

Posted on

Team Status Report for 4/20

Risk Identification and Mitigation Strategies
Primary Risk Concern: Our primary concern is the OCR finishing on time. This module of the project has been in the work for a while but we underestimated how long it would take for it to finish. Although this would be put as our priority for this week, Yuma still would need to integrate it into the code once its finished, taking more time.

Mitigation Measures:
Yuma will be solely focused on finishing the main module, and Jason will be solely focused on finishing the OCR.

Project Design Updates
As of the current reporting period, there have been no modifications to the initial design of the project.

Validation

For validation, the points remain from last week’s status report. One new aspect that I forgot to consider is validating our display. As of right now, the testing setup is a jumble of buttons and in order to meet the usability requirement, we hope to declutter and make the display more prettier. We will try to hit this requirement along with the other tests and metrics we hope to hit, mentioned in last week’s status report.

Schedule and Timeline
We are a little lagging behind the schedule but we do have enough complete for the final presentation and should have all of the remaining tasks done by demo day.