SEARCH · Engineering Papers
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
The presentation summarizes the application of SFRAT and next generation SWEEP tool to NASA programs to demonstrate their potential to provide more detailed oversight of software reliability at various stages of development and testing.
An evaluation of the software engineering techniques used for the development of a Modular Operating System (MOSS) was described. MOSS is a general purpose real time operating system which was developed for the Concept Verification Test (CVT) program. Each of the software engineering techniques was described and evaluated based on the experience of the MOSS project. Recommendations for the use of these techniques on future software projects were also given.
This paper describes the lessons learned from introducing CASE methods/tools into organizations and applying them to actual Ada software development projects. This paper will be useful to any organization planning to introduce a software engineering environment (SEE) or evolving an existing one. It contains management level lessons learned, as well as lessons learned in using specific SEE tools/methods. The experiences presented are from Alpha Test projects established under the STARS (Software Technology for Adaptable and Reliable Systems) project. They reflect the front end efforts by those projects to understand the tools/methods, initial experiences in their introduction and use, and later experiences in the use of specific tools/methods and the introduction of new ones.
Our ultimate goal is to create and maintain RELAP5-3D as the best software tool available to analyze nuclear power plants. This begins with writing excellent programming and requires thorough testing. This document covers development of RELAP5-3D software, the behavior of the RELAP5-3D program that must be maintained, and code testing. RELAP5-3D must perform in a manner consistent with previous code versions with backward compatibility for the sake of the users. Thus file operations, code termination, input and output must remain consistent in form and content while adding appropriate new files, input and output as new features are developed. As computer hardware, operating systems, and other software change, RELAP5-3D must adapt and maintain performance. The code must be thoroughly tested to ensure that it continues to perform robustly on the supported platforms. The coding must be written in a consistent manner that makes the program easy to read to reduce the time and cost of development, maintenance and error resolution. The programming guidelines presented her are intended to institutionalize a consistent way of writing FORTRAN code for the RELAP5-3D computer program that will minimize errors and rework. A common format and organization of program units creates a unifying look and feel to the code. This in turn increases readability and reduces time required for maintenance, development and debugging. It also aids new programmers in reading and understanding the program. Therefore, when undertaking development of the RELAP5-3D computer program, the programmer must write computer code that follows these guidelines. This set of programming guidelines creates a framework of good programming practices, such as initialization, structured programming, and vector-friendly coding. It sets out formatting rules for lines of code, such as indentation, capitalization, spacing, etc. It creates limits on program units, such as subprograms, functions, and modules. It establishes documentation guidance on internal comments. The guidelines apply to both existing and new subprograms. They are written for both FORTRAN 77 and FORTRAN 95. The guidelines are not so rigorous as to inhibit a programmer’s unique style, but do restrict the variations in acceptable coding to create sufficient commonality that new readers will find the coding in each new subroutine familiar. It is recognized that this is a “living” document and must be updated as languages, compilers, and computer hardware and software evolve.
The main achievements of a 36-month research program are presented. The main objective was to gain more insight into the problem of crack growth under thermal mechanical fatigue (TMF) conditions. This program was conducted at M.I.T. for the period of September 1982 to September 1985. The program was arranged into five technical tasks. Under Task I, the literature of TMF data was reviewed. The goal was to identify the crack propagation conditions in aircraft engines (hot section) and to assess the validity of conventional fracture mechanics parameters to address TMF crack growth. The second task defined the test facilities, test specimen and the testing conditions needed to establish the effectiveness of data correlation parameters identified in Task I. Three materials (Inconel X-750, Hastelloy-X, and B-1900) were chosen for the program. Task II was accomplished in collaboration with Pratt & Whitney Aircraft engineers. Under Task III, a computerized testing system to measure the TMF behavior (LCF and CG behaviors) of various alloys systems was built. The software used to run isothermal and TMF tests was also developed. Built around a conventional servohydraulic machine, the system is capable of push-pull tests under stress or strain and temperature controlled conditions in the temperature range of 25C to 1050C. A crack propagation test program was defined and conducted under Task IV. The test variables included strain range, strain rate (frequency) and temperature. Task V correlated and generalized the Task IV data for isothermal and variable temperature conditions so that several crack propagation parameters could be compared and evaluated. The structural damage (mode of cracking and dislocation substructure) under TMF cycling was identified and contrasted with the isothermal damage to achieve a sound fundamental mechanistic understanding of TMF.
System Visualization Tool (SVT) computer program developed to provide systems engineers with means of graphically representing networks. Generates diagrams illustrating structures and states of networks defined by users. Provides systems engineers powerful tool simplifing analysis of requirements and testing and maintenance of complex software-controlled systems. Employs visual models supporting analysis of chronological sequences of requirements, simulation data, and related software functions. Applied to pneumatic, hydraulic, and propellant-distribution networks. Used to define and view arbitrary configurations of such major hardware components of system as propellant tanks, valves, propellant lines, and engines. Also graphically displays status of each component. Advantage of SVT: utilizes visual cues to represent configuration of each component within network. Written in Turbo Pascal(R), version 5.0.
In response to the Vision for Space Exploration, the National Aeronautics and Space Administration (NASA) has defined a new space exploration architecture to return humans to the Moon and prepare for human exploration of Mars. One of the first new developments will be the Ares I Crew Launch Vehicle (CLV), which will carry the Orion Crew Exploration Vehicle (CEV), into Low Earth Orbit (LEO) to support International Space Station (ISS) missions and, later, support lunar missions. As part of Ares I development, NASA will perform a series of Ares I flight tests. The tests will provide data that will inform the engineering and design process and verify the flight hardware and software. The data gained from the flight tests will be used to certify the new Ares/Orion vehicle for human space flight. The primary objectives of this first flight test (Ares I-X) are the following: Demonstrate control of a dynamically similar integrated Ares CLV/Orion CEV using Ares CLV ascent control algorithms; Perform an in-flight separation/staging event between an Ares I-similar First Stage and a representative Upper Stage; Demonstrate assembly and recovery of a new Ares CLV-like First Stage element at Kennedy Space Center (KSC); Demonstrate First Stage separation sequencing, and quantify First Stage atmospheric entry dynamics and parachute performance; and Characterize the magnitude of the integrated vehicle roll torque throughout the First Stage (powered) flight. This paper will provide an overview of the Ares I-X flight test process and details of the individual flight tests.
We design, analyze, and experimentally validate a framework for demand-based allocation of high-performance space communication service in which the user spacecraft itself initiates a request for service. Leveraging machine-to-machine communications, the automated process has potential to improve the responsiveness and efficiency of space network operations. We propose an augmented ground station architecture in which a hemispherical-pattern antenna allows for reception of service requests sent from any user spacecraft within view. A suite of ground-based automation software acts upon these direct-to-Earth requests and allocates access to high-performance service through a ground station or relay satellite in response to immediate user demand. A software-defined radio transceiver, optimized for reception of weak signals from the helical antenna, is presented. Design and testing of signal processing equipment and a software framework to handle service requests is discussed. Preliminary results from on-orbit demonstrations with a testbed onboard the International Space Station are presented to verify feasibility of the concept.
Ethers are potential high-performance fuels that can be produced from renewable carbon sources such as biomass, but their combustion properties are not clearly understood. The cetane numbers (CN) for ethers, a measure of autoignition tendency, can range from less than 10 to greater than 100, and predictive tools based upon the molecular structures are desirable in order to focus fuel development research. In this study, we used molecular modeling, chemical kinetic modeling, and experimental measurements to understand the important reactions that lead to the autoignition of methylpropyl ether (MPE), a model for ethers containing alkyl chains long enough for intramolecular hydrogen transfer. These reactions are known to be important in the autoignition of alkanes and ethers and we propose to investigate the relationship between alkyl and ether reaction pathways. A reaction mechanism for MPE was created using MIT’s Reaction Mechanism Generator (RMG) and G4 quantum calculation results and models were tested using the ChemKin Pro suite of software. Results from atmospheric pressure, flow tube reactor experiments and rapid compression machine (RCM) experiments were used to test the kinetic model and suggest refinements.
Ethers are potential high-performance fuels that can be produced from renewable carbon sources such as biomass, but their combustion properties are not clearly understood. The cetane numbers (CN) for ethers, a measure of autoignition tendency, can range from less than 10 to greater than 100, and predictive tools based upon the molecular structures are desirable in order to focus fuel development research. In this study, we used molecular modeling, chemical kinetic modeling, and experimental measurements to understand the important reactions that lead to the autoignition of methylpropyl ether (MPE), a model for ethers containing alkyl chains long enough for intramolecular hydrogen transfer. These reactions are known to be important in the autoignition of alkanes and ethers and we propose to investigate the relationship between alkyl and ether reaction pathways. A reaction mechanism for MPE was created using MIT's Reaction Mechanism Generator (RMG) and G4 quantum calculation results and models were tested using the ChemKin Pro suite of software. Results from atmospheric pressure, flow tube reactor experiments and rapid compression machine (RCM) experiments were used to test the kinetic model and suggest refinements.
Static tensile and tensile creep testing of five ceramic fibers at elevated temperature was performed. J.P. Stevens, Co., Astroquartz 9288 glass fiber; Nippon Carbon, Ltd., (Dow Corning) nicalon NLM-102 silicon carbide fiber; and 3M Company Nextel 312, 380, and 480 alumina/silica/boria fibers were supplied in unsized tows. Single fibers were separated from the tows and tested in static tension and tensile creep. Elevated test temperatures ranged from 400 C to 1300 C and varied for each fiber. Room temperature static tension was also performed. Computer software was written to reduce all single fiber test data into engineering constants using ASTM Standard Test Method D3379-75 as a reference. A high temperature furnace was designed and built to perform the single fiber elevated temperature testing up to 1300 C. A computerized single fiber creep apparatus was designed and constructed to perform four fiber creep tests simultaneously at temperatures up to 1300 C. Computer software was written to acquire and reduce all creep data.
Hypobaric decompression sickness (DCS) research presents the medical monitor with the difficult task of assessing the onset and progression of DCS largely on the basis of subjective symptoms. Even with the introduction of precordial Doppler ultrasound techniques for the detection of venous gas emboli (VGE), correct prediction of DCS can be made only about 65 percent of the time according to data from the Armstrong Laboratory's (AL's) hypobaric DCS database. An AL research protocol concerned with exercise and its effects on denitrogenation efficiency includes implementation of a performance assessment test battery to evaluate cognitive functioning during a 4-h simulated 30,000 ft (9144 m) exposure. Information gained from such a test battery may assist the medical monitor in identifying early signs of DCS and subtle neurologic dysfunction related to cases of asymptomatic, but advanced, DCS. This presentation concerns the selection and integration of a test battery and the timely graphic display of subject test results for the principal investigator and medical monitor. A subset of the Automated Neuropsychological Assessment Metrics (ANAM) developed through the Office of Military Performance Assessment Technology (OMPAT) was selected. The ANAM software provides a library of simple tests designed for precise measurement of processing efficiency in a variety of cognitive domains. For our application and time constraints, two tests requiring high levels of cognitive processing and memory were chosen along with one test requiring fine psychomotor performance. Accuracy, speed, and processing throughout variables as well as RMS error were collected. An automated mood survey provided 'state' information on six scales including anger, happiness, fear, depression, activity, and fatigue. An integrated and interactive LOTUS 1-2-3 macro was developed to import and display past and present task performance and mood-change information.
The Assembly, Integration, Test, and Validation (AIT/AIV) of the Ariane4 Vehicle Equipment Bay was held at Matra Marconi Space (MMS) site of Toulouse for several years. For this activity, incident interpretation necessitates a great deal of different knowledge. When complex faults occur, particularly those appearing during overall control tests, experts of various domains (EGSE, software, on-board equipment) have to join for investigation sessions. Thus, an assistance tool for the identification of faulty equipment will improve the efficiency of diagnosis and the overall productivity of test activities. As a solution, the Aramiihs laboratory proposed considering the opportunity of a knowledge based system intended to assist the tester in diagnosis. This knowledge based system is, in fact, a short-term achievement of a long-term goal which is the capitalization of corporate memory in the Ariane4 test domain. Aramiihs is a research unit where engineers from MMS and researchers from the IRIT-CNRS cooperate on problems concerning new types of man-system interaction.
The James Webb Space Telescope (JWST) Project has been defining, developing, and exercising the use of a common eXtensible Markup Language (XML) for the command and telemetry (C&T) database structure. JWST is the first large NASA space mission to use XML for databases. The JWST project started developing the concepts for the C&T database in 2002. The database will need to last at least 20 years since it will be used beginning with flight software development, continuing through Observatory integration and test (I&T) and through operations. Also, a database tool kit has been provided to the 18 various flight software development laboratories located in the United States, Europe, and Canada that allows the local users to create their own databases. Recently the JWST Project has been working with the Jet Propulsion Laboratory (JPL) and Object Management Group (OMG) XML Telemetry and Command Exchange (XTCE) personnel to provide all the information needed by JWST and JPL for exchanging database information using a XML standard structure. The lack of standardization requires custom ingest scripts for each ground system segment, increasing the cost of the total system. Providing a non-proprietary standard of the telemetry and command database definition formation will allow dissimilar systems to communicate without the need for expensive mission specific database tools and testing of the systems after the database translation. The various ground system components that would benefit from a standardized database are the telemetry and command systems, archives, simulators, and trending tools. JWST has exchanged the XML database with the Eclipse, EPOCH, ASIST ground systems, Portable spacecraft simulator (PSS), a front-end system, and Integrated Trending and Plotting System (ITPS) successfully. This paper will discuss how JWST decided to use XML, the barriers to a new concept, experiences utilizing the XML structure, exchanging databases with other users, and issues that have been experienced in creating databases for the C&T system.
Transition temperature testing of ferritic steels evaluates the ductile to brittle transition temperature, where the behavior of the steel changes from controlled ductile tearing to uncontrollable brittle fracture. This testing is governed by ASTM (American Society of Testing and Materials) E1921 standard. The calculations and plots required by this standard are iterative in nature and require significant effort to produce by standard hand calculations. In addition to analysis of a complete data set, intermediate analysis during testing is beneficial to determine optimal test temperatures. Given the exhaustive nature of calculating the transition temperature, being able to quickly update target temperatures is a significant benefit to not only the quality of tests, but the number of required tests as well. T0 Test Evaluation Module (T0TEM) v1.5 is a software application created under the Layered Pressure Vessel (LPV) certification effort. To reduce the analysis time of transition temperature test data sets producedfor this effort, T0TEM was created to calculate the E1921 Master Curve along with all required data and validity checks. By creating this program, hundreds of hours of analysis time were saved. In addition, the creation of a standard program provided a significant improvement in the consistency with which results were reported. T0TEM also calculates the results and plots required for the E1921 inhomogeneity annex to determine whether a material behaves in a homogenous manner. This program was created by Levi Shelton and Cameron Bosley at NASA, with input and review from the E1921 committee. The results generated by T0TEM were compared to the validation data sets provided by ASTM with good concurrence. ASTM committee members have reviewed and applied T0TEM to other data sets with satisfactory results. T0TEM was originally released to the NASA Software Repository and publicly via SourceForge in May of 2020. Version 1.5 was released in April of 2021 with minor functionality updates and additional statistical analysis methods.
The paper discusses the design of a higher harmonic blade pitch control system for flight testing on an OH-6A helicopter. Alternative designs for both the mechanical and electronic subsystems are also presented. Among the recommendations set forth are: (1) use electronic analog methods instead of FFT software, delegating spectral analysis and self testing to an Electronic Control Unit; (2) use a digital rather than analog computer for increased flexibility in solution processing; and (3) locate HHC actuators in the nonrotating system and separate these actuators from the primary control system. It is concluded that a target weight for a prototype control system would be less than 1% of design gross weight and the production weight of the future HHC system may be 0.5 of the weight of the aircraft.
The ability to monitor air contaminants in the Shuttle and the International Space Station is important to ensure the health and safety of astronauts. Three specific space applications have been identified that would benefit from a chemical monitor: organic contaminants in crew cabins, propellant contaminants in the airlock, and pre-combustion fire detection. NASA has assessed several commercial and developing electronic noses (e-noses) for these applications. A preliminary series of tests identified those e-noses that exhibited sufficient sensitivity to the vapors of interest. These e-noses were further tested to assess their ability to identify vapors, and in-house software has been developed to enhance identification. This paper describes the tests, the classification ability of selected e-noses, and the software improvements made to meet the requirements for these space program applications.
The Mission Planning and Sequencing (MPS) element of Multi-Mission Ground System and Services (MGSS) provides space missions with multi-purpose software to plan spacecraft activities, sequence spacecraft commands, and then integrate these products and execute them on spacecraft. Jet Propulsion Laboratory (JPL) is currently is flying many missions. The processes for building, integrating, and testing the multi-mission uplink software need to be improved to meet the needs of the missions and the operations teams that command the spacecraft. The Multi-Mission Sequencing Team is responsible for collecting and processing the observations, experiments and engineering activities that are to be performed on a selected spacecraft. The collection of these activities is called a sequence and ultimately a sequence becomes a sequence of spacecraft commands. The operations teams check the sequence to make sure that no constraints are violated. The workflow process involves sending a program start command, which activates the Automatic Sequence Processor (ASP). The ASP is currently a file-based system that is comprised of scripts written in perl, c-shell and awk. Once this start process is complete, the system checks for errors and aborts if there are any; otherwise the system converts the commands to binary, and then sends the resultant information to be radiated to the spacecraft.