Fun fact: the actual programs in the spacecraft were stored in core rope memory, an ancient memory technology made by (literally) weaving a fabric/rope, where the bits were physical rings of ferrite material.
"Core" memory is resistant to cosmic rays. The state of a core bit will not change when bombarded by radiation in Outer Space. Can't say the same of solid state memory.
I worked on core memory computers in the 60's. You had 16K, tape drives (no disks) and FORTRAN. What a gas!
"It is first appropriate to briefly describe the Apollo Guidance Computer (AGC). This processor is a general purpose, sequential, digital machine. Its word length
is 16 bits including parity. The random access memory consists of 2048 words of
destructive, read-write memory, called erasable, and 36,864 words of non- destructive read-only memory called fixed memory. The memor’y cycle time (MCT) is slightly less than 12 microseconds, with two MCI’s required to execute an add
and four MCTs to execute a multiply. As is typical of real-time control computers, this machine has a set of special input-output channels with which it controls the
spacecraft and observes the state of its environment. The interrupt structure consists of ten program interrupts with associated priorities, which are used for program
control transfers. In addition, twenty-six counter interrupts with associated priorities allow for input-output servicing. The instruction set consists of forty-two
regular instructions and nine involuntary instructions. Figure 1 indicates the number and diversity of systems with which the AGC interacts"
Now that the shuttle program has ended, it would be nice to get the supposedly perfect code produced by the On-board Shuttle Group as well. I wonder if a FOIA request has been made.
A very interesting book, written by Frank O'Brien and published by Springer, The Apollo Guidance Computer: Architecture and Operation, is definitely worth the read. Fun fact: The unit weighed 70lbs (32kg).
The AGC has spawned a pretty active cult of hardware hackers that have built the AGC from scratch - including the core memory.
looking through some of those documents a couple things stand out to me:
1) learn your maths people if you want to do rocket science stuff
2) the amount and detail of the documentation they wrote back then is unreal
3) the simple webapps I write for big bucks at local megacorp pale in comparison to those programs that frickin landed people on the moon!
exDM69|14 years ago
http://en.wikipedia.org/wiki/Core_rope_memory
GnarfGnarf|14 years ago
I worked on core memory computers in the 60's. You had 16K, tape drives (no disks) and FORTRAN. What a gas!
strangetimes|14 years ago
LOL.
__alexs|14 years ago
J3L2404|14 years ago
http://en.wikipedia.org/wiki/Quipu
angersock|14 years ago
http://www.ibiblio.org/apollo/hrst/archive/1678.pdf
"It is first appropriate to briefly describe the Apollo Guidance Computer (AGC). This processor is a general purpose, sequential, digital machine. Its word length is 16 bits including parity. The random access memory consists of 2048 words of destructive, read-write memory, called erasable, and 36,864 words of non- destructive read-only memory called fixed memory. The memor’y cycle time (MCT) is slightly less than 12 microseconds, with two MCI’s required to execute an add and four MCTs to execute a multiply. As is typical of real-time control computers, this machine has a set of special input-output channels with which it controls the spacecraft and observes the state of its environment. The interrupt structure consists of ten program interrupts with associated priorities, which are used for program control transfers. In addition, twenty-six counter interrupts with associated priorities allow for input-output servicing. The instruction set consists of forty-two regular instructions and nine involuntary instructions. Figure 1 indicates the number and diversity of systems with which the AGC interacts"
EDIT: Apparently, as of six or so hours ago, Notch has implemented cutting-edge 1970s technology ( http://dcpu.com/highnerd/dcpu16_1_3.txt ). :)
tryeng|14 years ago
andrewcooke|14 years ago
anyone know the etymology? is it just a shortened form of "debugger"? is "bugger" not common slang in american english? or is this a joke?
Nate75Sanders|14 years ago
charlieok|14 years ago
viggity|14 years ago
"Debugging" came from the action of trying to find where the bug is at in a program (or, in the original case, the machine)
russss|14 years ago
http://code.google.com/p/virtualagc/source/browse/#svn%2Ftru...
jscheel|14 years ago
rbrtrbrt|14 years ago
http://www.ibiblio.org/apollo/listings/Luminary099/PINBALL_G...
It's in the code repository for multiple Apollo's
th0ma5|14 years ago
mladenkovacevic|14 years ago
skore|14 years ago
horsehead|14 years ago
tathagatadg|14 years ago
ptrckryn|14 years ago
The AGC has spawned a pretty active cult of hardware hackers that have built the AGC from scratch - including the core memory.
stuff4ben|14 years ago
roqetman|14 years ago
GnarfGnarf|14 years ago
Wouldn't be a hoot if someone ran this through a simulator, and discovered a bug that had eluded NASA?
jerf|14 years ago
jerius|14 years ago
[1]: http://www.fastcompany.com/magazine/06/writestuff.html
Retric|14 years ago
mykhal|14 years ago
glenntzke|14 years ago
pkmays|14 years ago
Michiel|14 years ago
alexbell|14 years ago
developer9|14 years ago
[deleted]
donnawarellp|14 years ago
[deleted]
rurounijones|14 years ago