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.
Development of tools that include the STP theorem poer and its associated Design Verification Systems; PHIL, a meta-programmable context sensitive structured editor; Pegasus, a system for support of graphical programming; and OBJ, an ultra high level programming language based on rewrite rules and abstract data type is reported.
The NASA Space Medicine program is now developing plans for more extensive use of high-fidelity medical simulation systems. The use of simulation is seen as means to more effectively use the limited time available for astronaut medical training. Training systems should be adaptable for use in a variety of training environments, including classrooms or laboratories, space vehicle mockups, analog environments, and in microgravity. Modeling and simulation can also provide the space medicine development program a mechanism for evaluation of other medical technologies under operationally realistic conditions. Systems and procedures need preflight verification with ground-based testing. Traditionally, component testing has been accomplished, but practical means for "human in the loop" verification of patient care systems have been lacking. Medical modeling and simulation technology offer potential means to accomplish such validation work. Initial considerations in the development of functional requirements and design standards for simulation systems for space medicine are discussed.
The NASA Space Medicine program is now developing plans for more extensive use of high-fidelity medical Simulation systems. The use of simulation is seen as means to more effectively use the limited time available for astronaut medical training. Training systems should be adaptable for use in a variety of training environments, including classrooms or laboratories, space vehicle mockups, analog environments, and in microgravity. Modeling and simulation can also provide the space medicine development program a mechanism for evaluation of other medical technologies under operationally realistic conditions. Systems and procedures need preflight verification with ground-based testing. Traditionally, component testing has been accomplished, but practical means for "human in the loop" verification of patient care systems have been lacking. Medical modeling and simulation technology offer potential means to accomplish such validation work. Initial considerations in the development of functional requirements and design standards for simulation systems for space medicine are discussed.
This paper describes the processes and results of Verification and Validation (VV) efforts for the Collocation Stand Alone Library and Toolkit (CSALT). We describe the test program and environments, the tools used for independent test data, and comparison results. The VV effort employs classical problems with known analytic solutions, solutions from other available software tools, and comparisons to benchmarking data available in the public literature. Presenting all test results are beyond the scope of a single paper. Here we present high-level test results for a broad range of problems, and detailed comparisons for selected problems.
FRET is an open source tool, developed at NASA Ames, for writing, understanding, formalizing, and analyzing requirements. In practice, requirements are typically written in natural language, which is ambiguous and consequently not amenable to formal analysis. Since formal, mathematical notations are unintuitive, requirements in FRET are entered in a restricted, natural language, called FRETish with precise unambiguous meaning. FRET helps users write FRETish requirements both by providing grammar information and examples during editing, but also through English and diagrammatic explanations to clarify subtle semantic issues. For each requirement, FRET automatically produces formalizations and supports interactive simulation of produced formalizations to ensure that they capture user intentions. Through its analysis portal, FRET connects to analysis tools by exporting verification code. Currently FRET connects to (1) the CoCoSim automated analysis tool for the verification of Simulink and Stateflow models, and (2) the Copilot runtime monitoring tool for the analysis of C programs. FRET also supports the consistency/realizability analysis of requirements for identifying conflicting requirements. In this tutorial, we introduce FRET and learn to speak and analyze FRETish through several examples.
In this tutorial, we present the FRET tool for writing, understanding, formalizing and analyzing requirements. In practice, requirements are typically written in natural language, which is ambiguous and consequently not amenable to formal analysis. Since formal, mathematical notations are unintuitive, requirements in FRET are entered in a restricted, natural language, called FRETish with precise unambiguous meaning. This tutorial explains how requirements can be captured in FRETish and subsequently formalized in temporal logics and in the synchronous data flow language Lustre. We show, through multiple examples, how FRET assists users in understanding FRETish requirements and clarifying subtle semantic issues through English and diagrammatic explanations as well as interactive simulation. FInally, this tutorial describes how FRET can be used to perform realizability checking for identifying conflicting requirements and the connection of FRET with (1) the CoCoSim automated analysis tool for the verification of Simulink and Stateflow models, and (2) the Copilot runtime monitoring tool for the analysis of C programs.
Space launch companies are actively developing, or in some cases have already developed, new vehicles that use large quantities of liquid oxygen (LOX) and liquid natural gas (LNG) propellants. This propellant mixture currently lacks sound/verified explosive safety standards for use in explosive siting and flight safety analysis. In the U.S., multiple government and commercial organizations have conducted limited testing, or are preparing to conduct tests, intended to provide a sound technical basis for LOX/LNG explosive standards applicable to space launch vehicle ground and flight operations. The limited testing and analysis conducted so far indicates the potential to produce extremely energetic explosions due to the miscibility of LOX/LNG (methane), a unique feature relative to previously used propellant mixtures such as hydrogen/oxygen or kerosene/oxygen. MOX is a homogenous mixture of methane and oxygen that is possible because of methane’s 100% miscibility in LOX. Preliminary testing by N2L, Inc. described in this paper shows that it is possible to form MOX with a variety of mixing methods, and that MOX is a sensitive high explosive capable of producing overpressures greater than comparable masses of C-4. The limited amount and quality of large-scale LOX/LNG explosive test data, and the potential formation of high-explosive MOX, create significant unknowns in the determination of hazard areas (cleared of the public) for ground operations (such as a static fire test) and flights of launch vehicles with LOX/LNG propellant. This paper will review the methods used by NASA to develop and validate the LOX/LH2 blast model using large-scale explosive test programs such as Project PYRO, the Hydrogen-Oxygen Vertical Impact (HOVI), and the Large-Scale Hydrogen-Oxygen Explosion (LSHOE) tests. This paper will describe how the same process was used to prepare an interim LOX/LNG blast model that applies to various LV failure scenarios and conservatively accounts for potential MOX formation. This paper also summarizes past and future testing and modeling efforts funded by a consortium of NASA, the US Federal Aviation Administration (FAA), and the US Space Force (USSF). These test programs should be concluded within the next 3 years and are intended to provide empirical data for model verification and validation.
Space launch companies are actively developing, or in some cases have already developed, new vehicles that use large quantities of liquid oxygen (LOX) and liquid natural gas (LNG) propellants. This propellant mixture currently lacks sound/verified LOX/LNG explosive safety standards for use in explosive siting and flight safety analysis. In the U.S., multiple government and commercial organizations have conducted limited testing, or are preparing to conduct tests, intended to provide a sound technical basis for explosive standards applicable to space launch vehicle ground and flight operations. The limited testing and analysis conducted so far indicates the potential to produce extremely energetic explosions due to the miscibility of LOX/LNG (methane), a unique feature relative to previously used propellant mixtures such as hydrogen/oxygen or kerosene/oxygen. MOX is a homogenous mixture of methane and oxygen that is possible because of methane’s 100% miscibility in LOX. Preliminary testing by N2L, Inc. described in this paper shows that it is possible to form MOX with a variety of mixing methods, and that MOX is a sensitive high explosive capable of producing overpressures greater than comparable masses of C-4. The limited amount and quality of large-scale LOX/LNG explosive test data, and the potential formation of high-explosive MOX, create significant unknowns in the determination of hazard areas (cleared of the public) for ground operations (such as a static fire test) and flights of launch vehicles with LOX/LNG propellant. This paper will review the methods used by NASA to develop and validate the LOX/LH2 blast model using large-scale explosive test programs such as Project PYRO, the Hydrogen-Oxygen Vertical Impact (HOVI), and the Large-Scale Hydrogen-Oxygen Explosion (LSHOE) tests. This paper will describe how the same process was used to prepare an interim LOX/LNG blast model that applies to various LV failure scenarios and conservatively accounts for potential MOX formation. This paper also summarizes past and future testing and modeling efforts funded by a consortium of NASA, the US Federal Aviation Administration (FAA), and the US Space Force (USSF). These test programs should be concluded within the next 3 years and are intended to provide empirical data for model verification and validation.
Pathfinder is the first in a series of Mars exploration projects that are fundamental elements of the Discovery Program missions funded by the (NASA).
The Literate Programming Extraction Engine is a Practical Extraction and Reporting Language- (PERL-)based computer program that facilitates and simplifies the implementation of a concept of self-documented literate programming in a fashion tailored to the typical needs of scientists. The advantage for the programmer is that documentation and source code are written side-by-side in the same file, reducing the likelihood that the documentation will be inconsistent with the code and improving the verification that the code performs its intended functions. The advantage for the user is the knowledge that the documentation matches the software because they come from the same file. This program unifies the documentation process for a variety of programming languages, including C, C++, and several versions of FORTRAN. This program can process the documentation in any markup language, and incorporates the LaTeX typesetting software. The program includes sample Makefile scripts for automating both the code-compilation (when appropriate) and documentation-generation processes into a single command-line statement. Also included are macro instructions for the Emacs display-editor software, making it easy for a programmer to toggle between editing in a code or a documentation mode.
Most of NASA's technology transfer activities are in the area of land use (development, suitability, and planning); forestry (including wildlife and range and vegetation inventories) agriculture related activities; and water resources. The technology dissemination function is exercised through three regional applications centers which are involved in 91 applications projects within 22 states. In addition there are approximately eight application system verification transfer (ASVT) projects, 21 university applications branches, institutionalized liason activities with public interest groups, and user requirements activities. As the result of budget cuts, the ASVT and user requirements and awareness programs are to be phased out at the end of FY81. The university applications programs are to be phased down and terminated by 1985. NASA will continue to work with the user more in an R & D and an applications development capacity, and not in a national scale or administrative way.
Solar cells used for Mars surface applications have been commercial space qualified AM0 optimized devices. Due to the Martian atmosphere, these cells are not optimized for the Mars surface and as a result operate at a reduced efficiency. A multi-year program, MOST (Mars Optimized Solar Cell Technology), managed by JPL and funded by NASA Code S, was initiated in 2004, to develop tools to modify commercial AM0 cells for the Mars surface solar spectrum and to fabricate Mars optimized devices for verification. This effort required defining the surface incident spectrum, developing an appropriate laboratory solar simulator measurement capability, and to develop and test commercial cells modified for the Mars surface spectrum. This paper discusses the program, including results for the initial modified cells. Simulated Mars surface measurements of MER cells and Phoenix Lander cells (2007 launch) are provided to characterize the performance loss for those missions. In addition, the performance of the MER rover solar arrays is updated to reflect their more than two (2) year operation.
The SAIL (Shuttle Avionics Integration Laboratory) has been established to provide direct in-line support to the space shuttle program. The SAIL provides a central facility where the avionics and related flight hardware, flight software, and flight procedures will be brought together for integration and verification testing. The basic approach is to utilize qualifiable avionics flight hardware to the greatest extent possible. Where this is not feasible, flight hardware simulators are developed that provide the electrical/electronic termination, stimulation, and signal interface to the flight hardware that it would actually encounter in the shuttle vehicle. This paper discusses the existing laboratory configuration supporting the approach and landing test phase of the shuttle program, the operational experience gained to date, and the design of the laboratory elements to support the orbital flight test phase.
The framework for quantitative scientific analysis with the Hubble Space Telescope (HST) will be established from a detailed calibration program, and a major responsibility of staff in the Telescope & Instruments Branch (TIB) is the development and maintenance of this calibration for the instruments and the telescope. The first in-orbit calibration will be performed by the SI Investigation Definition Teams (IDTs) during the Science Verification (SV) period in Cycle 0 (expected to start 3 months after launch and last for 5 months). Subsequently, instrument scientists in the TIB become responsible for all aspects of the calibration program. Because of the long lead times involved, TIB scientists have already formulated a calibration plan for the next observing period, Cycle 1 (expected to last a year after the end of SV), which has been reviewed and approved by the STScI Director. The purpose here is to describe the contents of this plan. Our primary aim has been to maintain through Cycle 1 the level of calibration that is anticipated by the end of SV. Anticipated accuracies are given here in tabular form - of course, these accuracies can only be best guesses because we do not know how each instrument will actually perform on-orbit. The calibration accuracies are expected to satisfy the normal needs of both the General Observers (GOs) and the Guaranteed Time Observers (GTOs).
The reliability of switching diode JANTX1N5614 was tested. The effect of power/temperature step stress on the diode was determined. Control sample units were maintained for verification of the electrical parametric testing. Results are reported.
The application of extended Kalman filtering to estimating the Space Shuttle Propulsion performance, i.e., specific impulse, from flight data in a post-flight processing computer program is detailed. The flight data used include inertial platform acceleration, SRB head pressure, SSME chamber pressure and flow rates, and ground based radar tracking data. The key feature in this application is the model used for the SRB's, which is a nominal or reference quasi-static internal ballistics model normalized to the propellant burn depth. Dynamic states of mass overboard and propellant burn depth are included in the filter model to account for real-time deviations from the reference model used. Aerodynamic, plume, wind and main engine uncertainties are also included for an integrated system model. Assuming uncertainty within the propulsion system model and attempts to estimate its deviations represent a new application of parameter estimation for rocket powered vehicles. Illustrations from the results of applying this estimation approach to several missions show good quality propulsion estimates.
The Consultative Committee for Space Data Systems (CCSDS) has begun the development of a set of protocol recommendations for Advanced Orbiting Systems (SOS). The AOS validation program and formal definition of AOS protocols are reviewed, and the configuration control of the AOS formal specifications is summarized. Independent implementations of the AOS protocols by NASA and ESA are discussed, and cross-support/interoperability tests which will allow the space agencies of various countries to share AOS communication facilities are addressed.
For some satellites the NASA Prediction Bulletins are the only means available to the general user for obtaining orbital information. A computational interface between the information given in the NASA Prediction Bulletins and standard orbit determination programs is provided. Such an interface is necessary to obtain accurate orbit predictions. The theoretical considerations and their computational verification in this interface modelling are presented. This analysis was performed in conjunction with satellite aided search and rescue position location experiments where accurate orbits of the Amateur Satellite Corporation (AMSAT) OSCAR-6 and OSCAR-7 spacecraft are a prerequisite.