It's one thing to question, another to be able to technically challenge. The alternatives need to be able to answer criticisms for themselves and NASA can then respond accordingly with maybe the DoD as an external technical source weighing in. The way it is shaping up it will not be truly an independent review if NASA is the sole technical advisor. Bad bad design.
snipIt's one thing to question, another to be able to technically challenge. The alternatives need to be able to answer criticisms for themselves and NASA can then respond accordingly with maybe the DoD as an external technical source weighing in. The way it is shaping up it will not be truly an independent review if NASA is the sole technical advisor. Bad bad design.
First meeting June 17th. Open to the public, but no statement of TV coverage.http://www.spaceref.com/news/viewsr.html?pid=31351It is interesting that very few items are on the agenda, and EELVs are one of them. I would love to see NASA managers testifying on why EELVs can't do the job.I also find it interesting that there is not a word of this meeting on the NASA website -- that I could find. In fact I couldn't find a word about the new Commission on the NASA web site. I don't think this is an oversight by NASA.
Quote from: Danny Dot on 06/01/2009 08:44 pmDid Augustine pick him or did NASA pick him?ESAS was apparently flawed because it relied 100% on a very pro-stick NASA support team.Danny DegerI personally know at least half of the ESAS team and they were not "pro-stick" going in.And as head of PA&E, he was the logical candidate. But NASA picked him.
Did Augustine pick him or did NASA pick him?ESAS was apparently flawed because it relied 100% on a very pro-stick NASA support team.Danny Deger
Quote from: marsavian on 06/01/2009 09:03 pmIt's one thing to question, another to be able to technically challenge. The alternatives need to be able to answer criticisms for themselves and NASA can then respond accordingly with maybe the DoD as an external technical source weighing in. The way it is shaping up it will not be truly an independent review if NASA is the sole technical advisor. Bad bad design.It was NEVER going to be a fully independent review. The government just doesn't work that way, largely b/c there is no point in forcing an independent answer down the throat of an agency that will have to execute it.
snipI personally know at least half of the ESAS team and they were not "pro-stick" going in.
So with that personal knowledge did they come around to the current architecture or were they "told" this is what it should be? Your answer will speak volumes.
Quote from: mars.is.wet on 06/01/2009 09:24 pmsnipI personally know at least half of the ESAS team and they were not "pro-stick" going in.I have no doubt they were not pro-Ares walking in, but were they good enough to ask pointed questions about the NASA data fed to them. For example, "The Atlas Mission Planner's guide says an Atlas V Heavy can lift 29 metric tons. You say it can only lift 22 metric tons. Can you explain the difference?" Or how about, "Why do the EELVs need new upperstages? Where is your analysis to support this?"I have about a dozen more hypothetical question that should have been asked, but I will stop with these two.Danny Deger
snipI would argue that if bias did creep in, it was because the requirements were set in such a way (even in an ongoing basis revised) as to favor a particular solution. And possibly when there were impediments to a particular solution, they were grandfathered in (much as Shuttle doesn't have to meet human rating requirements).snip
This happened BIG TIME. I was knee deep in the writing of the human rating requirements before ESAS and definitely saw requirements being put in for no real good reason except to make sure EELVs didn't meet them. The people putting in these requirements had already made up their mind to build the stick.While working for Rockwell Missile Systems, one of my primary jobs was to perform analysis to get the Air Force to write requirements that favored our systems. While I was doing this, our competitors were doing the same. But in this case the Air Force listened to both sides and wrote the requirements everyone had to bit to. In the case of Ares, NASA was both the design team and the requirements development team. There were no checks and balance in place to not bias the requirements to fit a particular design that was pre-chosen.Danny Deger
I take issue with the "for no good reason". While I understand your point of view, software redundancy and factors of safety are not "for no good reason".And those requirements were written BEFORE the alleged pro-stick crowd came to power.
While those requirements can be re-written, it is not the designer's job to re-write requirements, especially when handed down from OSMA who does not care which concept "wins" or is chosen.
The study that I saw also said EELVs need new upper stages. The human rating requirements said that upper stage structural margins (and software, and other things) were insufficient.While those requirements can be re-written, it is not the designer's job to re-write requirements, especially when handed down from OSMA who does not care which concept "wins" or is chosen.
@ mars.is.wetJust like I thought. You ARE part of the conspiracy at NASA to convince everyone EELVs need new upperstages
And the relationship of the *Independent* Augustine committee to the *NASA* committee is?