Comment by coldtea
Comment by coldtea a day ago
[flagged]
Comment by coldtea a day ago
[flagged]
Running a code test doesn't require firing a rocket.
How would you test a rocket?
You test components in isolation, you test integration of components, you run simulations of the entire rocket, and finally you test the rocket launch.
You’ll catch issues along the way, but you can’t catch all of them before a full launch test. That’s why there are launch tests.
This can get as far as the test plan is complete, multiply iterated under different interface conditions and thorough. And you are still relying upon the adherence of the simulated models to the physical reality.
Real tests do all of this at once with no option to escape reality.
Again, one thing is automating thorough software tests, another one is testing physical stuff.
This is the programmer fallacy if you have a bunch of code passing unit tests, it’s going to work when combined.
Launching a rocket is far more complex than shipping a release.
It is more like an "all or nothing" process.
I truly hope that if you ever design a rocket yourself, that you will test it. I have no idea why you'd think testing is a terrible thing to do if it has to do with rockets.
He just means MORE checking for leaks.
They already implemented a whole host of changes to the vehicles after the first test back in 2023. There's a list of corrective actions here.
Even NASA years into their existence has suffered catastrophic fatal failures. Even with the best and most knowledgeable experts working on it we are ultimately still in the infancy of space flight. Just like airlines every incident we try and understand the cause and prevent it from happening again. Lastly what they are doing is incredibly difficult with probably thousands of things that could go wrong. I think they are doing an amazing job and hope one day, even if I miss it, that space flight becomes acceptable to all who wish to go to space.
The history of rocketry goes much further back than the space shuttle. The shuttle was supposed to be a step towards reusability but didn’t succeed or progress the way they thought it would. Starship is continuing that dream of full reusability and their approach is working. You can’t plan everything on paper when it comes to hardware especially when attempting things that have never been done before, you just don’t have the data in that case. You have to build prototypes and test them to destruction. All manufacturers do this.
In hindsight yes. The trick is knowing which of the thousands of things to do are necessary. And yes, that’s how you end up with preflight checklists
Can you name a space company with less failures? Also I think it is unfair to even compare SpaceX to anything else, because of the insane amount of starts / tests combined unparalleled creativity.
According to this website their current success rate is 99,18%. That's a good number I guess? Considering other companies did not even land their stages for years.
https://spaceinsider.tech/2024/07/31/ula-vs-spacex/#:~:text=....
It says right there in your source that that figure refers to Falcon in particular. For comparison, Starship's current track record is 3/7 launch failures (+1 landing failure).
There's an order of magnitude difference between them. If they were cars, it'd be like comparing the smallest car you can think of vs one of the biggest tanks ever made.
The usual definition of success for a rocket is getting the payload to the intended orbit. Since Starship doesn't have a payload yet, at least not a real one, its "success rate" is not measuring the same thing.
I'd say that only the 7th mission was legitimately a failure, because there was some rerouting of flights outside the exclusion zone. The other six missions were successful tests since nothing other than the rocket itself was affected.
You cannot compare a mature product to something that is still under initial development.
That would be like comparing a 1-y.o.'s ability to run to a 10-y.o.'s. Of course the younger kid doesn't yet control their legs, but that doesn't mean it's going to stumble and fall forever.
It's just taxpayer money they're blowing up, so it doesn't really matter.
They're blowing up their own money, unless you still count it as being the taxpayer's after the government pays them for launch services.
The savings Spacex has promise of delivering to NASA make every dollar given to them probably an easy 2x-3x ROI.
Without Spacex, the typical cohort of gov contractors would have been happy bleeding NASA dry with one time use rockets that have 10x the launch cost and carry 1/4 the cargo.
It hasn't been disbursed yet (entirely). They get rewards for certain accomplishments.
Starship program is funded in part by NASA as part of Artemis program. So some of this money is ours.
It sounds like he's talking to investors and not to general public.
In my experience in corporate america you communicate efficiency by proclaiming a checklist of things to do - plausible, but not necessarily accurate things - and then let engineers figure it out.
Nobody cares of the original checklist as long as the problem gets resolved. It's weird but it seems very hard to utter statement "I don't have specific answers but we have very capable engineers, I'm sure they will figure it out". It's always better to say (from the top of your head) "To resolve A, we will do X,Y and Z!". Then when A get's resolved, everyone praises the effort. Then when they query what actually was done it's "well we found out in fact what were amiss were I, J K".
Test flights.
My tests keep failing until I fix all of my code, then we deploy to production. If code fails in production than that's a problem.
We could say that rockets are not code. A test run of a Spaceship surely cost much more than a test run of any software on my laptop but tests are still tests. They are very likely to fail and there are things to learn from their failures.