6 ms·
Saving Voyager 1 [video]
- sho_hn 2y agoObligatory link: https://www.imdb.com/title/tt17658964/ https://www.imdb.com/title/tt17658964/
- jgalt212 2y agoI have not see the posted video, but this documentary, It's Quieter in the Twilight, was great. The Farthest was also excellent. https://www.pbs.org/the-farthest/ https://www.pbs.org/the-farthest/
- qingcharles 2y ago+1 to this
- gorbot 2y agoNeat!
- divbzero 2y agoWow, just incredible. We have the Story of Mel from the 1960s, but this story of saving Voyager 1 is hard to beat and will hold a special place in programming lore.
- ballooney 2y agoAbsolutely and completely fascinating and highly worth a watch. Reminds you how glorious engineering can be.
- ngcc_hk 2y agoThat is what hacker for.
- ngcc_hk 2y agoAnd there should be an emulation environment for us to try and understand the details. Unlike the moon landing controller it is still alive …
- rep_lodsb 2y agoApparently they don't have a lot of the details either, and may not even be allowed to make some of what they have public? Note the line at the bottom of the presentation: "This document has been reviewed and determined not to contain export controlled CUI."
- qingcharles 2y agoAlso none of the software at least is public domain. It was developed by CalTech and somehow it is insulated from FOIA. (Normally work done by contractors on behalf of a government agency is property of that agency)
- acidburnNSA 2y agoAmazing talk. It kind of sounds like they don't have some kind of Voyager computer emulator? I find that hard to believe?
- divbzero 2y agoSounds like they didn't even have perfect records of what software was deployed while they were trying to resuscitate the spacecraft? Because software deployed over the years to the same limited memory overwrote previous versions of software. Eventually they managed to get that memory dump (from a fail-safe and/or plain luck) which probably gave them a clearer picture of what they were dealing with.
- rcxdude 2y agoThey didn't even have perfect records of what hardware was deployed. They had to risk assess what version of the instruction set it was running!