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.

Leave a Reply

Your email address will not be published. Required fields are marked *