Shuttle Assessment Tool was Inferior
An anonymous reader writes " Shuttle report in Houston Chronicle: 'The computer program Boeing engineers used to predict that a debris-damaged Columbia could land safely wasn't much more than a simple chart of past foam damage, accident investigators said Tuesday.'"
Edward Tufte is a demigod in the world of information-design, and he made an interesting case recently that bad PowerPoint design in Boeing's report contributed to the misinterpretation of the analysis. Eg, the way the ppt-slide was laid out almost completely concealed the fact that the test was on a small cube of foam.
Shuttle report in Houston Chronicle: 'The computer program Boeing engineers used to predict that a debris-damaged Columbia could land safely wasn't much more than a simple chart of past foam damage, accident investigators said Tuesday.'
In other news, the Houston-based ContractorCorp announced its new, $20 million-dollar-a-license aerospace disaster analysis software...
Also today, President Bush vowed that "no cost would be spared" to identify that shuttle problem that "struck such a tragic blow to our nation's future"...
May we never see th
I was listening to cspan last night and Gehman said this "program" was nothing more than an excel spreadsheet. And the chart of past damage simply could not predict damage from the size of foam that hit Columbia.
They had only guesses as to what kind of material (foam, ice, ice-loaded foam, etc.) hit the wing. Only crude estimates as to how much hit, & where. They'd NEVER done real inspections (ultrasound, X-ray, etc.) of those carbon-carbon composite leading edges (to look for delamination, fractures, internal erosion from oxygen entering through surface pinholes, etc.) I haven't heard that they had ANY real test data from larger hits.
In this context, it doesn't much matter whether the "program" is half a million lines of gigaflop-sucking Fortran or a Buck Rogers Secret Decoder Ring. They were (fairly contentedly) starved for meaningful input.
GIGO.
It's easy to make up & spread cool- and credible-sounding stuff. Finding & checking hard facts is hard work.
Seems like a moot point to me. From what I understand they had no alternative but to attempt a landing. Maybe if they had somehow scraped together another shuttle launch right after the first one they could have all ridden home in the second one? Or maybe fixed the damage to the first one? I doubt it.
Oh, and here are some previous TPS Reports thrown in for good measure.
First, I am an engineer. Alot of you probably are too. What I'm going to say will probably be modded flamebait, etc, but I'm fighting my own battles at work in regards to problems that no one else saw... or care
Alot of the analysis has been attacking the engineers for not asking enough questions. Thats fine and dandy in a 100% hindsight problem- we have a failed shuttle- lets' find out why. Alot of the reviews have been talking about data presentation- thats good too- I went to school for engineering, not marketing, and therefor don't know what a marketer does as to how to present information without getting bogged down in details.
But when it comes straight down to it, it's money, pure and simple. Do you think CAT scans of tiles are inexpenisve? Probably a couple $k each. Do this for every tile. Want to understand turbulence completely (and people that say you can model a chaotic system- just watch the weather channel to know how EASY that is)- that costs money and time. Quite a bit of both, too.
So now you've got budget concerns on projects that aren't funded and you can only skunk work it too much (note- skunk work is done on the side, unpaid overtime/salary, and 'hiding' the cost of equipment time/usage under a variety of things. It's amazing what you can do sometimes).
Now and then you get lucky and management comes around... funds your project, everyone gets paid with a little back in the jar for the next skunk project... then again, what does management usually know? zip. Just those bottom line numbers
Now obviously there was a bit of scaleup issue. I'm not comfortable with a 5x scaleup on some jobs, much less a 640x prediction- thats me personally. And the analysis that reads safety as a failure, instead of safety as a problem is dead on (1/3 the O-ring). But don't go too hard on the engineers- many comments are headed that way. Just remember under-funding answers the important questions, and may lop a bunch of details under assumptions... and every now and then you get bit in the ass... hard.
Modding me down still doesn't change the fact that
PHIL CONDIT SUCKS DISEASED DONKEY DICK!!
Slashdot Eds Link Anonymous Posts With Logged Posts
They Are Vermin Feeding On Each Other's Feces.
I Hate \.