[tz] Deep Impact: wrong time zone?
Malcolm.Wallace at sc.com
Mon Sep 23 07:54:22 UTC 2013
Reddit making a guess:
Put another way, if you represented time as the number of tenths of a second since midnight on January 1, 2000, then you would hit 4294967296 tenths of a second on August 11, 2013. 4294967296 is significant because it's 2^32, which is the smallest number that can't be represented as a 32-bit integer. Generally this will wrap around to 0 (as in calculating 4294967295 + 1 will give you 0).
From: tz-bounces at iana.org [mailto:tz-bounces at iana.org] On Behalf Of Paul Eggert
Sent: 22 September 2013 23:37
To: Arthur David Olson; tz at iana.org
Subject: Re: [tz] Deep Impact: wrong time zone?
Deep Impact's chief mission scientist Mike A'Hearn said, "Basically, it was a Y2K problem, where some software didn't roll over the calendar date correctly."
The fault-protection software misread any dates after 2013-08-11, and the misreads triggered an endless series of computer reboots.
The failure was in the fault-protection software -- i.e., if they hadn't tried to prevent failure, Deep Impact would still be working.
What timescale wraps around on 2013-08-11? Perhaps it was something mission-specific, such as the number of deciseconds since the mission began, or the number of milliseconds since the previous reboot, and this was bowdlerized into "calendar date" for the general public.
NASA Declares End to Deep Impact Comet Mission.
National Geographic 2013-09-20
This email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please delete all copies and notify the sender immediately. You may wish to refer to the incorporation details of Standard Chartered PLC, Standard Chartered Bank and their subsidiaries at http://www.standardchartered.com/en/incorporation-details.html.
More information about the tz