Edit

Page

Page title:

Page body:

[1] [CITE@en[Deep Impact (spacecraft) - Wikipedia]], [TIME[2022-12-31T00:08:01.000Z]], [TIME[2023-01-01T11:40:59.878Z]] <https://en.wikipedia.org/wiki/Deep_Impact_(spacecraft)#Contact_lost_and_end_of_mission>

>According to chief scientist A'Hearn,[SUP[__&&[&&__79__&&]&&__]] the reason for the software malfunction was a Y2K-like problem. August 11, 2013, 00:38:49.6, was 2[SUP[32]] tenth-seconds (deciseconds) from January 1, 2000, leading to speculation that a system on the craft tracked time in one-tenth second increments since January 1, 2000, and stored it in an unsigned 32-bit integer, which then overflowed at this time, similar to the Year 2038 problem.[SUP[__&&[&&__80__&&]&&__]]

[3] 値 [N[0]] が[TIME[2000-01-01T00:00:00]]。

[4] この記述では[[時間帯]]が不明。 [[UTC]] か。

[5] [CITE@en-US[NASA's Deep Space Comet Hunter Mission Comes to an End]], [[https://www.jpl.nasa.gov/]], [TIME[2023-11-25T06:29:21.000Z]] <https://www.jpl.nasa.gov/news/nasas-deep-space-comet-hunter-mission-comes-to-an-end>

>After losing contact with the spacecraft last month, mission controllers spent several weeks trying to uplink commands to reactivate its onboard systems. Although the exact cause of the loss is not known, analysis has uncovered a potential problem with computer time tagging that could have led to loss of control for Deep Impact's orientation. That would then affect the positioning of its radio antennas, making communication difficult, as well as its solar arrays, which would in turn prevent the spacecraft from getting power and allow cold temperatures to ruin onboard equipment, essentially freezing its battery and propulsion systems.

[2] 関連:
[[整数時刻系]],
[[元期]]

Historical Legal Sensitive Parent: [Help / License]

Edit

Page

Errors

Page name(s)