Re:Computing glitch may have doomed Mars lander
by zymhan on Tuesday October 25, 2016 @08:49AM
(#12787434)
Surely in 2016 no one is using imperial units as a default for anything even remotely related to aerospace programming.
[ Parent
| on HN ]
Re:Computing glitch may have doomed Mars lander
by rootbear on Tuesday October 25, 2016 @10:20AM
(#12788193)
I work at NASA and sadly, we do still use Imperial units for many things. It's a travesty.
Re:Computing glitch may have doomed Mars lander
by logfromblammo on Tuesday October 25, 2016 @11:06AM
(#12788589)
In military aviation mission planning, it's even worse. We have to support any damn-fool unit some random major might want to see on the printed reports. A length might need to display in feet, yards, meters, kilometers, statute miles, nautical miles, US flight level (hundreds of feet by barometer reading), AGL vs. MSL, etc. Sometimes, people mix customary, nautical, and SI units, such as by showing distances in km, altitudes in feet, and speed in knots (NM/h).
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.
Re:Computing glitch may have doomed Mars lander
by TylerH on Tuesday October 25, 2016 @11:25AM
(#12788730)
I enjoy the literary irony here of you imposing a ban on Imperial units and yet you'd go live in an Imperial shack.
Re:Computing glitch may have doomed Mars lander
by witty_username on Tuesday October 25, 2016 @02:33PM
(#12790353)
Does the software store unit information and calculates with units (like say 1 m / 1 s = 1 m/s) or does it directly operate on the numerical value (so just 1/1 = 1)?
I think the first way should be fast enough with today's processors (but IIRC the processors on the Rovers are slower).