Abstract
Large scientific collaborations, often with hundreds or thousands of members, are an excellent opportunity for a case study in best practices implemented while developing open source hardware. Using a publicly available design of timing equipment for gravitational wave detectors as a case study, we evaluated many facets of the open source hardware development, including practices, awareness, documentation, and longevity. Two diverse student teams, composed of high school and college students, participated in an end-to-end exercise of testing publicly-available documented hardware that originated from more than a decade ago. We found that the primary value of large collaborations lie in the ability to cultivate teamwork, provide a diverse set of role-models, and explore the possibilities of open hardware development of varying complexities. Learning from the experiences of the student groups, we make constructive recommendations where the open source hardware community can learn from the collaborations and vice versa.
Introduction
Large scientific collaborations like LIGO are often mandated to make their hardware designs open-source, especially when funded by taxpayers. However, there is a significant gap between making files "publicly available" and making them "reproducible." This paper addresses the challenge of documentation longevity and accessibility. Hardware designed by experts for experts often relies on institutional knowledge, proprietary software, and obsolete components that vanish over time. This study investigates whether a motivated outsider can actually use decade-old documentation to understand, manufacture, and test complex scientific instruments.
Methodology
The researchers designed an "End-to-End Exercise" to stress-test the LIGO Timing System documentation. They recruited two student teams—composed of high school and undergraduate students—to act as "proxies for the public."
The exercise involved several key phases:
- Documentation Retrieval: Searching the LIGO Document Control Center for design and manufacturing files.
- Simulated Manufacturing: Obtaining modern PCB quotes to compare against historical 2017 data.
- Software Migration: Attempting to convert proprietary Altium files to the open-source KiCad suite.
- Physical Testing: Executing original 2010 test procedures on legacy hardware environments.
- Qualitative Assessment: Gauging learning curves through pre- and post-exercise surveys.
Key Insights: Software and Documentation Barriers
A major finding was the role of software as a gatekeeper. The original project's reliance on Altium 2009 created a massive barrier. To even test the boards, students had to find legacy hardware capable of running Windows 7. This highlights that OSHW is only as "open" as the tools required to view it.
Furthermore, documentation is often written for a "tight circle" of peers. Terms clear to original LIGO engineers stalled the student teams, suggesting a need for "simplified" documentation aimed at the general public. The most successful path to resolving ambiguity was direct contact with the original creators, suggesting that OSHW projects require a "social" component to survive long-term.
Results and Discussion
The exercise revealed significant hurdles in modern reproducibility:
- Conversion Failures: Automated Altium-to-KiCad conversion tools were unreliable, necessitating a time-consuming manual process.
- Documentation Gaps: Multi-page schematics often lacked file links, and missing wiring information required extensive "detective work."
- Economic Drift: Custom hardware manufacturing has become significantly less affordable for US-based creators compared to a decade ago, with modern quotes far exceeding historical prices even after inflation adjustment.
Despite these hurdles, the educational impact was profound. Students with minimal prior PCB design knowledge successfully navigated testing procedures when provided with occasional mentor access, proving OSHW's value as a pedagogical tool.
Conclusion and Future Work
While large collaborations offer robust documentation, "bit rot" and expert-bias remain significant challenges. Future efforts should focus on:
- Curriculum Integration: Teaching basic PCB literacy in undergraduate science programs.
- Firmware Maintenance: Strategies to prevent OSHW projects from becoming locked in obsolete operating systems.
- Discoverability: Improving SEO and metadata so projects can be found easily outside internal databases.
Summary updated