Falling back to one processor when the others die is easy. Doing it honestly is the hard part. In our simulator, a last processor that never checks itself gave at least one wrong result on 87% of missions. Ours checks its own work: 80% of the useful work, with 1% of the wrong results.
Mru Aerospace
Systems that still run a thousand years after we're gone.
Latest casts
About 4,000 robot floats drift through the world's oceans. Every 10 days, each one sinks as deep as 2,000 m, rises back to the surface and sends home what it measured. Most are never recovered. The battery decides when the mission ends. The software decides how much good data comes home before then.
Right now, Voyager 1 is one light-day from Earth: 25.9 billion km. A command sent today arrives tomorrow, and the answer takes another day to come back. In 1990, from less than a quarter of this distance, it turned around and took this photo. Earth is the dot in the sunbeam. Image: NASA/JPL-Caltech
The standard way to protect a machine from wrong answers is three processors voting. Once it can't outvote a bad one, it stops on purpose. In our simulator of 1,000-year missions with no repairs, stopping only comes out ahead if a single wrong answer costs more than 136 years of useful work. That's the number worth arguing about.
A pipeline can run for hundreds of kilometers through places where nobody lives, with monitoring stations along the way and patrols weeks apart. If a station's processor starts giving wrong answers, nobody may notice until the next patrol. Mru Field is built to catch it and say so.