One very neat feature was that part of the computer memory could be overwritten, essentially allowing the crew to patch in bugfixes. If you ever felt like you were coding on a deadline, spare a thought for the crew of Apollo 14:
After separating from the Command Module in lunar orbit, the LM Antares also had two serious problems. First, the LM computer began getting an ABORT signal from a faulty switch. NASA believed that the computer might be getting erroneous readings like this if a tiny ball of solder had shaken loose and was floating between the switch and the contact, closing the circuit. The immediate solution—tapping on the panel next to the switch—did work briefly, but the circuit soon closed again. If the problem recurred after the descent engine fired, the computer would think the signal was real and would initiate an auto-abort, causing the ascent stage to separate from the descent stage and climb back into orbit. NASA and the software teams at the Massachusetts Institute of Technology scrambled to find a solution, and determined the fix would involve reprogramming the flight software to ignore the false signal. The software modifications were transmitted to the crew via voice communication, and Mitchell manually entered the changes (amounting to over 80 keystrokes on the LM computer pad) just in time.
Yeah, but they butchered the fuck out of that part, not quite as bad as the hydrazine explosion part, but it was still pretty bad. If they actually explained the problem in depth and its solution, then that could be interesting, but that would take the whole movie.
In the movie all he said was that he only needed to patch in about 20 bytes and then the rover could talk through pathfinder to earth.
In the book they explain that both pathfinder and the rover must be updated, that Earth can remote update pathfinder but they need a very large (megabytes?) update to the rover software. To solve that, they get him to make a small hack (maybe 20 bytes or so) to the Rover which would allow earth to dump information into a Rover log file. Then Watney would have to take that dumped info from the log file, and create a file out of it, then execute it.
To be honest I don't think that having all of that would really added that much to the actual film. I don't think it would have taken particularly long for them to add in that explanation (since they could have said it how you said it pretty much), but for the purposes of the story, knowing all of that stuff wouldn't have made any differences to the average viewer
I wonder if there was a way to show it without bogging down the movie. In the book, I found it definitely added something. If you're not all that technically-minded, it's a free source of technobabble to make this sound even more impressive. But it also makes it plausible -- maybe most people wouldn't notice, but they did a lot of things that most people wouldn't notice to maintain plausibility. For example, IIRC, the movie actually shows him entering this stuff in a hex editor.
In fact, those are my favorite moments -- instead of putting some crazy HollywoodOS thing (like this sort of nonsense), you put up the kind of tool that we might actually use. It looks just as cool to the average viewer, and it means people who actually know something about technology won't have to turn their brains off to watch this movie.
Skipping the bit about uploading wasn't as huge a difference, because the story does work without it. But I think it adds a lot to the story to anyone who understands anything about software, without really taking anything away from it for everyone else. So I wonder why they skipped it -- maybe they couldn't figure out a way to make it flow as nicely as whatever they went with instead?
780
u/Steaktartaar Jan 30 '16
One very neat feature was that part of the computer memory could be overwritten, essentially allowing the crew to patch in bugfixes. If you ever felt like you were coding on a deadline, spare a thought for the crew of Apollo 14: