https://en.wikipedia.org/wiki/Mars_Polar_Lander#Landing_atte...
I wonder what causes the confusion.
I don't think GP was judging ESA. I think they were merely pointing out how impressive NASA's success rate has been lately.
You also have to pre-program the entire flight and find out half an hour later if your parachutes and retro-rockets deployed, or you made a relatively small crater.
NASA's budget is larger, but they're doing more missions (and spending a lot on SLS and James Webb). I suspect blaming the ExoMars crash on budget is inaccurate.
It went riding on another orbiter, Mars Express, but at least reached the surface intact.
But what kind of "on the ground" test condition could have made it to do that ?
The fact that it was "designed to decelerate the craft for 30 seconds until it was metres off the ground" but instead it ran only 3, raises many questions. Not to say that there are zillions of ways to actually test that you are on the ground or not..
Given that the parachute was deployed at the correct time and its deployment was governed by air speed (to be deployed around 1mach), the gyroscopes were likely working correctly. The radar detection wasn't available until after deployment of the parachute (more specifically, after ejecting the heat shield, which occurred at the same time), so if the machine's decision was based on faulty input, the doppler radar is likely to blame.
It is also possible that the sensors were working correctly, but the inputs were processed incorrectly. I'd expect that an issue like that could have been caught while testing the lander on earth...
edit: it's also unlikely the engines would have kept firing after computer malfunction: there were multiple (9 iirc) thrusters all around the craft and they were fired independently using pulse-width modulation. This approach was intended to both slow down the descent and to stabilize its course/orientation.
I don't know about that. I've worked on systems where there is some hardware with thruster duration that software is writing. So if software crashes, the thrusters stop. (But I have never worked on a lander). If software is running the control loop, things would get very bad if the engines kept running at their previous output levels for 27 seconds. Thrusters are never aligned perfectly, who knows what kind of rate the lander had, there may be wind pushing it, etc. If a thruster blindly kept running, the lander may have spun up, flipped over, etc.
But the point that I wanted to make is that a software crash wouldn't explain why the lander behaved as if it was on the ground. So it's more probable that it reached the "on the ground" condition.
If that condition was adequately programmed, the chances that some sensor glitch could have triggered it are quite low. So the probability is higher that it was either badly programmed or maybe someone flipped a bit somewhere ..
Unless they used a ground proximity radar which sent back false pings due to overheating caused by the too early discarded heat shield?
I'll wait for the final crash analysis and report, but I trust that the lessons learned here will significantly improve the chances of future missions, if at least by adding some more redundancies into the mix.
But it's not the case, isn't it?
That said, _if_ there were any US companies involved then perhaps there might have been complications. Many years ago I worked on guidance software for tunnelling machines and we had a US client who insisted that we reprogrammed the entire system for them to work in "centifeet", i.e. 100th of a foot or approx 3mm.
I well remember the chaos and arguments caused by adopting such a ridiculous chimera of a unit, and was struck by how resistant some people are to adopting something as universal and transferrable as SI units.
SI is an improvement but it is not quite perfect. As long as we have a choice of imperfect systems, we have to pick which is most convenient.
I somewhat agree with that - I had the exact same conversation with my kids very recently.
Re. physical object: well, whatever physical reference artefact is used, to all intents and purposes the physical stuff is water, with the basically sensible equivalence 1L = 1kg = 1000cc. As you point out, it's not perfect because of the somewhat arbitrary scales (kg, cc), and it gets worse when you bring temperature into it (I believe it's supposed to be measured at 4 degrees C, but I'm not totally sure of that).
You're right in that it is not perfect, but at least it is a fair attempt at coherence.
Correct; it's because at that temperature water is at its densest: https://en.wikipedia.org/wiki/Water#States
Redefining the Kilogram with the DIY Watt Balance: https://www.youtube.com/watch?v=ewQkE8t0xgQ
Maybe they used an US-developed microcontroller library and screwed up the unit setting.
Much simpler to test fire the engines in a lab somewhere to make sure they run, and test the software in a simulation of the landing. It'll probably come out in the next year or so that there was either just a flat error in the code, or that the simulation was incorrect in some way.
If I were ever to somehow become absolute tyrant over the entire Earth, my first edict would make open and notorious use of non-SI units a capital crime, then I'd go live in my imperial hermit shack on a remote mountainside (paradoxically, one with a >1 Gb/s network connection) until my minions finished mopping up the last of the blood.
I think the first way should be fast enough with today's processors (but IIRC the processors on the Rovers are slower).
>>...The lander even switched on its suite of instruments, ready to record Mars’s weather and electrical field...
It's a shame. But, reading that, I can't help imagining the lander in the role of the Blue Whale from Hitchhiker's Guide to the Galaxy:
"I wonder what this big flat thing rushing toward me is? I think I'll call it 'The Ground'"