CERN OPERA experiment 'faster-than-light neutrino' measurement error
An experiment at the OPERA facility in Italy appeared to show neutrinos traveling faster than light, a result that would have upended a century of physics, before the team found and corrected the error themselves.
The damage was public. The root cause was preventable.
An experiment at the OPERA facility in Italy appeared to show neutrinos traveling faster than light, a result that would have upended a century of physics, before the team found and corrected the error themselves.
What the software actually got wrong
A fiber-optic cable connecting a GPS receiver to the experiment's timing system was not fully screwed in, introducing a small but critical delay into the very precise time measurements the experiment depended on, and a related clock oscillator calibration issue also contributed to the erroneous timing data before both were identified and corrected.
A fiber-optic cable connecting a GPS receiver to the...
A fiber-optic cable connecting a GPS receiver to the experiment's timing system was not fully screwed in, introducing a small but critical delay into the very precise time measurements the experiment depended on
Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.
A related clock oscillator calibration issue also contributed to...
a related clock oscillator calibration issue also contributed to the erroneous timing data before both were identified and corrected
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
Beyond code coverage and "shall" testing
Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.
Surfaces this before code exists
Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.
Connects the failure mode to the hazard
Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.
Find the overlooked root causes before they ship.
Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.