Dhruv Status Report – 4/12/2025

Accomplishments this week:
This week I focused on connecting the backend pipeline to the to the frontend. This involved a lot of effort in changing the structure of the code to match the frontend. We know have a working calendar view with configurable settings and generated diary entries. Now, whenever a picture is taken, it dynamically gets added to the website. In addition to this, Will and I worked on location. We realized the GPS is not great so we are going back to using the Blue’s Notecard. We also all 3D printed the casing for our parts.

Reflection on schedule:
I need to focus on helping integrate all the parts together and start testing. We are behind the schedule as we should have started testing.

Plans for next week:
Finish entire pipeline and start testing.

Verification Plans:
To verify that my part works as expected. I have built a simulator to simulate location changes using my arrow keys. I am using this to simulate the entire pipeline of picture taking and website updates. So far, it is working correctly. Once, we have the location working, we will verify location by walked certain distances and comparing coordinates with our phone. We will make sure it is within the 100 meter radius. We have already tested camera capture and network connectivity.

Dhruvs status report 3/29

Accomplishments this week:
This week I made a lot of progress. I worked on the raspberry pi and got the camera working and automated picture taking. We ran into many issues with trying to communicate with the pico and connecting the blues to the pico. Therefore, I decided to set up a Hive broker and use MQTT to send images and receive commands. I also connected this to my existing application and now whenever i am stationary in a new location for 10 seconds, it publishes a capture command to Hive. The pico is subscribed to the command topic and initiates a picture capture. After the image is taken, it publishes it to an image topic. My laptop is subscribed to this topic and downloads the image to a local directory. This is then connected to the backend pipeline to summarize and create a diary. Will and I also got the blue’s notecard set up and can now send us location data based off a command.

Reflection on Schedule:
I am ahead of schedule and have mainly finished all my parts.

Plans for next week:
Since I have done a lot of the early work on my part, I will continue working on the hardware. We will focus on automating location next and then full integration.

status report march 22nd – dhruv

Accomplishments this week:
This week I did a lot of work on the hardware software integration of our project. First, I worked on being able to send a signal to the raspberry pi pico from my laptop. I was able to do this through a serial connection. In the future, I want to be able to do this through MQTT. Then, William and I were able to work on the arducam. Will was able to connect the arducam to the raspberry pi pico. Then we worked together and read through the docs and were able to capture an image through the arducam. Overall, good progress was made!

Reflection on Schedule:
I am ahead of schedule now and have finished a large portion of the early developments of my part for the software back-end and begun working on the hardware software integration.

Plans for next week:
Since I have done a lot of the early work on my part, I will continue working on the hardware. I will be trying to set up MQTT and also sending GPS coordinates.

status report march 15th – Dhruv

Accomplishments this week:
This week I did a lot of work on the software back-end. Specifically, I spent a lot of time coding the location change detection program and got it working. I made a dummy website to show the model of this working. I have a map with a user that can be controlled by arrow keys that shows this program working. When the user becomes stationary, a signal to capture an image is sent and I use a vision model to get details about the image. I store all these details in a string and send these to an LLM (Open AI API) to get the summary.

Reflection on Schedule:
I am ahead of schedule now and have finished a large portion of the early developments of my part for the software back-end

Plans for next week:
Since I have done a lot of the early work on my part, I will be working on the hardware next week. In specific, I will be working on getting the arducam set up with Will.

status report 3/8/25 – Dhruv

This week I worked on the raspberry Pi Pico, blue’s notecard, and arducam to learn how to set it up. I learned what all the pins do and how to connect each one together. I also spent a lot of time working on the paper that was due. I spent time researching section 6 and 7. I have also been working on setting up our AWS. I am configuring all the roles and IAM permissions we will need for this project. I have also been working on our location change detect function and will be testing it soon when we get the hardware side working. Overall, I believe I am slightly behind schedule but can catch up soon.

Dhruv’s Status Report for 2/22/2025

This past week I spent time doing research on the software block diagram of the project. We realized this project is much more complex than we originally thought. The main concern I was researching was how to transfer images from the glasses to the cloud. My original idea was to do it through the blue’s notecard onto notehub which can connect to AWS. However, I found out that blues notecard cannot send large files and instead needs to send images in chunks. We can also send through raspberry pi but after research, I was not able to find out how large of an image we can send. Therefore, we are going to have to do tests to determine what size of image we can send. If we cannot send a large image file, we will try to compress our image down to 8kB as that is the max file size we can send in one chunk through blues notecard. I also practiced my presentation this week as I presented on Monday. We have also received our parts and I have begun brainstorming on how I will start the implementation. I am going to start with the image capture trigger as that is the start of the software pipeline and work from there.

Dhruv’s Status Report – 2/15/2025

This week I did a lot of work on the design proposal and researching the pipeline of the software section. In specific, I researched the blues notecard and raspberry pi nano and realized that they run on a voltage between 1.8 and 5.5 and need an average voltage of 3.7. I also finalized that location coordinates are continuously sent to AWS and if the distance from start point is greater than 20 meters, a signal is sent to a lambda which executes a picture capture. This will be done by setting up an AWS IOT endpoint. Once the image is captured, it will be sent back for storage in AWS S3 and will be tagged with location and time. Whenever the user requests an LLM summary at the end of the day, we will query a fine tuned LLM (llama 3.2) and return the output to the user. I also worked on the design presentation such as making the design for the software side. I am also presenting today so I practiced what I am gonna say and also prepared potential questions I could be asked.

Status Report – Week 1 (Dhruv)

This week, I did a lot of work on the slides and presentation. I spent many hours researching the design of our product to figure out what devices to use. In particular, I spent time researching how to have constant connectivity to the cloud to have continuous image transmission. I also spent time refining the requirements for our hardware and software.

My role on our team is on the software side. Therefore, I also spent time researching how the location would work and designing the system for getting images processed. In particular, I decided that we would like to use something like AWS S3 to store compressed images daily. When the user wants their summary, a function will fetch all files under the S3 folder for the current day and feed it into a multimodal LLM to handle summarization. We will also tag each image with a timestamp and google maps location to get an accurate summarization of the day!

Other than working on the slides, I began to brainstorm on how exactly to attack this problem. We also began thinking of what orders to put in for our device.