MAPLD 2005 PC Over-burden and the Apollo 11 Finding (An Insider s Perspective ).


24 views
Uploaded on:
Description
MAPLD 2005 Computer Overload and the Apollo 11 Landing (An Insider s View ). Jack Garman NASA Retired (now Lockheed Martin Information Technology). Introduction. A “ring-side seat” My scope of knowledge Parkinson’s Law Work expands to fill the time available for its completion
Transcripts
Slide 1

MAPLD 2005 Computer Overload and the Apollo 11 Landing (An Insider s View ) Jack Garman NASA Retired (now Lockheed Martin Information Technology)

Slide 2

Introduction A "ring-side seat" My extent of learning Parkinson\'s Law Work extends to fill the time accessible for its fruition A "precept" authored by the twentieth-century British researcher C. Northcote Parkinson, known as Parkinson\'s Law. It calls attention to that individuals typically take all the time distributed (and much of the time more) to achieve any assignment. Garman

Slide 3

Themes A Story "Long, long prior, in cosmic systems far, far away" The Legacy ( Observations ) Flexibility As in "change" and advancement Parkinson\'s Law Corollary - programming necessities change and extend to surpass every sensible projection Fault Tolerance Responding to the unthinkable Planning for things that "can\'t occur" Layers of reflection are genuine No one truly observes "the entire" Time Everything is distinctive, yet everything is the same Garman

Slide 4

Painting an Image of the Times No "Web", no E-mail, no "illustrations" No "individual" PCs Word and PowerPoint "by hand", Excel by means of (GFE) slide lead "Live" CRT\'s were a wonder "The primary " Embedded PCs Digital flight control (versus simple) Guidance and Control PCs "Apollo Guidance Computer" Technology: speed, center memory, rope memory, no plate Garman

Slide 5

Painting an Image of the Times (cont\'d) Simulation Concepts in other than constant Voice and information postpones IT Expertise (generally little) Operating frameworks or "frameworks programming" Software Engineering Amazing for the day – primitive by all accounts esp prerequisites, testing, code examination Youth and innocence (and legislative issues) Obedient, brilliant, devoted Politics to a great extent imperceptible to the troops Protected, constrained comm - no web, no "NASAWatch", no "container half vacant" Garman

Slide 6

Apollo The Saturn V and IU The CSM The LM The AGC and CMC and LGC – and AGS Software "solidify" Garman

Slide 7

Layers of Abstraction (IT perspective) The Astronauts " Piloting " (and preparing) The flight control framework The direction framework (and orbital mechanics) The flight programming (and improvement frameworks) The locally available PC and related rigging The shuttles (or test systems) and subsystems The C 3 connects The ground organizes The Mission Control Center The centralized server and related apparatus The Mission Control Center (MCC) programming (and advancement frameworks) The consoles " Mission Operations " (and recreation/preparing) The Staff Support rooms The Flight Controllers and "MOCR" Me Garman

Slide 8

Flight Computers and Software The outline of the "aeronautics" (direction PC programming) Approach to handle mgmt Async versus Adjust Continue in light of the obscure Approach to Fault Recovery Single string, profoundly solid, "disappointment impossible" Vs. Multi-string, FOFS, "quit" on hard fall flat Nightmare: All quit It implied the product must have the capacity to "restart" Continue in light of the obscure Nightmare: Restart circle Garman

Slide 9

The MCC "Reassures" "Occasion" lights TV or "computerized" Speaker Display Select "P"- tube "Voice Loop" Controls NO KEYBOARDS Garman

Slide 10

Training Mission Control Sci-Fi to a youthful architect in the late 60\'s Reading the screens in Mission Control Crew Trainers ISAGC Simulations Types of "preparing" Simulations and "Coordinated Sim\'s" Playing both sides Pad Tests (MCCH attached to the genuine vehicle) Garman

Slide 11

Mission Control Center Houston Very progressive (charge structure) MOCR "Leading group of Governors" Flight Director Flight Controllers Capcom Comm The "Trench" Systems Medical Support "Simsup" SSR\'s ("the reserved alcove specialists") Infrastructure Support MCCH, PCs, systems… Engineering Support NASA designers and temporary workers around the nation Garman

Slide 12

Reminder: This was 36-years prior… … . Garman

Slide 13

The Story "Setting up" a disappointment that "can\'t occur" "playing both sides" The Results and planning The "Genuine article" 85 + 15 = 100 Alarms, ace alert and cautioning Garman

Slide 14

The Console "Cheat-Sheet" by and large is it to some degree frightening to me this was even allowed as an "instrument" or technique for a 24-year-old specialist sitting at a comfort in Mission Control amid the main arrival on the Moon Garman

Slide 15

The Story (cont\'d) Two snapshots of "reality" The "resound" "We have clean… " Rich has it all online http://www.klabs.org/history/apollo_11_alarms/support/Garman

Slide 16

The Legacy (Conclusion) Garman

Slide 17

Flexibility (change and advancement) Shuttle Legacy was/is fly-by-wire Software settled equipment improvement issues Vehicle improvement practically "killed" programming advancement utilized a HOL, yet a genuine fight "measured" 15% punishment in size Qualitative pick up in dependability Infinite pick up in change (unforeseen) (Parkinson\'s Law: Shuttle flight programming was "created" no less than three times) General (into today) Extraordinary apparatuses (and extra layers of reflection) Good News: Change is simpler Bad News: Change is less demanding Garman

Slide 18

Fault Tolerance Shuttle Avionics Legacy FO/FS and "synchronize focuses" The match up/async "wars" BFS versus PASS (versus "BASS") and S/W adaptation to internal failure Testing SPF, Crew Trainers, SAIL Cycle taking – testing the unthinkable Murphy\'s Law Good: A flight PC fizzled without effect on ALT Bad: The main orbital dispatch was postponed 48 hrs because of a PASS/BFS interface 1:67 disappointment Garman

Slide 19

Layers of Abstraction are Real No one "knows" the entire Horizontal versus vertical information turning out to be increasingly an issue Egocentricity Downward: Engineering reliance on "lower layer" secret elements always expanding The issue of "off the rack" Apollo to Shuttle to Station "flight PC" in degree Upward: Knowing where my piece, my "discovery", fits in the entire is increasingly troublesome Anecdote DoD Software Engineers projection: 1988 Garman

Slide 20

The Legacy (finished up) Flexibility ("change") Fault Tolerance ("can\'t occur") Layers of reflection are constant and Change Everything is diverse today yet everything is the same! In the event that it works, don\'t settle it! Be that as it may, - on the off chance that it works , it\'s outdated! Garman

Slide 21

Garman

Recommended
View more...