3 ms·
About the same as you debug an issue from having just a tracelog. The rocket and pad equipment have quite a few sensors that record information, so you have qui
by ygra 10y ago
About the same as you debug an issue from having just a tracelog. The rocket and pad equipment have quite a few sensors that record information, so you have quite a lot of data afterwards to spot anomalies (you could also compare to previous successful launches / static fires to spot them). Admittedly, that doesn't really explain how they figure out some stuff, e.g. with CRS-7 the problem was with a strut holding a high-pressure helium vessel in the second stage. They likely would have seen the overpressurization of the tank and there are not many sources for that pressure, but pinpointing it to a piece that doesn't even exist anymore ... beats me.
- mikeknoop 10y agoI don't recall the source, but they identified the CRS-7 strut by using several mechanical vibration sensors placed on various parts of the rocket. The deflection / explosion reaches the sensors at different times, and with precision timing, it enables you to reverse pinpoint where it must have originated: the failing strut.
- TrevorJ 10y agothey also have pressure sensors in the tanks so the timing of pressure differences allowed them to determine that the tank came loose before it burst.
- rohit89 10y agoThey probably brainstorm through all the possible scenarios that could have caused a particular condition and then see if the data matches and they can prove it as best they can.