SpaceX Launch To International Space Station Delayed For Code Tweaks
RogerRoast writes "The first private spaceship launch to the International Space Station has been delayed, possibly by at least a week, the vehicle's makers announced Monday. The commercial spaceflight company SpaceX was set to launch its Dragon capsule atop a Falcon 9 rocket April 30 from Cape Canaveral Air Force Station in Florida." The article quotes SpaceX lead Elon Musk's twittered explanation: "Am pushing launch back approx a week to do more testing on Dragon docking code. New date pending coordination with @NASA."
Maybe the just noted half the libraries were in metric
"Last minute code tweaks" never go well.
When Fascism comes to America, it will call itself Anti-Fascism, and tell you to give up your guns.
Better they found it now and missed the deadline than went anyhow and exploded. You do not get too many second chances in space.
Cowards!!! Launch early, launch often. (Or just give the coders the honor of being test pilots. That will make those code monkeys program it real good the first time...)
Space travel has a long history of "extremely rare if not practically impossible" issues coming up to bite you. Missions have been lost because of a single missing comma in the code. So, there is reason for this caution, and neither you nor Elon Musk is going to be able to change it.
im sure you'd see git comments like
--removed sound-activated LED code
restored sound activation code. needed for espresso.py
--removed callbacks, class for rancilio espresso maker. please stop this.
--added pizza ordering support for dominos, stub for pizza hut
--removed food related code for pizza, chinese food, references to 'the luther'.
-- removed orbital re-entry positioning code. two can play this game
-- re-added orbital code. this is not funny. please stop.
-- added DMX512 dance-floor lighting control module, arduino support for twitter potted plant control
Good people go to bed earlier.
Life support systems require more rigorous testing than simple Monte Carlo. They generally require component testing, bounds case testing, and branch path analysis of the code so that every line of code gets hit during testing.
I've worked on two projects that qualified as life support systems; one was an MRI console for a GE Medical Systems MRI machine (back when it was still being called NMR before it was politically corrected to remove the word "Nuclear"), and the second was a blood gas analyzer. Incorrect operation of the code in either of those cases could have resulted in someone dying as a result of a doctor getting misinformation.
The amount of testing and the rigor of the testing involved in both of those projects was unbelievable. Even then, we were required to carry liability insurance out the wazoo on both projects in case we screwed up the code. There's a reason medical equipment is so expensive.
Space systems that can ram into an occupied space station, and which are intended to some day carry humans to orbit qualify as life support, even if they are being sent up with a load of supplies instead of a human crew. Monte Carlo won't cut it any more than it will for a system call fuzzer trying to find a sequence of three system calls in a row that , if they are called with precisely the right parameters, will trigger a kernel panic.
-- Terry
NASA and Russia are extremely cautious when it comes to anything ISS-related for very good reason. If this thing really screwed up and seriously damaged ISS to the point where they had to abandon it, it would probably end the era of human spaceflight and lead to big budget cuts for both agencies.
What political party do you join when you don't like Bible-thumpers *or* hippies?
No where in Elon's Tweet or in the referenced article does it say they need to tweak the code... it says they need more time to "test" it.
Bill
It's my Sig and you can't have it. Mine! All Mine!