Month: March 2025

Emma Status Report (3/15)

Emma Status Report (3/15)

This week, I have spent my time developing the computer interface with Tkinter and the back end connection between the GUI and Raspberry Pi. I am using a socket server to connect the Raspberry Pi and computer, which allows the computer to send commands to 

Maddie Status Report (3/15/25)

Maddie Status Report (3/15/25)

This week has definitely been a bit slower than I intended. I’ve faced some issues with parts being ordered/delivered, which has slowed progress on working on the Z-direction movement. That being said, I have constructed a makeshift spool which should allow for us to still 

Maddie Status Report (3/8/25)

Maddie Status Report (3/8/25)

Over the last two weeks, most of my time went towards working on the design report, as well as continuing to work on the image stitching algorithm. Because of some travel hiccups, I did not get everything that I planned in my last status report completed. That being said, I largely have a program which can take in a folder of ordered images and stitch them together horizontally and vertically to create one cohesive image! The shortcoming of this week was that I didn’t get to spend as much time thinking about image stitching validation as I would have liked. This is a goal for next week, as well as beginning to write code which automatically captures images with adequate overlap during a livestream process. I plan to do this by calculating the dimensions of the camera’s view based on the z-direction’s position, and using this figure along with the boat’s speed to determine the necessary image-capture interval. 

 

On the other side of the project, I’ve continued to look into the spool / wind guide component of the project, and hope to have these 3D prints submitted to techspark by the end of the week. These parts will be largely adapted from Thingiverse parts, but will need to be significantly modified and rescaled as most open source parts are intended for 3D printer filament, which is a significantly larger spool and smaller “thread” than our cable. 

 

Overall, I am a little behind where I would like to be. That being said, I’ve been able to block out adequate time this week to make up for being able to do less than I planned since the last report 🙂

Emma Status Report (3/8/25)

Emma Status Report (3/8/25)

This week I worked on setting up the motors for the boat. I soldered the wires to the motors, set up the circuit with the motor drivers and the Raspberry Pi, and turned the motors on and off using remote terminal commands. I also spent 

Abigael Status Report (3/8/25)

Abigael Status Report (3/8/25)

This week I worked on figuring out how to process images in python for the ML color detection algorithm. I was able to get the RGB pixel value from a JPEG image using the Pillow library and from this step am able to self group 

Team Status Report #4 (3/8/25)

Team Status Report #4 (3/8/25)

This week (3/2-3/8) our team enjoyed a super fun spring break! Prior to that (2/23-3/1), we focused on finalizing our design details and plan in the design report. Emma set up and tested the motors for the boat, Maddie worked on the image recombination code, and Abie worked on the color sorting algorithm. As a team we are on schedule and do not anticipate any risks going forward.

 

Part A: (Emma) Our design and product takes into account several global factors. First, coral reefs exist all over the world, and all reefs are equally important to protect. Our technology is not reliant or determined by United States regulations or standards. Our core processor, the Raspberry Pi 4, is certified for use in 55 countries across 6 continents (excluding Antarctica). Additionally, we are aiming to design our boat such that the user never has to take out the Raspberry Pi from its waterproof casing and allow easy access to necessary sections of the Pi, including the power supply and SD card. We also will be making the front end of the application easy to use so that the user does not have to be an expert with Raspberry Pi code to execute the research.

 

Part B: (Maddie) Our product solution is designed in such a way that doesn’t present many possible issues related to cultural traditions or beliefs. Many regions have developed their own specific knowledge and systems for conservation; our device supports these practices, most notably through having a user-driven navigation system (rather than being autonomous) as well the ability to take photos and notes on demand in the interface enables users to continue monitoring reefs as they choose. The nature of the Reef Rover is primarily as a tool for conservation, meaning that scientists and other operators can use it flexibly. Additionally, because of Reef Rover’s speed, size, and non-invasive design, we’ve worked to minimize the impact that our product could have on fishing and other maritime traditions. Lastly, we do not believe that there are any laws or restrictions that would impede the use of Reef Rover – it is more common for restrictions on human diving or large-scale robotic operations, due to the risk they pose to the delicate reef. Our device is designed to be operable under any set of common restrictions for conservation, making it more accessible legally than other forms of monitoring. 

 

Part C: (Abie) As a project, Reef Rover was designed with the intention of assisting scientists in monitoring the health of coral reefs across the globe. Our product is primarily suited for shallow water coral on the coastlines, which make up the majority of all coral reefs. Coral reefs also serve as the habitat to approximately a quarter of all marine life, and over half of all shallow water coral have been destroyed as a result of global warming. In their efforts to conserve these vital ecosystems, it is imperative that scientists have access to reliable data, and that they are consistent in the measurements recorded across all coral reefs studied for comparison purposes. Reef Rover eliminates the need for a human diver to survey the area, reducing risks to both the divers and the delicate coral. Earlier renditions of our design featured a crawling device, but in order to maximize the non invasive nature of our robot, we altered the original plan to create a two part boat and submersible that will not make contact with the coral. Additionally, our design records water temperature and pH and uses video captured during transversal of an underwater area to create a comprehensive map of the coral reef system as well as its level of bleaching to a higher degree of accuracy than current satellite imaging. This complete set of data will help scientists to more efficiently study and protect our ocean environment.