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.
A preliminary reduced variable master was constructed for pressure loading. A study of cell thickness versus cell stress was completed. Work is continuing on encapsulation of qualification modules. A 4 ft x 4 ft 'credit card' construction laminate was made.
This case study of Hurricane Matthew (October 2016) uses the NASA Short-Term Prediction Research and Transition (SPoRT) Center DNB power outage product (using GSFC VIIRS DNB preliminary Black Marble product, Roman et al.. 2017) and 2013 LandScan Global population data to look for correlations between the post-event %-of-normal radiance and the utility company-reported outage numbers (obtained from EAGLE-1).
This case study analyzes the application of the cleanroom software development methodology to the development of production software at the NASA/Goddard Space Flight Center. The cleanroom methodology emphasizes human discipline in program verification to produce reliable software products that are right the first time. Preliminary analysis of the cleanroom case study shows that the method can be applied successfully in the FDD environment and may increase staff productivity and product quality. Compared to typical Software Engineering Laboratory (SEL) activities, there is evidence of lower failure rates, a more complete and consistent set of inline code documentation, a different distribution of phase effort activity, and a different growth profile in terms of lines of code developed. The major goals of the study were to: (1) assess the process used in the SEL cleanroom model with respect to team structure, team activities, and effort distribution; (2) analyze the products of the SEL cleanroom model and determine the impact on measures of interest, including reliability, productivity, overall life-cycle cost, and software quality; and (3) analyze the residual products in the application of the SEL cleanroom model, such as fault distribution, error characteristics, system growth, and computer usage.
The EDIN (Engineering Design Integration) System which provides a collection of hardware and software, enabling the engineer to perform man-in-the-loop interactive evaluation of aerospace vehicle concepts, was considered. Study efforts were concentrated in the following areas: (1) integration of hardware with the Univac Exec 8 System; (2) development of interactive software for the EDIN System; (3) upgrading of the EDIN technology module library to an interactive status; (4) verification of the soundness of the developing EDIN System; (5) support of NASA in design analysis studies using the EDIN System; (6) provide training and documentation in the use of the EDIN System; and (7) provide an implementation plan for the next phase of development and recommendations for meeting long range objectives.
The Tethered Satellite System has great prospects for extending orbital operations capability of the Space Transportation System to science, applications, and technology projects not otherwise attainable. The system will installed in the Shuttle Orbiter and will have the capability to deploy a captive satellite up to 100 km away from the Orbiter. Control and retrieval of the satellite are accomplished by means of a tether line connecting the satellite and the cargo bay mounted equipment in the Orbiter. At low satellite altitudes, the system will permit investigations of a duration that could not be pursued with sounding rockets of free-flying spacecraft. The propose of the Shuttle/Tethered Satellite System Definition Study was to produce the preliminary design, preliminary specifications, gross program plans, and program cost estimate for a 1982 operational verification flight. This was accomplished during a fifteen month effort under by the NASA George C. Marshall Space Flight Center (MSFC). The MSFC Phase 1 and related studies demonstrated the feasibility of the system and served as a starting point for the Phase 2 definition study.
The high initial cost of prototype Very Large Scaled Integrated (VLSI) parts requires that sufficient verifications be made to eliminate design errors before actually producing the prototypes. Logic simulation is the means by which the VLSI engineer can ensure that the design will function properly. The computer time required for logic simulation can be reduced through the use of behavioral models. Behavioral models, however, require time to write and verify and they do not always produce a dramatic speed up in logic simulation time. This paper presents a study of behavioral modeling aimed at discovering which circuit types benefit most from the use of behavioral models for logic simulation.
Throttleable thrustor system for Mars soft landing, selecting catalytic decomposition engine from system weight and performance studies
A one dimensional model for studying the thermal dynamics of cooling lakes was developed and verified. The model is essentially a set of partial differential equations which are solved by finite difference methods. The model includes the effects of variation of area with depth, surface heating due to solar radiation absorbed at the upper layer, and internal heating due to the transmission of solar radiation to the sub-surface layers. The exchange of mechanical energy between the lake and the atmosphere is included through the coupling of thermal diffusivity and wind speed. The effects of discharge and intake by power plants are also included. The numerical model was calibrated by applying it to Cayuga Lake. The model was then verified through a long term simulation using Lake Keowee data base. The comparison between measured and predicted vertical temperature profiles for the nine years is good. The physical limnology of Lake Keowee is presented through a set of graphical representations of the measured data base.
The research performed and the results obtained at the Laboratory for Radiation Studies, Prairie View A&M University and Texas A&I University, on the problem of Single Events Upsets, the various schemes employed to limit them and the effects they have on the reliability and fault tolerance at the systems level, such as robotic systems are reviewed.
In current practice, it is often difficult to draw firm conclusions about turbulence model accuracy when performing multi-code CFD studies ostensibly using the same model because of inconsistencies in model formulation or implementation in different codes. This paper describes an effort to improve the consistency, verification, and validation of turbulence models within the aerospace community through a website database of verification and validation cases. Some of the variants of two widely-used turbulence models are described, and two independent computer codes (one structured and one unstructured) are used in conjunction with two specific versions of these models to demonstrate consistency with grid refinement for several representative problems. Naming conventions, implementation consistency, and thorough grid resolution studies are key factors necessary for success.
The ongoing Operational Applications of Satellite Snowcover Observations (OASSO) Project of NASA's Applications Systems Verification Test (ASVT) Program is discussed. The general objectives, organization, and study-area activities of the OASSO program are outlined. It is noted that this part of the ASVT Program is designed to evaluate under operational conditions the overall utility of satellite snowcover observations for stream flow forecasts and will be carried out in four regions centered in Arizona, California, Colorado, and Oregon.
The effects of mesoscale and microscale fluctuations of the winds on the determination of the synoptic scale wind are studied in order to show the effects of mesoscale variability on the verification of wind forecasts and on the comparison of remotely sensed and anemometer-averaged winds, and to show how to measure the synoptic wind scale more accurately. The frequencies involved correspond to periods longer than one hour and extend to the microscale. Nondimensional spectra that span both the mesoscale and the microscale are derived. Both conventional anemometer averages and remotely sensed winds contain a random component of the mesoscale wind in their values. These components are differences and not errors when winds are compared, and quantitative values for these differences are given. Ways of improving the measurement of the synoptic scale wind by transient ships, data buoys, and scatterometers on future spacecraft are described.
During the thermal vacuum test phase of the GOES 7 spacecraft, the primary scan mirror system exhibited unacceptably high drive friction. The observed friction was found to correlate with small misalignments in the mirror structure and unavoidable loads induced by the vehicle spin. An intensive effort to understand and document the performance of the scan mirror bearing system under these loads is described. This effort involved calculation of the bearing loads and expected friction torque, comparison of the computed values to test data, and verification of the lubrication system performance and limitations under external loads. The study culminated in a successful system launch in February of 1987. The system has operated as predicted since that time.
This study consists of an investigation into the nonstationary transient response of the Verification Test Article (VETA) when subjected to random acoustic excitation. The goal is to assess excitation models that can be used in the design of structures and equipment when knowledge of the structure and the excitation is limited. The VETA is an instrumented cantilever beam that was exposed to acoustic loading during five Space Shuttle launches. The VETA analytical structural model response is estimated using the direct averaged power spectral density and the normalized pressure spectra methods. The estimated responses are compared to the measured response of the VETA. These comparisons are discussed with a focus on prediction conservatism and current design practice.
This Technical Memorandum is the result of a 2-year project funded by the Defense Logistics Agency-Aviation, Hazardous Minimization and Green Products Branch, to identify and test two candidate solvents to replace hydrochlorofluorocarbon-225 (HCFC-225) for cleaning oxygen systems. The solvents were also compared to a second solvent composed predominantly of perfluorobutyl iodide (PFBI), which had received limited approval by the United States Air Force (USAF) for hand wipe cleaning of components for aviators’ breathing oxygen systems. The tests performed for this study were based on those reported in AFRL-ML-WP-TR-2003-4040, “The Wipe Solvent Program,” the test program used to qualify Ikon® Solvent P for USAF applications.The study was completed in August 2014, prior to the completion of a more extensive study funded by the NASA Rocket Propulsion Test (RPT) program. The results of the RPT project are reported in NASA/TP-2015-18207, “Replacement of Hydrochlorofluorocarbon–225 Solvent for Cleaning and Verification Sampling of NASA Propulsion Oxygen Systems Hardware, Ground Support Equipment, and Associated Test Systems.” The test methods used in this study for nonvolatile residue (NVR) background, materials compatibility, and cleaning effectiveness were different than those used for the RPT project; a smaller set of materials and contaminants were tested. The tests for this study were complementary to and provided supplementary information for the down-selection process during the course of the test program reported in NASA/TP-2015-218207.
Runtime Verification is a light-weight approach to systems verification, where actual executions of a system are processed and analyzed using rigorous techniques. In this paper we shall narrow the term’s definition to represent the commonly studied variant consisting of verifying that a single system execution conforms to a specification written in a formal specification language. Runtime verification (in this sense) can be used for writing test oracles during testing when the system is too complex for full formal verification, or it can be used during deployment of the system as part of a fault protection strategy, where corrective actions may be taken in case the specification is violated. Specification languages for runtime verification appear to differ from for example temporal logics applied in model checking, in part due to the focus on monitoring of events that carry data, and specifically due to the desire to relate data values existing at different time points, resulting in new challenges in both the complexity of the monitoring approach and the expressiveness of languages. Over the recent years, numerous runtime verification specification languages have emerged, each with its different features and levels of expressiveness and usability. This paper presents an overview and a discussion of this design space.
This publication contains the proceedings of the Second NASA Formal Methods Symposium sponsored by the National Aeronautics and Space Administration and held in Washington D.C. April 13-15, 2010. Topics covered include: Decision Engines for Software Analysis using Satisfiability Modulo Theories Solvers; Verification and Validation of Flight-Critical Systems; Formal Methods at Intel -- An Overview; Automatic Review of Abstract State Machines by Meta Property Verification; Hardware-independent Proofs of Numerical Programs; Slice-based Formal Specification Measures -- Mapping Coupling and Cohesion Measures to Formal Z; How Formal Methods Impels Discovery: A Short History of an Air Traffic Management Project; A Machine-Checked Proof of A State-Space Construction Algorithm; Automated Assume-Guarantee Reasoning for Omega-Regular Systems and Specifications; Modeling Regular Replacement for String Constraint Solving; Using Integer Clocks to Verify the Timing-Sync Sensor Network Protocol; Can Regulatory Bodies Expect Efficient Help from Formal Methods?; Synthesis of Greedy Algorithms Using Dominance Relations; A New Method for Incremental Testing of Finite State Machines; Verification of Faulty Message Passing Systems with Continuous State Space in PVS; Phase Two Feasibility Study for Software Safety Requirements Analysis Using Model Checking; A Prototype Embedding of Bluespec System Verilog in the PVS Theorem Prover; SimCheck: An Expressive Type System for Simulink; Coverage Metrics for Requirements-Based Testing: Evaluation of Effectiveness; Software Model Checking of ARINC-653 Flight Code with MCP; Evaluation of a Guideline by Formal Modelling of Cruise Control System in Event-B; Formal Verification of Large Software Systems; Symbolic Computation of Strongly Connected Components Using Saturation; Towards the Formal Verification of a Distributed Real-Time Automotive System; Slicing AADL Specifications for Model Checking; Model Checking with Edge-valued Decision Diagrams; and Data-flow based Model Analysis.
Aspects of Space Station automated systems testing and verification are discussed, taking into account several program requirements. It is found that these requirements lead to a number of issues of uncertainties which require study and resolution during the Space Station definition phase. Most, if not all, of the considered uncertainties have implications for the overall testing and verification strategy adopted by the Space Station Program. A description is given of the Galileo Orbiter fault protection design/verification approach. Attention is given to a mission description, an Orbiter description, the design approach and process, the fault protection design verification approach/process, and problems of 'stress' testing.