So I've been half-watching the Mars stuff for the last week and a half, mostly out of the corner of my eye between actual work, and the thing that got me wasn't the landing footage (which yes, incredible, the "seven minutes of terror" video is still on my second monitor in a loop) — it's what NASA's been doing to Curiosity's brain over the last few days.
Quick recap for anyone who's been off the grid: Curiosity touched down on Mars August 6th. Since then the JPL team has basically been doing a full OS swap on a two-billion-dollar rover sitting 154 million miles away, one command at a time, each of which takes about fourteen minutes just to arrive. Not fourteen minutes round trip. Fourteen minutes ONE WAY. So you send a command, you wait almost half an hour to find out if it worked, and if it didn't, well, tough, try again tomorrow because the Deep Space Network has other stuff to talk to too.
The rover landed running "EDL software," which is the stuff built just for entry, descent and landing, all the parachute and sky-crane and rocket-powered hover nonsense that had everyone at mission control chewing their fingernails off. That software isn't what you want running the rover for the next two years of actually driving around and drilling rocks, so this week they've been swapping it over to the surface ops build. It's not a reboot, it's not "click restart and grab a coffee." It's methodical, slow, and if something goes wrong there's no rebooting into safe mode with a USB stick. You get one shot and thirteen straight minutes of dead air before you know if you bricked a national space asset.
I complain constantly about my home router taking four minutes to apply a firmware update and drop my connection for ninety seconds in the process. My Galaxy Nexus sat there "verifying update" for what felt like an hour last month and I nearly threw it across the room. Meanwhile these guys are patching an operating system on another planet with a comms lag longer than most of my meetings, and nobody at JPL is panicking on Twitter about it, they're just calmly running the checklist. Puts things in perspective, a little.
The other thing that happened this week, smaller and honestly the detail I like more: NASA officially named Curiosity's touchdown spot "Bradbury Landing," after Ray Bradbury, who died back in June. It's a strip of Martian gravel that's now got a science fiction writer's name stamped on it permanently, which feels exactly right for a mission that's basically living out the plot of half his short stories. I went and reread "The Martian Chronicles" opening chapter after I saw that, first time since high school. Holds up better than I remembered, though some of it reads pretty differently now that there's an actual nuclear-powered robot rolling around out there instead of little green telepaths.
None of this is the flashy stuff — no rocket landings, no parachutes, just a team patiently pushing bytes across the solar system and waiting. But it's the part of the mission that actually tells you if the thing works long-term, and it's the part most coverage skips because "engineers wait fourteen minutes for a status ping" doesn't make for good TV. I think it's the best part though. It's the unglamorous grind that decides whether two billion dollars and eight years of work turns into two years of real science or a very expensive brick on a red rock.
Curiosity's still got test drives ahead before it starts doing anything with that laser or the drill, and from what I've read the team wants everything squared away on the software side before they let it roll more than a few meters. Which, fine, take your time. I'd rather wait an extra week than have someone's Mars rover get bricked because they rushed a patch, the same way I'd rather my phone update slowly and correctly than fast and broken, except apparently my phone hasn't gotten that memo yet either.
Anyway. Back to actual work. My router's still due for that firmware fix and unlike JPL I don't have a backup rover.