![]() ![]() In addition, it was the computer specialist Jack Garman down at NASA who wisely advised a “no abort” for the lunar landing. This astute observation enabled an easy solution: this data could be directly relayed to the astronauts from Houston (rather than displayed on the computer). ![]() During these alarms, astronaut Buzz Aldrin noted that a certain condition (16/68 code display which is range to the landing site and the LM velocity) consistently triggered this 1202 alarm. Important lessons were learned from this key moment have relevance to AI in medicine and health care: The alarms (one 1201 and multiple 1202s) were triggered as a result of this condition that warranted Executive Overflow (computer overload). Spurious radar signals were flooding this computer with limited capacity at the time of the landing (and vital programs were not able to be run). This entire constellation of programs, aptly named the Apollo Guidance Computer, was deconstructed into modules designed to run individually but the computer itself was a single processor computer (not designed to run multiple programs). The technology (and human) “fail” in brief: The software program on the lunar module (LM) had to accommodate information such as state vector (location and movement), module performance, and landing parameters. One relatively small but significant moment during this monumental event was Apollo 11’s 1202 Alarm that occurred at about 3,000 feet up from the lunar surface that almost lead to an abort of the historic landing. We have just celebrated the 50th anniversary of the lunar landing, arguably the most significant news event of this century. Neil Armstrong, Apollo 11 Commander, minutes before lunar landing ![]() “It’s a 1202… What is that? Give us a reading on the 1202 Program Diagram.” ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |