NASA Open Sources Apollo 11 Code (2009)
21–30 of 37 posts
Re: NASA Open Sources Apollo 11 Code (2009)
#22I'm afraid the holodeck will be society's last invention. - Scott Adams
And this ultimate GUI would require the ultimate coding effort.
Re: NASA Open Sources Apollo 11 Code (2009)
#23We invest a lot of code in GUI, which makes me think of: I'm afraid the holodeck will be society's last invention. - Scott Adams And this ultimate GUI would require the ultimate coding effort.
"As time passed, and more and more people became familiar with the demo, nobody got around to inventing an improvement for the user interface, so the coders simply built it into the flight software without any specific requirements to do so"
The future will always be duct tape and bubble gum.
Re: NASA Open Sources Apollo 11 Code (2009)
#24It's worth noting that the software, while only 36k machine words long, and the hardware, which was very slow even by the standards of other computers of the 60s, were remarkable works created in only a couple years by huge teams (peak of 800 people working on hardware and 400 on software IIRC). Its popular to dismiss the AGC as simple and uninteresting, but it was a challenging engineering task, and it never once ha…
It never once had a failure in flight, except for the short in Apollo 14, which they managed to hack around mid-flight. Cool story: http://www.ibiblio.org/apollo/#Final_exam_for_the_advanced_s...
However there truly was never an unknown software bug discovered in flight. Lots of known software bugs had workarounds, partially because there was a hard deadline of about 4 months where the software couldn't be changed before the launch. Pretty amazing.
Re: NASA Open Sources Apollo 11 Code (2009)
#25"July 23, 2009"
Re: NASA Open Sources Apollo 11 Code (2009)
#26Anyone who is looking for something to run it on could take a look at Block I Apollo Guidance Computer (AGC): How to build one in your basement [1]. The build took one guy four years and a lot of wire-wrap. A fascinating and quite awe-inspiring piece of work. [1] http://klabs.org/history/build_agc/
Re: NASA Open Sources Apollo 11 Code (2009)
#27It's worth noting that the software, while only 36k machine words long, and the hardware, which was very slow even by the standards of other computers of the 60s, were remarkable works created in only a couple years by huge teams (peak of 800 people working on hardware and 400 on software IIRC). Its popular to dismiss the AGC as simple and uninteresting, but it was a challenging engineering task, and it never once ha…
Stating it never failed in flight is jumping the gun a bit, it didn't fly enough times to get a reliable statistic.
Re: NASA Open Sources Apollo 11 Code (2009)
#28Anyone who is looking for something to run it on could take a look at Block I Apollo Guidance Computer (AGC): How to build one in your basement [1]. The build took one guy four years and a lot of wire-wrap. A fascinating and quite awe-inspiring piece of work. [1] http://klabs.org/history/build_agc/
How about an emulator?
Re: NASA Open Sources Apollo 11 Code (2009)
#29Anyone who is looking for something to run it on could take a look at Block I Apollo Guidance Computer (AGC): How to build one in your basement [1]. The build took one guy four years and a lot of wire-wrap. A fascinating and quite awe-inspiring piece of work. [1] http://klabs.org/history/build_agc/
Haha... That's pretty amazing... How about an emulator?
Or, if you want a web-based version (via asm.js): http://svtsim.com/moonjs/agc.html
(I knew about the Burkey version, but the JS port I just found. Ain't the modern world amazing?)