Incidentally, the publisher of the AGC book, Praxis Publishing, has a whole collection of well-written, engaging, and technically deep books in their space exploration category, namely, 'How Apollo Flew to the Moon'. http://www.praxis-publishing.co.uk/books.php
What boggles the mind isn't that this was possible in the 60s, it's that it required such diverse and comprehensive achievements. It wasn't just a rocket. It's a very (!) long document but these stand out:
(regarding the flight computers)
The powered flight major loop contains guidance and navigation calculations,
timekeeping, and all repetitive functions which do not occur on an interrupt
basis.
The minor loop contains the platform gimbal angle and accelerometer sampling
routines and control system computations. Since the minor loop is involved
with vehicle control, minor loop computations are executed at the rate of 25
times per second during the powered phase of flight. However, in earth
orbit, a rate of only ten executions per second is required for satisfactory
vehicle control.
The execution time for any given major loop, complete with minor loop
computations and interrupts, is not fixed.
(regarding the Vehicle Assembly Building)
The high bay area which is located in the northern section of the building,
is approximately 525 feet high, 518 feet wide, and 442 feet long. It
contains four checkout bays, each capable of accommodating a fully
assembled, Saturn V space vehicle.
[it's not a rocket, it's a space vehicle. Kind of like boats aren't vessels]
Each pair of opposite checkout bays is served by a 250-ton bridge crane with
a hook height of 462 feet.
It is absolutely crazy to think about how NASA got to the moon in freakin' 1969. Ten years ago, we didn't have FB, YouTube, widespread WiFi, flatscreen TVs, smartphones, LTE... That we landed a spaceship on the moon 4.5 times longer ago (45 years) when the state of the art was a photocopy machine is truly mindblowing.
What's even more mind blowing is the amount of time we've wasted by pumping money, time and resources into useless wars and spying infrastructures. Imagine what mankind could have accomplished if WW2 truly was the last war and all energy could have gone into getting of this planet. I'm sure we would have had "real" hover boards by now..
And there were people alive at the time who remembered the airplane being invented. Today, we can tell astounding stories to our snapchatting kids of the time when men walked on the moon.
I have just finished reading the Command and Control book about nuclear weapons development in the US. The differences in technology are even more striking than the space race. That until quite recently nuclear weapons had less security than the lock screen on a smart phone. That the early warning/firing systems had less communication reliability than sending an email. So much of the modern world seems to be derived in significant part from the cold war arms race.
Consider in 1969--much less going back to when many of the design decisions were made. (And by "no" here, I mean no in anything approaching mainstream.) No electronic calculators, just barely color television, mostly rotary dial telephones. Moore's Law had only recently been coined. No PCs of course. No Internet in any meaningful sense.
I think the moral is that you work with what you got. And that a lot of modern technology makes us more efficient in terms of personnel numbers, but if your personnel isn't constrained, that's not overall that much more efficient. Like, if you can't easily change drawings in a CAD program, that's a pain, but the solution is to hire dozens of drafters to redraw them.
What's more crazy to me is that 50 years later, we have not built an air-breathing aircraft that surpasses the SR-71 in speed or altitude. We clearly have the capacity to achieve great feats of technological ingenuity, but that doesn't mean those feats get done.
Man, I would have given up some serious allowance money for this back when the Apollo program was active.
Reading through the descriptions of some of the flight and launch control systems gives me a high level of respect for the software folk responsible. Sure, the systems were simple compared to today, but there was no room for any of the sloppiness we see passed off as "software engineering" in the interim years. "Mmm, I'm not entirely sure about that launch abort method, but we'll check it in, see if test finds anything."
I went to a talk by one of the people responsible for the Apollo guidance software (Dr. Battin from what was in the 1960s the MIT Instrumentation Lab) a few years ago. One of his stories was about how some astronauts visited Raytheon where the code was being effectively "woven" into the core memory. As he explained it, one of the purposes of the visit was to impress upon those (women) who were making the core memories that it was really important not to make a mistake because otherwise these nice young boys would die.
I find it interesting that the manual quality, writing, diagram, etc. is much higher than most things I read nowadays. Its actually a pleasure to read through...
Just imagine how much good that could be accomplished if the time spent simply on meaningless snark about photo-sharing apps was instead productively deployed.
[+] [-] kqr2|11 years ago|reply
http://www.apolloguidancecomputer.com/index.html
http://www.amazon.com/The-Apollo-Guidance-Computer-Architect...
[+] [-] nimzo|11 years ago|reply
[+] [-] arh68|11 years ago|reply
(regarding the flight computers)
(regarding the Vehicle Assembly Building) [it's not a rocket, it's a space vehicle. Kind of like boats aren't vessels][+] [-] tonyplee|11 years ago|reply
[+] [-] esoteric_wombat|11 years ago|reply
https://drive.google.com/file/d/0B8iAUeIURaT8ZS1PbTlMTjlCams...
[+] [-] jessriedel|11 years ago|reply
[+] [-] schtinky|11 years ago|reply
[+] [-] pan69|11 years ago|reply
[+] [-] sgustard|11 years ago|reply
[+] [-] 7952|11 years ago|reply
[+] [-] ghaff|11 years ago|reply
[+] [-] smackfu|11 years ago|reply
[+] [-] peterwwillis|11 years ago|reply
[+] [-] mikestew|11 years ago|reply
Reading through the descriptions of some of the flight and launch control systems gives me a high level of respect for the software folk responsible. Sure, the systems were simple compared to today, but there was no room for any of the sloppiness we see passed off as "software engineering" in the interim years. "Mmm, I'm not entirely sure about that launch abort method, but we'll check it in, see if test finds anything."
[+] [-] ghaff|11 years ago|reply
[+] [-] ash|11 years ago|reply
Apollo Lunar Module documentation: https://www.hq.nasa.gov/alsj/alsj-LMdocs.html
[+] [-] analog31|11 years ago|reply
[+] [-] WalterBright|11 years ago|reply
[+] [-] TheOtherHobbes|11 years ago|reply
I guess someone lost the PDF for it.
[+] [-] zobzu|11 years ago|reply
[+] [-] gshubert17|11 years ago|reply
http://en.wikipedia.org/wiki/Apollo_12
[+] [-] teamonkey|11 years ago|reply
It seems to me the chances of reaching the rubber vestibule or the coil-spring-cushioned blast room are fairly slim.
[+] [-] moioci|11 years ago|reply
[+] [-] ash|11 years ago|reply
Also, command module and spacesuit demo: http://www.youtube.com/watch?v=re0F-DgNQTA
[+] [-] unknown|11 years ago|reply
[deleted]
[+] [-] facorreia|11 years ago|reply
[+] [-] ar7hur|11 years ago|reply
[+] [-] msabalau|11 years ago|reply
[+] [-] zirco|11 years ago|reply
[+] [-] smackfu|11 years ago|reply
[+] [-] kirk21|11 years ago|reply
[+] [-] Ankaios|11 years ago|reply
[+] [-] webwarrior|11 years ago|reply
[+] [-] swhitt|11 years ago|reply
[+] [-] joezydeco|11 years ago|reply