4 ms·
Well, nevermind. According to this, they were using 24bit fixed point, not floating: http://www.ima.umn.edu/~arnold/disasters/patriot.html http://www.ima.umn.e
by extension 16y ago
Well, nevermind. According to this, they were using 24bit fixed point, not floating:
http://www.ima.umn.edu/~arnold/disasters/patriot.html http://www.ima.umn.edu/~arnold/disasters/patriot.html
Maybe a better moral is "avoid absolute clocks or counters, if at all possible".
- sundarurfriend 16y agoThis may be a naive question but: why did the error get accumulated over time? The original system clock was correct, and if they read from it every time and converted, the error would have remained at 0.000000095. Could someone explain how exactly this happened?
- regularfry 16y agoThe figure of 0.000000095 refers to the inaccuracy in the multiplier to get from the clock conter value to a value of time in seconds, not the inaccuracy in the clock itself. As the clock counter increases, the difference between the true time and the clock counter times the multiplier increases linearly. Edited for clarity.