<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: House approves NASA budget</title>
	<atom:link href="http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=house-approves-nasa-budget</link>
	<description>Because sometimes the most important orbit is the Beltway...</description>
	<lastBuildDate>Wed, 17 Sep 2014 13:35:41 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.0.38</generator>
	<item>
		<title>By: Paul Dietz</title>
		<link>http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18535</link>
		<dc:creator><![CDATA[Paul Dietz]]></dc:creator>
		<pubDate>Mon, 30 Jul 2007 13:28:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18535</guid>
		<description><![CDATA[&lt;i&gt;That doesnâ€™t help your argument and only makes it look desperate.&lt;/i&gt;

I suspect a good fraction of the remaining desperate defenders of the concept are drawing a paycheck from it, in one way or another.  It&#039;s hard to change someone&#039;s mind when their livelihood depends on their current stance.

Oops, arguing the posters.  Never mind. :)]]></description>
		<content:encoded><![CDATA[<p><i>That doesnâ€™t help your argument and only makes it look desperate.</i></p>
<p>I suspect a good fraction of the remaining desperate defenders of the concept are drawing a paycheck from it, in one way or another.  It&#8217;s hard to change someone&#8217;s mind when their livelihood depends on their current stance.</p>
<p>Oops, arguing the posters.  Never mind. <img src="http://www.spacepolitics.com/wp-includes/images/smilies/icon_smile.gif" alt=":)" class="wp-smiley" /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anonymous</title>
		<link>http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18455</link>
		<dc:creator><![CDATA[anonymous]]></dc:creator>
		<pubDate>Sun, 29 Jul 2007 19:15:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18455</guid>
		<description><![CDATA[&quot;IIRC Block 1 Orion is the ISS variant, it was never intended to support lunar missions.&quot;

This argument misses or ignores the whole point behind a &quot;block&quot; development strategy to maximize vehicle commonality and contain costs.

The fact remains that the mass/performance shortfalls are now so big that the ISS and lunar Orions can no longer share a common design. It&#039;s no longer a matter of simply changing the interior layout to create the lunar-capable Block II.  The lunar Orion, assuming the next White House or two ever give NASA a shot at it after this fiasco, will now be a fundamentally different vehicle design than the ISS Orion, with all the associated new development costs and time.

The alternative is for NASA to redesign Ares I a third time.  But doing that also entails all new development costs and time.

Either way, NASA has to design and develop at least one more vehicle than originally planned to create the lunar architecture.  And that means more costs and more time than planned and promised, which will mean more cuts to other NASA programs, going back to a future White House and Congress for more money, and/or a substantial delay in the human lunar return effort.

&quot;Its a moot point that in 2007 the conceptual design for Ares V does not meet the conceptual requirements for lifting the conceptual design of the Lunar Lander for a conceptual mission in 2020.&quot;

It&#039;s not a moot point when the Ares V can no longer leverage or share element commonality (e.g., 5-segment SRB) with Ares I.  That&#039;s going to drive additional design and development costs over and above those mentioned above.  Maintaining two different sets of vehicle element elements, instead of one common set, is also going to drive operational costs.

And again, that assumes that the next White House or two even lets NASA get that far after this fiasco.

&quot;Trying to analyze this whole process externally &quot;

It&#039;s not a matter of process and it&#039;s no external analysis.  Internal documents that state the problems in very plain language are available on both NASAWatch and nasaspaceflight.com.

Where are the current, internal, confirmable, publicly available sources stating otherwise?  

&quot;Studies are performed by small groups of engineers to investigate alternatives, risks and to refine definition. Itâ€™s not unusual that such studies discover problems,&quot;

The Ares I/Orion performance/mass shortfalls are not the result of a &quot;small group of engineers&quot; doing studies to &quot;discover problems&quot;.  The entire Orion program stood down for weeks to get a handle on the shortfall.  

&quot;However some have their own agenda to find fault and undermine the work,&quot;

How can we know what anyone&#039;s agenda is on an internet blog?  Does posting here give us clairvoyant superpowers?

&quot;they latch onto every negative rumor as proof of their own view,&quot;

Again, publicly available internal documentation articulating the mass/performance shortfalls and schedule problems in very plain language is hardly &quot;rumor&quot;.

And again, where are the current, internal, confirmable, publicly available sources stating otherwise?

&quot;a view based on incomplete knowledge and often llittle understanding of basic engineering.&quot;

Please, argue the facts, logic, and opinions, not the posters.  It&#039;s fine if you don&#039;t have any facts or logic to back up your opinions.  But don&#039;t resort to broad personal attacks on everyone who disagrees with your opinion.  That doesn&#039;t help your argument and only makes it look desperate.]]></description>
		<content:encoded><![CDATA[<p>&#8220;IIRC Block 1 Orion is the ISS variant, it was never intended to support lunar missions.&#8221;</p>
<p>This argument misses or ignores the whole point behind a &#8220;block&#8221; development strategy to maximize vehicle commonality and contain costs.</p>
<p>The fact remains that the mass/performance shortfalls are now so big that the ISS and lunar Orions can no longer share a common design. It&#8217;s no longer a matter of simply changing the interior layout to create the lunar-capable Block II.  The lunar Orion, assuming the next White House or two ever give NASA a shot at it after this fiasco, will now be a fundamentally different vehicle design than the ISS Orion, with all the associated new development costs and time.</p>
<p>The alternative is for NASA to redesign Ares I a third time.  But doing that also entails all new development costs and time.</p>
<p>Either way, NASA has to design and develop at least one more vehicle than originally planned to create the lunar architecture.  And that means more costs and more time than planned and promised, which will mean more cuts to other NASA programs, going back to a future White House and Congress for more money, and/or a substantial delay in the human lunar return effort.</p>
<p>&#8220;Its a moot point that in 2007 the conceptual design for Ares V does not meet the conceptual requirements for lifting the conceptual design of the Lunar Lander for a conceptual mission in 2020.&#8221;</p>
<p>It&#8217;s not a moot point when the Ares V can no longer leverage or share element commonality (e.g., 5-segment SRB) with Ares I.  That&#8217;s going to drive additional design and development costs over and above those mentioned above.  Maintaining two different sets of vehicle element elements, instead of one common set, is also going to drive operational costs.</p>
<p>And again, that assumes that the next White House or two even lets NASA get that far after this fiasco.</p>
<p>&#8220;Trying to analyze this whole process externally &#8221;</p>
<p>It&#8217;s not a matter of process and it&#8217;s no external analysis.  Internal documents that state the problems in very plain language are available on both NASAWatch and nasaspaceflight.com.</p>
<p>Where are the current, internal, confirmable, publicly available sources stating otherwise?  </p>
<p>&#8220;Studies are performed by small groups of engineers to investigate alternatives, risks and to refine definition. Itâ€™s not unusual that such studies discover problems,&#8221;</p>
<p>The Ares I/Orion performance/mass shortfalls are not the result of a &#8220;small group of engineers&#8221; doing studies to &#8220;discover problems&#8221;.  The entire Orion program stood down for weeks to get a handle on the shortfall.  </p>
<p>&#8220;However some have their own agenda to find fault and undermine the work,&#8221;</p>
<p>How can we know what anyone&#8217;s agenda is on an internet blog?  Does posting here give us clairvoyant superpowers?</p>
<p>&#8220;they latch onto every negative rumor as proof of their own view,&#8221;</p>
<p>Again, publicly available internal documentation articulating the mass/performance shortfalls and schedule problems in very plain language is hardly &#8220;rumor&#8221;.</p>
<p>And again, where are the current, internal, confirmable, publicly available sources stating otherwise?</p>
<p>&#8220;a view based on incomplete knowledge and often llittle understanding of basic engineering.&#8221;</p>
<p>Please, argue the facts, logic, and opinions, not the posters.  It&#8217;s fine if you don&#8217;t have any facts or logic to back up your opinions.  But don&#8217;t resort to broad personal attacks on everyone who disagrees with your opinion.  That doesn&#8217;t help your argument and only makes it look desperate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cIclops</title>
		<link>http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18410</link>
		<dc:creator><![CDATA[cIclops]]></dc:creator>
		<pubDate>Sun, 29 Jul 2007 09:34:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18410</guid>
		<description><![CDATA[Wish I could say wrote:

&lt;i&gt;NASA has in fact determined that there is zero margin for the Block 1 Ares 1 and Orion to support lunar missions. Furthermore, I have heard from MSFC senior personnel that the current Ares 5 conceptual design does not meet requirements for delivering enough mass to lunar orbit and therefore a fully-fueled LSAM to the lunar surface.&lt;/i&gt;

Hello and thank you for your response. IIRC Block 1 Orion is the ISS variant, it was never intended to support lunar missions. Its a moot point that in 2007 the conceptual design for Ares V does not meet the conceptual requirements for lifting the conceptual design of the Lunar Lander for a conceptual mission in 2020.

An engineering enterprise of this scale involves many engineers and projects and few have the complete overview. Studies are performed by small groups of engineers to investigate alternatives, risks and to refine definition. It&#039;s not unusual that such studies discover problems, solving them is what engineers do. Trying to analyze this whole process externally is fascinating for those of us who are genuinely interested in following this extraordinary endeavor. However some have their own agenda to find fault and undermine the work, they latch onto every negative rumor as proof of their own view, a view based on incomplete knowledge and often llittle understanding of basic engineering.]]></description>
		<content:encoded><![CDATA[<p>Wish I could say wrote:</p>
<p><i>NASA has in fact determined that there is zero margin for the Block 1 Ares 1 and Orion to support lunar missions. Furthermore, I have heard from MSFC senior personnel that the current Ares 5 conceptual design does not meet requirements for delivering enough mass to lunar orbit and therefore a fully-fueled LSAM to the lunar surface.</i></p>
<p>Hello and thank you for your response. IIRC Block 1 Orion is the ISS variant, it was never intended to support lunar missions. Its a moot point that in 2007 the conceptual design for Ares V does not meet the conceptual requirements for lifting the conceptual design of the Lunar Lander for a conceptual mission in 2020.</p>
<p>An engineering enterprise of this scale involves many engineers and projects and few have the complete overview. Studies are performed by small groups of engineers to investigate alternatives, risks and to refine definition. It&#8217;s not unusual that such studies discover problems, solving them is what engineers do. Trying to analyze this whole process externally is fascinating for those of us who are genuinely interested in following this extraordinary endeavor. However some have their own agenda to find fault and undermine the work, they latch onto every negative rumor as proof of their own view, a view based on incomplete knowledge and often llittle understanding of basic engineering.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anonymous</title>
		<link>http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18399</link>
		<dc:creator><![CDATA[anonymous]]></dc:creator>
		<pubDate>Sun, 29 Jul 2007 07:10:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18399</guid>
		<description><![CDATA[&quot;This sort of â€œolâ€™ time religionâ€ that supporters of the ARES architecture have just baffles me. How can ANYONE claim greater reliability and safety from a computer-aided design that has never been built..?&quot;

My two-bit take on quantitative safety analysis in ESAS is that it&#039;s driven by GIGO (garbage-in, garbage-out).  ESAS uses the same quantitative models and analytical techniques that were telling us Shuttle LOM/LOC was on the order of 1-in-1000 before Challenger and 1-in-250 before (and after) Columbia.  Those models and analysis have been proven to be off by orders of magnitude versus the real world.  We&#039;re kidding ourselves to claim anything (good or bad) with respect to the reliability or safety of any launch vehicle using that piss-poor of an analytical track record.

&quot;Quick question. I know that itâ€™s an article of faith among many that Oâ€™Keefe and Steidle were â€œforced out because of their all EELV architectureâ€,&quot;

O&#039;Keefe wasn&#039;t forced out at all.  He left NASA HQ. to become the head of a university back in Louisiana, a position that combined his love of teaching (prior to taking the Deputy Director position at OMB, O&#039;Keefe taught at Syracuse) with his love of policy and administration (in his home state of Louisiana to boot).  It was an offer he could not refuse.  And even without such an offer, O&#039;Keefe was way too politically powerful, between his connections to Cheney and Stevens, to get forced out.

There are two stories on Steidle.  One, Griffin visited Steidle when Griffin was still heading APL and, in Griffin&#039;s usual apolitical way, threw insults Steidle regarding Steidle&#039;s aerospace engineering knowledge, to which Steidle leaned forward and surprised Griffin on a point or two in no uncertain terms.  When the other shoe dropped and Griffin became NASA Administrator, Griffin had little choice but to get rid of Steidle after butting heads with him.

The second, more well-known, story is that Griffin was genuinely displeased with the rate of progress towards a highly defined lunar architecture and gave Steidle his pink slip ASAP as a result.  Personally, I&#039;d take Steidle&#039;s deliberative, highly competitive, procurement-driven, and militarily-prove approach to developing a human space flight architecture over Griffin/ESAS&#039;s 60-day jump-to-a-conclusion on the basis of bad data, inadequate analysis, and in the absence of any competition or real deliberation.

I suspect the real story on Steidle involves some of both of these stories --both personally motivated as well as genuine professional disagreements on the best approach to program development.

&quot;and that therefore a Shuttle Derived architecture is a hard requirement from NASAâ€¦&quot;

It became a hard requirement for Griffin after ESAS and may have been requirement for Griffin before ESAS.  Although I can speculate that Senators Hutchison and Nelson made Shuttle workforce retention a pre-condition of Griffin&#039;s Senate confirmation, I have yet to see any evidence that Shuttle-derived per se was a hard requirement for anyone other than Griffin.  Even then, a Shuttle-derived requirement does not explain some of the stupidity exhibited in ESAS, like totally missing the superior Shuttle-derived hardware combination embodied in DIRECT 2/Jupiter 120.

Never attribute to ill intentions what is easily explained by idiocy.]]></description>
		<content:encoded><![CDATA[<p>&#8220;This sort of â€œolâ€™ time religionâ€ that supporters of the ARES architecture have just baffles me. How can ANYONE claim greater reliability and safety from a computer-aided design that has never been built..?&#8221;</p>
<p>My two-bit take on quantitative safety analysis in ESAS is that it&#8217;s driven by GIGO (garbage-in, garbage-out).  ESAS uses the same quantitative models and analytical techniques that were telling us Shuttle LOM/LOC was on the order of 1-in-1000 before Challenger and 1-in-250 before (and after) Columbia.  Those models and analysis have been proven to be off by orders of magnitude versus the real world.  We&#8217;re kidding ourselves to claim anything (good or bad) with respect to the reliability or safety of any launch vehicle using that piss-poor of an analytical track record.</p>
<p>&#8220;Quick question. I know that itâ€™s an article of faith among many that Oâ€™Keefe and Steidle were â€œforced out because of their all EELV architectureâ€,&#8221;</p>
<p>O&#8217;Keefe wasn&#8217;t forced out at all.  He left NASA HQ. to become the head of a university back in Louisiana, a position that combined his love of teaching (prior to taking the Deputy Director position at OMB, O&#8217;Keefe taught at Syracuse) with his love of policy and administration (in his home state of Louisiana to boot).  It was an offer he could not refuse.  And even without such an offer, O&#8217;Keefe was way too politically powerful, between his connections to Cheney and Stevens, to get forced out.</p>
<p>There are two stories on Steidle.  One, Griffin visited Steidle when Griffin was still heading APL and, in Griffin&#8217;s usual apolitical way, threw insults Steidle regarding Steidle&#8217;s aerospace engineering knowledge, to which Steidle leaned forward and surprised Griffin on a point or two in no uncertain terms.  When the other shoe dropped and Griffin became NASA Administrator, Griffin had little choice but to get rid of Steidle after butting heads with him.</p>
<p>The second, more well-known, story is that Griffin was genuinely displeased with the rate of progress towards a highly defined lunar architecture and gave Steidle his pink slip ASAP as a result.  Personally, I&#8217;d take Steidle&#8217;s deliberative, highly competitive, procurement-driven, and militarily-prove approach to developing a human space flight architecture over Griffin/ESAS&#8217;s 60-day jump-to-a-conclusion on the basis of bad data, inadequate analysis, and in the absence of any competition or real deliberation.</p>
<p>I suspect the real story on Steidle involves some of both of these stories &#8211;both personally motivated as well as genuine professional disagreements on the best approach to program development.</p>
<p>&#8220;and that therefore a Shuttle Derived architecture is a hard requirement from NASAâ€¦&#8221;</p>
<p>It became a hard requirement for Griffin after ESAS and may have been requirement for Griffin before ESAS.  Although I can speculate that Senators Hutchison and Nelson made Shuttle workforce retention a pre-condition of Griffin&#8217;s Senate confirmation, I have yet to see any evidence that Shuttle-derived per se was a hard requirement for anyone other than Griffin.  Even then, a Shuttle-derived requirement does not explain some of the stupidity exhibited in ESAS, like totally missing the superior Shuttle-derived hardware combination embodied in DIRECT 2/Jupiter 120.</p>
<p>Never attribute to ill intentions what is easily explained by idiocy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Dietz</title>
		<link>http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18381</link>
		<dc:creator><![CDATA[Paul Dietz]]></dc:creator>
		<pubDate>Sun, 29 Jul 2007 04:34:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18381</guid>
		<description><![CDATA[&lt;i&gt;Paul - Nope. Just not necessarily right.&lt;/i&gt;

So then why did you phrase that response as you did?  The rhetorical question being asked didn&#039;t require that the majority necessarily be right, only that it often be right.]]></description>
		<content:encoded><![CDATA[<p><i>Paul &#8211; Nope. Just not necessarily right.</i></p>
<p>So then why did you phrase that response as you did?  The rhetorical question being asked didn&#8217;t require that the majority necessarily be right, only that it often be right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Goff</title>
		<link>http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18365</link>
		<dc:creator><![CDATA[Jonathan Goff]]></dc:creator>
		<pubDate>Sun, 29 Jul 2007 00:14:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18365</guid>
		<description><![CDATA[Anonymous,
Quick question.  I know that it&#039;s an article of faith among many that O&#039;Keefe and Steidle were &quot;forced out because of their all EELV architecture&quot;, and that therefore a Shuttle Derived architecture is a hard requirement from NASA... 

You seem to be disagreeing with the conventional wisdom regarding O&#039;Keefe.  Would you be able to elaborate your reasoning?  I&#039;ve never heard anything actually solid ever produced to show that O&#039;Keefe was kicked out because of supporting EELVs, but it&#039;s an idea that seems to be the conventional wisdom in spite of the paucity of evidence.

~Jon]]></description>
		<content:encoded><![CDATA[<p>Anonymous,<br />
Quick question.  I know that it&#8217;s an article of faith among many that O&#8217;Keefe and Steidle were &#8220;forced out because of their all EELV architecture&#8221;, and that therefore a Shuttle Derived architecture is a hard requirement from NASA&#8230; </p>
<p>You seem to be disagreeing with the conventional wisdom regarding O&#8217;Keefe.  Would you be able to elaborate your reasoning?  I&#8217;ve never heard anything actually solid ever produced to show that O&#8217;Keefe was kicked out because of supporting EELVs, but it&#8217;s an idea that seems to be the conventional wisdom in spite of the paucity of evidence.</p>
<p>~Jon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wish I could say</title>
		<link>http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18362</link>
		<dc:creator><![CDATA[Wish I could say]]></dc:creator>
		<pubDate>Sat, 28 Jul 2007 23:32:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18362</guid>
		<description><![CDATA[clclops, 

     according to nasaspaceflight.com&#039;s reports of actual Constellation program documents &amp; meetings, NASA has in fact determined that there is zero margin for the Block 1 Ares 1 and Orion to support lunar missions.  Furthermore, I have heard from MSFC senior personnel that the current Ares 5 conceptual design does not meet requirements for delivering enough mass to lunar orbit and therefore a fully-fueled LSAM to the lunar surface.  In this engineer&#039;s own words: &quot;it doesn&#039;t close&quot;.  

     I&#039;m not saying NASA can&#039;t fix this.  I&#039;m not saying that these engineers are incompetent.  What I am saying is that by developing Ares 1 instead of using the highly-reliable Atlas V (with those evil-but-reliable Russian engines), we are pushing off all development of Ares 5 or EDS or LSAM until after the Shuttle stops flying.  

     Then, when you hear Congress asking why can&#039;t we fly the shuttle a few more times... perhaps for two years or so... to reduce the &quot;gap&quot;, one has to conclude that 95% of the focus of Constellation has been put on recreating Apollo VII, not Apollo XI.  

     And even if you accept Donald&#039;s Macbethian &quot;it&#039;s worse to go back and start over&quot; -- which I heard from 1985 through 1993, only to watch ISS become something very different than Freedom -- then we&#039;re stuck on a track that doesn&#039;t appear to get us out of LEO.  

    THAT is a bad thing, if you support the basic goal of VSE.]]></description>
		<content:encoded><![CDATA[<p>clclops, </p>
<p>     according to nasaspaceflight.com&#8217;s reports of actual Constellation program documents &amp; meetings, NASA has in fact determined that there is zero margin for the Block 1 Ares 1 and Orion to support lunar missions.  Furthermore, I have heard from MSFC senior personnel that the current Ares 5 conceptual design does not meet requirements for delivering enough mass to lunar orbit and therefore a fully-fueled LSAM to the lunar surface.  In this engineer&#8217;s own words: &#8220;it doesn&#8217;t close&#8221;.  </p>
<p>     I&#8217;m not saying NASA can&#8217;t fix this.  I&#8217;m not saying that these engineers are incompetent.  What I am saying is that by developing Ares 1 instead of using the highly-reliable Atlas V (with those evil-but-reliable Russian engines), we are pushing off all development of Ares 5 or EDS or LSAM until after the Shuttle stops flying.  </p>
<p>     Then, when you hear Congress asking why can&#8217;t we fly the shuttle a few more times&#8230; perhaps for two years or so&#8230; to reduce the &#8220;gap&#8221;, one has to conclude that 95% of the focus of Constellation has been put on recreating Apollo VII, not Apollo XI.  </p>
<p>     And even if you accept Donald&#8217;s Macbethian &#8220;it&#8217;s worse to go back and start over&#8221; &#8212; which I heard from 1985 through 1993, only to watch ISS become something very different than Freedom &#8212; then we&#8217;re stuck on a track that doesn&#8217;t appear to get us out of LEO.  </p>
<p>    THAT is a bad thing, if you support the basic goal of VSE.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shubber</title>
		<link>http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18348</link>
		<dc:creator><![CDATA[shubber]]></dc:creator>
		<pubDate>Sat, 28 Jul 2007 21:34:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18348</guid>
		<description><![CDATA[&lt;i&gt;â€œThe Ares vehicles far exceed any military or private sector capability in terms of safety, reliabilityâ€

On what basis? Demonstrated flights? Nope, still a paper design. Heritage? Nope, threw that out with the 4-segment and air-start SSME. ESAS calculations? Nope, they couldnâ€™t even get blackout periods and thrust levels right. &lt;/i&gt;

Curse you, Anonymous, and the differing time zones between Australia and the US!!

You beat me to it.

This sort of &quot;ol&#039; time religion&quot; that supporters of the ARES architecture have just baffles me.  How can ANYONE claim greater reliability and safety from a computer-aided design that has never been built..?

Oh, wait - I get it now.

Since it&#039;s never been built, it&#039;s NEVER FAILED.

If it&#039;s never failed, it must be better in terms of safety and reliability than something which has had 1 or more mishaps (even if they weren&#039;t complete failures).

See? With the right coaxing, you can logically make the argument that was made about the ARES.

And on that note, I have this great, 100% reliable reusable space transportation system that i&#039;m willing to sell to NASA or the DoD for only $1 billion.  It has the lowest failure and unreliability rate of any space system out there.

:-)]]></description>
		<content:encoded><![CDATA[<p><i>â€œThe Ares vehicles far exceed any military or private sector capability in terms of safety, reliabilityâ€</p>
<p>On what basis? Demonstrated flights? Nope, still a paper design. Heritage? Nope, threw that out with the 4-segment and air-start SSME. ESAS calculations? Nope, they couldnâ€™t even get blackout periods and thrust levels right. </i></p>
<p>Curse you, Anonymous, and the differing time zones between Australia and the US!!</p>
<p>You beat me to it.</p>
<p>This sort of &#8220;ol&#8217; time religion&#8221; that supporters of the ARES architecture have just baffles me.  How can ANYONE claim greater reliability and safety from a computer-aided design that has never been built..?</p>
<p>Oh, wait &#8211; I get it now.</p>
<p>Since it&#8217;s never been built, it&#8217;s NEVER FAILED.</p>
<p>If it&#8217;s never failed, it must be better in terms of safety and reliability than something which has had 1 or more mishaps (even if they weren&#8217;t complete failures).</p>
<p>See? With the right coaxing, you can logically make the argument that was made about the ARES.</p>
<p>And on that note, I have this great, 100% reliable reusable space transportation system that i&#8217;m willing to sell to NASA or the DoD for only $1 billion.  It has the lowest failure and unreliability rate of any space system out there.</p>
<p><img src="http://www.spacepolitics.com/wp-includes/images/smilies/icon_smile.gif" alt=":-)" class="wp-smiley" /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anonymous</title>
		<link>http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18319</link>
		<dc:creator><![CDATA[anonymous]]></dc:creator>
		<pubDate>Sat, 28 Jul 2007 14:22:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18319</guid>
		<description><![CDATA[&quot;The Ares vehicles far exceed any military or private sector capability in terms of safety, reliability&quot;

On what basis?  Demonstrated flights?  Nope, still a paper design.  Heritage?  Nope, threw that out with the 4-segment and air-start SSME.  ESAS calculations?  Nope, they couldn&#039;t even get blackout periods and thrust levels right. 

&quot;and lift.&quot;

Ares I is underperforming by several tons for the lunar architecture (well below three-stick Atlas V and Delta IV capabilities that could actually put the big Orion into orbit and not some suborbital hop) and Ares V by over ten tons.  How is that superior &quot;lift&quot;?

&quot;Ares V is in very early development,&quot;

Ares V has not even started development, not by a long shot.

&quot;the Lunar Architecture is even less well defined&quot;

How is four astronauts to the lunar south pole for a week with EOR and global lunar access an &quot;undefined&quot; architecture?  

&quot;&quot;There is no basis for saying they canâ€™t close this mostly undefined architecture;&quot;

Then why was LockMart considering drastic changes to Orion&#039;s lunar requirements like forgoing global access?

And why has NASA now directed LockMart to forgo Orion&#039;s lunar requirements altogether and focus on ISS?

The reality is that the shortfalls in Ares I and V performance for the lunar architecture are so big that either Orion&#039;s basic requirements will get revisited with consequent changes to the Orion design or NASA is going to have to substantially redesign the Ares vehicles for greater lift (or adopt different launch vehicles).  Shortcomings this large in mass margin cannot be fixed by just shaving a design here and there -- NASA will have to fundamentally start over from scratch with one or more of these vehicles to create a lunar-capable system.

Or NASA can forgo a lunar-capable system altogether, which is what&#039;s currently happening.  

FWIW...]]></description>
		<content:encoded><![CDATA[<p>&#8220;The Ares vehicles far exceed any military or private sector capability in terms of safety, reliability&#8221;</p>
<p>On what basis?  Demonstrated flights?  Nope, still a paper design.  Heritage?  Nope, threw that out with the 4-segment and air-start SSME.  ESAS calculations?  Nope, they couldn&#8217;t even get blackout periods and thrust levels right. </p>
<p>&#8220;and lift.&#8221;</p>
<p>Ares I is underperforming by several tons for the lunar architecture (well below three-stick Atlas V and Delta IV capabilities that could actually put the big Orion into orbit and not some suborbital hop) and Ares V by over ten tons.  How is that superior &#8220;lift&#8221;?</p>
<p>&#8220;Ares V is in very early development,&#8221;</p>
<p>Ares V has not even started development, not by a long shot.</p>
<p>&#8220;the Lunar Architecture is even less well defined&#8221;</p>
<p>How is four astronauts to the lunar south pole for a week with EOR and global lunar access an &#8220;undefined&#8221; architecture?  </p>
<p>&#8220;&#8221;There is no basis for saying they canâ€™t close this mostly undefined architecture;&#8221;</p>
<p>Then why was LockMart considering drastic changes to Orion&#8217;s lunar requirements like forgoing global access?</p>
<p>And why has NASA now directed LockMart to forgo Orion&#8217;s lunar requirements altogether and focus on ISS?</p>
<p>The reality is that the shortfalls in Ares I and V performance for the lunar architecture are so big that either Orion&#8217;s basic requirements will get revisited with consequent changes to the Orion design or NASA is going to have to substantially redesign the Ares vehicles for greater lift (or adopt different launch vehicles).  Shortcomings this large in mass margin cannot be fixed by just shaving a design here and there &#8212; NASA will have to fundamentally start over from scratch with one or more of these vehicles to create a lunar-capable system.</p>
<p>Or NASA can forgo a lunar-capable system altogether, which is what&#8217;s currently happening.  </p>
<p>FWIW&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrasteia</title>
		<link>http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18292</link>
		<dc:creator><![CDATA[Adrasteia]]></dc:creator>
		<pubDate>Sat, 28 Jul 2007 09:44:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/07/27/house-approves-nasa-budget/#comment-18292</guid>
		<description><![CDATA[&lt;i&gt;There is no basis for saying they canâ€™t close this mostly undefined architecture; alternatives are even further away because of their lesser capability.&lt;/i&gt;

I&#039;d like to hear Lockheed Martin&#039;s side of this argument.]]></description>
		<content:encoded><![CDATA[<p><i>There is no basis for saying they canâ€™t close this mostly undefined architecture; alternatives are even further away because of their lesser capability.</i></p>
<p>I&#8217;d like to hear Lockheed Martin&#8217;s side of this argument.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
