<font color="yellow">"I respectfully request that you tone your remarks down a bit "</font><br /><br />OK I guess because of being frustrated by the scrub my wording was poor, sorry about that. I do and did understand that there were probably lot of <i>technical</i> reasons for doing that test now and not before. But it's not a purely technical issue, more like PR or image. <br /><br />Two events in the Launch Scrub News Conference highlighted this. First the Italian reporter asking a general question is the shuttle just too complex because the two recent mishaps (window cover, sensor fault). The second and more clear was the question about authorization for go flight while knowing that there are some untested issues. IIRC this was the one where Griffin intervened. The answers by the NASA staff were of course quite valid, because the source of the bug is still unknown they did what they could changed pretty much everything and decided to try with that, knowing that if the sensors still act they would notice it during countdown tests. <br /><br />Then Griffin started talking how the phenomenon is intermittent, it comes and goes. I don't know if he meant this as some sort of justification to the go flight decision or not, but if it was isn't it rather poor one? How does a test verify that intermittent sensor fault has been solved? How do you know if the problem is gone while you test but comes back the second you launch if you don't know the root cause for sure? What happened now is that NASA brought untested machine to the launch pad with fixes that they were uncertain of, hoping that the bug didn't show up during countdown. If that is NASA way of business as usual then .. oh well, it is.<br />