Apollo 11 Guidance Computer source code • Hacker News Board

Re: Apollo 11 Guidance Computer source code

#31

Post by ceocoder » Thu, Jul 07, 2016, 2:24 PM UTC

sjtgraham wrote: post #6

BURN_BABY_BURN--MASTER_IGNITION_ROUTINE.s - https://github.com/chrislgarry/Apollo-11/blob/dc4ea6735c4646...

I really wish we can do an AMA with these two,

> # THE MASTER IGNITION ROUTINE WAS CONCEIVED AND EXECUTED, AND (NOTA BENE) IS MAINTAINED BY ADLER AND EYLES.

I had to look this up, NOTA BENE is latin for,

  observe carefully or take special notice

Re: Apollo 11 Guidance Computer source code

#32

Post by ianbertolacci » Thu, Jul 07, 2016, 2:30 PM UTC

Have they considered rewriting it in rust?

Re: Apollo 11 Guidance Computer source code

#33

Post by pc86 » Thu, Jul 07, 2016, 2:30 PM UTC

sjtgraham wrote: post #6

BURN_BABY_BURN--MASTER_IGNITION_ROUTINE.s - https://github.com/chrislgarry/Apollo-11/blob/dc4ea6735c4646...

Also interesting is the name of two of the "General Purpose Ignition Routines" (I'm assuming, I don't speak Assembly):

  159: BURNBABY
  169: B*RNB*B*

Re: Apollo 11 Guidance Computer source code

#34

Post by mbrumlow » Thu, Jul 07, 2016, 2:36 PM UTC

alehander42 wrote: post #20

people could've really used a higher-level language compiling to optimized AGC(apollo computer) assembly. Is there any reason why they didn't develop one? It seems it would've helped tremendously with the productivity and verification (and a lot of the explanations and equations would be readable as code, not as an non-executed comment)

I could be wrong. But I think part of why they did it this way was so they could edit things on the fly if a emergency dictated so. Having to ship a compiler (would have likely been an entire separate computer) would have not been feasible.

With things done this way and documented this why they could (fairly sure did) have the pages printed out on paper and such. And if say there was some bug or new routine that needed to be added mid flight they could go to a key board input (no screen) and with the instructions from the ground reprogram a section or add a new jump point or change a value mid flight.

Remember, computers were not what they are today. They did not have super powerful laptops and such with fancy tools.

Re: Apollo 11 Guidance Computer source code

#35

Post by shepardrtc » Thu, Jul 07, 2016, 2:38 PM UTC

strgrd wrote: post #5

Previous discussion: https://news.ycombinator.com/item?id=8063192

Also, two days ago: https://news.ycombinator.com/item?id=12037546

Re: Apollo 11 Guidance Computer source code

#36

Post by fergyfresh » Thu, Jul 07, 2016, 2:41 PM UTC

Alright, who wants to make a video game using this source code with me?

Re: Apollo 11 Guidance Computer source code

#37

Post by dhoe » Thu, Jul 07, 2016, 2:42 PM UTC

Anchor wrote: post #8

uptown wrote: post #3

Love this line: TC BANKCALL # TEMPORARY, I HOPE HOPE HOPE CADR STOPRATE # TEMPORARY, I HOPE HOPE HOPE TC DOWNFLAG # PERMIT X-AXIS OVERRIDE https://github.com/chrislgarry/Apollo-11/blob/master/LUNAR_L...

And this: GAINBRAK,1 # NUMERO MYSTERIOSO https://github.com/chrislgarry/Apollo-11/blob/master/LUNAR_L...

Line 666

Re: Apollo 11 Guidance Computer source code

#38

Post by phireal » Thu, Jul 07, 2016, 2:44 PM UTC

ceocoder wrote: post #31

sjtgraham wrote: post #6

BURN_BABY_BURN--MASTER_IGNITION_ROUTINE.s - https://github.com/chrislgarry/Apollo-11/blob/dc4ea6735c4646...

I really wish we can do an AMA with these two, > # THE MASTER IGNITION ROUTINE WAS CONCEIVED AND EXECUTED, AND (NOTA BENE) IS MAINTAINED BY ADLER AND EYLES. I had to look this up, NOTA BENE is latin for, observe carefully or take special notice

Hence N.B.

Re: Apollo 11 Guidance Computer source code

#39

Post by akshatpradhan » Thu, Jul 07, 2016, 2:46 PM UTC

If this were to be rewritten in a high level language, I wonder what would it look like?

Re: Apollo 11 Guidance Computer source code

#40

Post by sizzzzlerz » Thu, Jul 07, 2016, 2:46 PM UTC

sixothree wrote: post #26

What was the development environment like for this code?

Pencil, eraser, paper, Punchcards, punchcard machine, Punchcard reader, computer, papertape, papertape puncher, AGC computer, Command Module, LEM, Neil Armstrong, Buzz Aldrin, Michael Collins.

These last 3 are software QA.