Note however, that I choose to duplicate only scanned or photographic images of the original documents.
In other words, I provide something as close to the "real thing" as I can.
However, in working with higher-reliability code — disclaimer: my only familiarity with such matters is in working with airborne code in the U.
S., which is currently governed by a document called RTCA DO-178C, and thus I don't really know what they thought about it in 1970 in the space biz — there is a concept of "dead code", i.e., code that is never executed under the software requirements, and specifically never tested; the dead code must be completely removed from software beyond the absolute lowest level of criticality.
SKYLARK, if you'll recall, is the AGC software that replaced COLOSSUS (and was adapted from it) in the command modules used for the Apollo-Skylab and Apollo-Soyuz missions.As such, they can serve (for our purposes) to fill in gaps in LUMINARY Memo or COLOSSUS Memo series in order to track AGC revision-to-revision changes.We don't have many of these, but Don Eyles has given us a few in order to help understand some of the changes in Luminary 131 for Apollo 13 that weren't tracked by the LUMINARY Memos.Now, there is value-added in this process, since I add searchable text to those PDFs which are image-only, as well as adding metadata and bookmark panes where they don't exist.My intention is to eventually provide one-stop-shopping for all of your Apollo and Gemini computing-system documentation needs.