Autocode

Abstract: Real-time validation of rocket engine sensor data improves mission safety and reduces flight operations and ground test costs. NASA Lewis Research Center, in partnership with Expert Microsystems, has developed an innovative sensor validation system enabling real-time, automated sensor failure detection for all types of mission critical systems. Work to date has verified that these sensor validation algorithms enable highly reliable data validation for critical Space Shuttle Main Engine performance sensors, including the turbine discharge temperatures on both turbopumps. We have completed production of a prototype run-time module which has been shown to validate 22 SSME flight sensors in real-time with very high reliability. The Sensor Validation System consists of a sensor validation network development system and a realtime kernel. The network development system provides the workstation-based tools that define the analytical redundancy relations and decision strategy used by the real-time kernel to detect sensor failures in a real-time data stream. The network development system includes an autocode generator which automatically produces the validation files used by the real-time kernel. The real-time kernel plus the autocode generated files form a run-time module which can be easily integrated with the host process. This design enables non-programmers to produce and maintain sensor validation run-time modules for any process application.

Abstract: A product-line managing module includes a code and bill of material (BOM) generator module and a configuration management module. The code and BOM generator module: receives data dictionary entries and interface information; generates a product BOM of at least one of a product based on the data dictionary entries and interface information; and generates autocode for N modules based on the data dictionary entries and interface information, where N is an integer greater than 1. The configuration management module assembles the autocode to generate the product.

Abstract: Job control languages are a feature of any large scale operating system. This paper traces the historical development of these languages, and compares two representative examples, OS/360 JCL and GEORGE 3 command language. The paper draws an analogy between job control languages and programming languages, showing that JCL is equivalent to an assembly language, whilst GEORGE 3 command language is like a simple autocode.