Submission information
Submission Number: 213
Submission ID: 5998
Submission UUID: 87b196d1-b8c5-43b0-990f-352a3ba18095
Submission URI: /form/project
Created: Fri, 01/30/2026 - 08:26
Completed: Fri, 01/30/2026 - 08:26
Changed: Tue, 03/03/2026 - 11:57
Remote IP address: 2601:541:1000:4570:182a:93e:6a86:557a
Submitted by: Benjamin Ford
Language: English
Is draft: No
Webform: Project
| Received Sent | 1 |
|---|---|
| Accept and Publish Sent | 1 |
| Project Title | Old Ships and New Tech: Finding Great Lakes Shipwrecks with Machine Learning |
| Program | PA Science |
| Project Image | |
| Tags | |
| Status | Recruiting |
| Project Leader | Benjamin Ford |
| nywq@iup.edu | |
| Mentor(s) | |
| Student-facilitator(s) | |
| Mentee(s) | |
| Project Description | There are an estimated 6000 shipwrecks on the bottoms of the Great Lakes, of which thousands have yet to be located. The traditional methods to locate shipwrecks require many hours of searching the bottom along narrow swaths. The advent of multibeam sonar technology has allowed much more rapid data collection. Within the Great Lakes, large areas of the lake bottoms have been recently surveyed by the National Oceanographic and Atmospheric Administration (NOAA) using multibeam sonar in support of new and planned National Marine Sanctuaries. The amount of data collected in these surveys has overwhelmed the ability of the available experts to analyze the data in real time, so that large portions of the lake bottoms are recorded but not analyzed for shipwrecks. Applying a machine learning approach to identifying shipwrecks within these data would benefit NOAA, Great Lakes archaeologists, and maritime archaeology broadly. Developing a technique that utilizes the multibeam sonar data, including backscatter data, to identify shipwrecks will create a more complete record of the cultural heritage resting on the lake floors. There are sufficient known shipwrecks in the data to train and test a model that can then be deployed throughout the remaining data to identify previously unidentified shipwrecks. These shipwrecks are claimed by the federal government under the Abandoned Shipwreck Act and the responsibility of state and federal governments to manage. Effective management begins with identifying the shipwrecks. Once identified, the shipwrecks can be analyzed by an archaeologist for their potential to inform our understanding of the past. A model developed for the Great Lakes could be employed more broadly to identify shipwrecks in other regions, greatly improving our ability to manage and interpret humanity’s shared history. Shipwrecks include information about technological changes; in many cases they were the space shuttles of their time, carrying humans into unknown and inhospitable environments and capturing the attention and talents of the most innovative thinkers of the day. Shipwrecks are also time capsules that can tell a largely complete story about the resources and priorities of people in the past. They are also touchstones for many people, allowing a connection to their ancestors as well as the struggle between humans and larger forces. Shipwrecks are also an excellent means to study chemistry, biology, and geology as they become part of the surrounding environment, and offer opportunities to engage the public in these topics as well as mathematics and other STEM fields. All of this begins with finding the sites. Expected outcomes would be one or more conference presentations and a co-authored, peer-reviewed publication. Collaborators will include Dr. Samuel Griegs (Indiana University of Pennsylvania) and Dr. Benjamin Ioset (National Marine Sanctuary Foundation). |
| Project Deliverables | |
| Project Deliverables | |
| Student Research Computing Facilitator Profile | |
| Mentee Research Computing Profile | |
| Student Facilitator Programming Skill Level | |
| Mentee Programming Skill Level | |
| Project Institution | |
| Project Address | |
| Anchor Institution | |
| Preferred Start Date | |
| Start as soon as possible. | No |
| Project Urgency | Already behind3Start date is flexible |
| Expected Project Duration (in months) | |
| Launch Presentation | |
| Launch Presentation Date | |
| Wrap Presentation | |
| Wrap Presentation Date | |
| Project Milestones | |
| Github Contributions | |
| Planned Portal Contributions (if any) | |
| Planned Publications (if any) | |
| What will the student learn? | |
| What will the mentee learn? | |
| What will the Cyberteam program learn from this project? | |
| HPC resources needed to complete this project? | |
| Notes | |
| What is the impact on the development of the principal discipline(s) of the project? | |
| What is the impact on other disciplines? | |
| Is there an impact physical resources that form infrastructure? | |
| Is there an impact on the development of human resources for research computing? | |
| Is there an impact on institutional resources that form infrastructure? | |
| Is there an impact on information resources that form infrastructure? | |
| Is there an impact on technology transfer? | |
| Is there an impact on society beyond science and technology? | |
| Lessons Learned | |
| Overall results |