ryan/Apollo-11
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Convert MAIN into Markdown source code indices (#666)

Browse Source 
* Convert MAIN into Markdown source code indices

* Remove content from MAIN now in README

* docs(luminary): link up README to source files

* docs(luminary): fix linting issues
This commit is contained in:
James Harris
2020-09-01 16:17:52 +01:00
committed by GitHub
parent 9df8cbda3a
commit 3676b43413
2 changed files with 223 additions and 73 deletions
Download Patch File Download Diff File Expand all files Collapse all files

73
Luminary099/MAIN.agc
View File

@@ -1,72 +1,3 @@
# Copyright: Public domain.
# Filename: MAIN.agc
# Purpose: The main source file for Luminary 1A, revision 099.
# It is part of the source code for the Lunar Module's (LM)
# Apollo Guidance Computer (AGC) for Apollo 11.
# Assembler: yaYUL
# Contact: Ron Burkey <info@sandroid.org>.
# Website: www.ibiblio.org/apollo/index.html
# Mod history: 2009-05-05 RSB Adapted from Luminary131/MAIN.agc.
#
# The contents of the "Luminary099" files, in general, are
# transcribed from a digital images created from a hardcopy of the program
# residing at the MIT Museum. Many thanks to Debbie Douglas of the Museum,
# and to Paul Fjeld (who made the images).
#
# Notations on this document read, in part:
#
# ASSEMBLE REVISION 001 OF AGC PROGRAM LMY99 BY NASA 2021112-061
# 16:27 JULY 14,1969
# [Note that this is the date the hardcopy was made, not the
# date of the program revision or the assembly.]
# ...
# THIS LGC PROGRAM IS INTENDED FOR USE IN THE LM DURING THE MANNED
# LUNAR LANDING MISSION OR ANY SUBSET THEREOF.
# ...
#
# The page images themselves, as reduced in size (and consequently in
# quality) to be suitable for online presentation, are available at
# http://www.ibiblio.org/apollo. If you want to see the (much) higher
# quality digital images that Paul actually made, contact info@sandroi.org
# directly.
#
# This file is a little different from the other Luminary099 files I'm providing,
# in that it doesn't represent anything that appears directly in the original source.
# What I (RSB) have done for organizational purposes is to split the huge monolithic
# source code into smaller, more manageable chunks--i.e., into individual source
# files. Those files are rejoined within this file as "includes". It just makes
# it a little easier to work with. The code chunks correspond to natural divisions
# into sub-programs. In fact, these divisions are more-or-less specified by
# the source code itself. Refer to the "TABLE OF SUBROUTINE LOG SECTIONS" at the
# very beginning of the file ASSEMBLY_AND_OPERATION_INFORMATION.agc.
#
# It may be reasonably asked why tens of thousands of lines of source are joined by
# means of inclusion, rather than simply assembling the source files individually and
# then linking them to form the executable. The answer is that the original
# development team had no linker. The builds were monolithic just like this.
# There was a big emphasis on reusability of the code in the original project,
# apparently, but this reusability took the form of inserting your deck of
# punch-cards at the appropriate position in somebody else's deck of punch-cards.
# (Actually, I believe a tape-library method was used to avoid having to continually
# reload the card decks, but that doesn't change the basic principle.)
# So, indeed, the method of file-inclusion is a very fair representation of the
# methods used in the original development ... with the improvement, of course,
# that you no longer have to worry about dropping the card deck. On the other hand,
# I wasn't there at the time, so I may have no idea what I'm talking about.
#
# Finally, note that the original Apollo AGC assembler (called "YUL") is no longer
# available (as far as I can tell). In fact, it was replaced by another assembler
# ("GAP") even before Apollo 11, but GAP is no more available than is YUL. The
# replacement assembler yaYUL accepts a slightly different format for the source
# code from what YUL or GAP accepted, so the source code has been targeted for
# assembly with yaYUL.
# What follows is simply a bunch of file-includes for the individual code chunks.
# I've marked the page numbers to make proof-reading easier. Besides, the digital
# images of the assembly listing contains a lot of interesting tables (cross-
# referenced to page numbers) created by GAP, but not duplicated by yaYUL, so it's
# still valuable even if the source-files listed below are at hand.
$ASSEMBLY_AND_OPERATION_INFORMATION.agc # pp. 1-27
$TAGS_FOR_RELATIVE_SETLOC.agc # pp. 28-37
$CONTROLLED_CONSTANTS.agc # pp. 38-53
@@ -158,7 +89,3 @@ $TRIM_GIMBAL_CNTROL_SYSTEM.agc # pp. 1472-1484
$AOSTASK_AND_AOSJOB.agc # pp. 1485-1506
$SPS_BACK-UP_RCS_CONTROL.agc # pp. 1507-1510
# pp. 1511-1743: GAP-generated tables.