Search NASA⌕ Search

SEARCH · Search NASA

Results for “checking”

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.

At least 559 records · Page 31
All sourcesNASA NTRSDOE OSTI
NASA NTRS2002

Launch Vehicle Sizing Benefits Utilizing Main Propulsion System Crossfeed and Project Status

To meet the goals for a next generation Reusable Launch Vehicle (RLV), a unique propulsion feed system concept was identified using crossfeed between the booster and orbiter stages that could reduce the Two-Stage-to-Orbit (TSTO) vehicle weight and Design, Development, Test and Evaluation (DDT&E) costs by approximately 25%, while increasing safety and reliability. The Main Propulsion System (MPS) crossfeed water demonstration test program addresses all activities required to reduce the risks for the MPS crossfeed system from a Technology Readiness Level (TRL) of 2 to 4 by the completion of testing and analysis by June 2003. During the initial period, that ended in March 2002, a subscale water flow test article was defined. Procurement of a subscale crossfeed check valve was initiated and the specifications for the various components were developed. The fluid transient and pressurization analytical models were developed separately and successfully integrated. The test matrix for the water flow test was developed to correlate the integrated model. A computational fluid dynamics (CFD) model of the crossfeed check valve was developed to assess flow disturbances and internal flow dynamics. Based on the results, the passive crossfeed system concept was very feasible and offered a safe system to be used in an RLV architecture. A water flow test article was designed to accommodate a wide range of flows simulating a number of different types of propellant systems. During the follow-on period, the crossfeed system model will be further refined, the test article will be completed, the water flow test will be performed, and finally the crossfeed system model will be correlated with the test data. This validated computer model will be used to predict the full-scale vehicle crossfeed system performance.

Chandler, Frank↗
NASA NTRS2002

An Overview of the Runtime Verification Tool Java PathExplorer

We present an overview of the Java PathExplorer runtime verification tool, in short referred to as JPAX. JPAX can monitor the execution of a Java program and check that it conforms with a set of user provided properties formulated in temporal logic. JPAX can in addition analyze the program for concurrency errors such as deadlocks and data races. The concurrency analysis requires no user provided specification. The tool facilitates automated instrumentation of a program's bytecode, which when executed will emit an event stream, the execution trace, to an observer. The observer dispatches the incoming event stream to a set of observer processes, each performing a specialized analysis, such as the temporal logic verification, the deadlock analysis and the data race analysis. Temporal logic specifications can be formulated by the user in the Maude rewriting logic, where Maude is a high-speed rewriting system for equational logic, but here extended with executable temporal logic. The Maude rewriting engine is then activated as an event driven monitoring process. Alternatively, temporal specifications can be translated into efficient automata, which check the event stream. JPAX can be used during program testing to gain increased information about program executions, and can potentially furthermore be applied during operation to survey safety critical systems.

Havelund, Klaus↗
NASA NTRS2002

Program Instrumentation and Trace Analysis

Several attempts have been made recently to apply techniques such as model checking and theorem proving to the analysis of programs. This shall be seen as a current trend to analyze real software systems instead of just their designs. This includes our own effort to develop a model checker for Java, the Java PathFinder 1, one of the very first of its kind in 1998. However, model checking cannot handle very large programs without some kind of abstraction of the program. This paper describes a complementary scalable technique to handle such large programs. Our interest is turned on the observation part of the equation: How much information can be extracted about a program from observing a single execution trace? It is our intention to develop a technology that can be applied automatically and to large full-size applications, with minimal modification to the code. We present a tool, Java PathExplorer (JPaX), for exploring execution traces of Java programs. The tool prioritizes scalability for completeness, and is directed towards detecting errors in programs, not to prove correctness. One core element in JPaX is an instrumentation package that allows to instrument Java byte code files to log various events when executed. The instrumentation is driven by a user provided script that specifies what information to log. Examples of instructions that such a script can contain are: 'report name and arguments of all called methods defined in class C, together with a timestamp'; 'report all updates to all variables'; and 'report all acquisitions and releases of locks'. In more complex instructions one can specify that certain expressions should be evaluated and even that certain code should be executed under various conditions. The instrumentation package can hence be seen as implementing Aspect Oriented Programming for Java in the sense that one can add functionality to a Java program without explicitly changing the code of the original program, but one rather writes an aspect and compiles it into the original program using the instrumentation. Another core element of JPaX is an observation package that supports the analysis of the generated event stream. Two kinds of analysis are currently supported. In temporal analysis the execution trace is evaluated against formulae written in temporal logic. We have implemented a temporal logic evaluator on finite traces using the Maude rewriting system from SRI International, USA. Temporal logic is defined in Maude by giving its syntax as a signature and its semantics as rewrite equations. The resulting semantics is extremely efficient and can handle event streams of hundreds of millions events in few minutes. Furthermore, the implementation is very succinct. The second form of even stream analysis supported is error pattern analysis where an execution trace is analyzed using various error detection algorithms that can identify error-prone programming practices that may potentially lead to errors in some different executions. Two such algorithms focusing on concurrency errors have been implemented in JPaX, one for deadlocks and the other for data races. It is important to note, that a deadlock or data race potential does not need to occur in order for its potential to be detected with these algorithms. This is what makes them very scalable in practice. The data race algorithm implemented is the Eraser algorithm from Compaq, however adopted to Java. The tool is currently being applied to a code base for controlling a spacecraft by the developers of that software in order to evaluate its applicability.

Havelund, Klaus↗
NASA NTRS2001

Runtime Analysis of Linear Temporal Logic Specifications

This report presents an approach to checking a running program against its Linear Temporal Logic (LTL) specifications. LTL is a widely used logic for expressing properties of programs viewed as sets of executions. Our approach consists of translating LTL formulae to finite-state automata, which are used as observers of the program behavior. The translation algorithm we propose modifies standard LTL to B chi automata conversion techniques to generate automata that check finite program traces. The algorithm has been implemented in a tool, which has been integrated with the generic JPaX framework for runtime analysis of Java programs.

Giannakopoulou, Dimitra↗
NASA NTRS2002

What Went Wrong: Explaining Counterexamples

Model checking, initially successful in the field of hardware design, has recently been applied to software. One of the chief advantages of model checking is the production of counterexamples demonstrating that a system does not satisfy a speci cation. However, it may require a great deal of human effort to extract the essence of an error from even a detailed source-level trace of a failing run. We use an automated method for nding multiple versions of an error (and similar executions that do not produce an error), and analyze these executions to produce a more succinct description of the key elements of the error. The description produced includes identi cation of portions of the source code crucial to distinguishing failing and succeeding runs, di erences in invariants between failing and non-failing runs, and information on the necessary changes in scheduling and environmental actions needed to cause suc- cessful runs to fail. In addition, this analysis allows a classi cation of errors by features such as whether they are purely concurrent (i.e. can be induced by changing only thread scheduling).

Groce, Alex↗
NASA NTRS2002

Pressure-Application Device for Testing Pressure Sensors

A portable pressure-application device has been designed and built for use in testing and calibrating piezoelectric pressure transducers in the field. The device generates pressure pulses of known amplitude. A pressure pulse (in contradistinction to a steady pressure) is needed because in the presence of a steady pressure, the electrical output of a piezoelectric pressure transducer decays rapidly with time. The device includes a stainless- steel compressed-air-storage cylinder of 500 cu cm volume. A manual hand pump with check valves and a pressure gauge are located at one end of the cylinder. A three-way solenoid valve that controls the release of pressurized air is located at the other end of the cylinder. Power for the device is provided by a 3.7-V cordless-telephone battery. The valve is controlled by means of a pushbutton switch, which activates a 5 V to +/-15 V DC-to-DC converter that powers the solenoid. The outlet of the solenoid valve is connected to the pressure transducer to be tested. Before the solenoid is energized, the transducer to be tested is at atmospheric pressure. When the solenoid is actuated by the push button, pressurized air from inside the cylinder is applied to the transducer. Once the pushbutton is released, the cylinder pressure is removed from the transducer and the pressurized air applied to the transducer is vented, bringing the transducer back to atmospheric pressure. Before this device was used for actual calibration, its accuracy was checked with a NIST (National Institute of Standards and Technology) traceable calibrator and commercially calibrated pressure transducers. This work was done by Wanda Solano of Stennis Space Center and Greg Richardson of Lockheed Martin Corp.

Source record↗
NASA NTRS2004

Applying Jlint to Space Exploration Software

Java is a very successful programming language which is also becoming widespread in embedded systems, where software correctness is critical. Jlint is a simple but highly efficient static analyzer that checks a Java program for several common errors, such as null pointer exceptions, and overflow errors. It also includes checks for multi-threading problems, such as deadlocks and data races. The case study described here shows the effectiveness of Jlint in find-false positives in the multi-threading warnings gives an insight into design patterns commonly used in multi-threaded code. The results show that a few analysis techniques are sufficient to avoid almost all false positives. These techniques include investigating all possible callers and a few code idioms. Verifying the correct application of these patterns is still crucial, because their correct usage is not trivial.

Artho, Cyrille↗
NASA NTRS2003

Teaching Cockpit Automation in the Classroom

This study explores the idea of teaching fundamental cockpit automation concepts and skills to aspiring professional pilots in a classroom setting, without the use of sophisticated aircraft or equipment simulators. Pilot participants from a local professional pilot academy completed eighteen hours of classroom instruction that placed a strong emphasis on understanding the underlying principles of cockpit automation systems and their use in a multi-crew cockpit. The instructional materials consisted solely of a single textbook. Pilots received no hands-on instruction or practice during their training. At the conclusion of the classroom instruction, pilots completed a written examination testing their mastery of what had been taught during the classroom meetings. Following the written exam, each pilot was given a check flight in a full-mission Level D simulator of a Boeing 747-400 aircraft. Pilots were given the opportunity to fly one practice leg, and were then tested on all concepts and skills covered in the class during a second leg. The results of the written exam and simulator checks strongly suggest that instruction delivered in a traditional classroom setting can lead to high levels of preparation without the need for expensive airplane or equipment simulators.

Casner, Stephen M.↗
NASA NTRS2003

Sodium Heat Pipe Module Processing For the SAFE-100 Reactor Concept

To support development and hardware-based testing of various space reactor concepts, the Early Flight Fission-Test Facility (EFF-TF) team established a specialized glove box unit with ancillary systems to handle/process alkali metals. Recently, these systems have been commissioned with sodium supporting the fill of stainless steel heat pipe modules for use with a 100 kW thermal heat pipe reactor design. As part of this effort, procedures were developed and refined to govern each segment of the process covering: fill, leak check, vacuum processing, weld closeout, and final "wet in". A series of 316 stainless steel modules, used as precursors to the actual 321 stainless steel modules, were filled with 35 +/- 1 grams of sodium using a known volume canister to control the dispensed mass. Each module was leak checked to less than10(exp -10) std cc/sec helium and vacuum conditioned at 250 C to assist in the removal of trapped gases. A welding procedure was developed to close out the fill stem preventing external gases from entering the evacuated module. Finally the completed modules were vacuum fired at 750 C allowing the sodium to fully wet the internal surface and wick structure of the heat pipe module.

Martin, James↗
NASA NTRS2003

The Application of Lidar to Synthetic Vision System Integrity

One goal in the development of a Synthetic Vision System (SVS) is to create a system that can be certified by the Federal Aviation Administration (FAA) for use at various flight criticality levels. As part of NASA s Aviation Safety Program, Ohio University and NASA Langley have been involved in the research and development of real-time terrain database integrity monitors for SVS. Integrity monitors based on a consistency check with onboard sensors may be required if the inherent terrain database integrity is not sufficient for a particular operation. Sensors such as the radar altimeter and weather radar, which are available on most commercial aircraft, are currently being investigated for use in a real-time terrain database integrity monitor. This paper introduces the concept of using a Light Detection And Ranging (LiDAR) sensor as part of a real-time terrain database integrity monitor. A LiDAR system consists of a scanning laser ranger, an inertial measurement unit (IMU), and a Global Positioning System (GPS) receiver. Information from these three sensors can be combined to generate synthesized terrain models (profiles), which can then be compared to the stored SVS terrain model. This paper discusses an initial performance evaluation of the LiDAR-based terrain database integrity monitor using LiDAR data collected over Reno, Nevada. The paper will address the consistency checking mechanism and test statistic, sensitivity to position errors, and a comparison of the LiDAR-based integrity monitor to a radar altimeter-based integrity monitor.

Campbell, Jacob L.↗
NASA NTRS2004

Software Safety Analysis of a Flight Guidance System

This document summarizes the safety analysis performed on a Flight Guidance System (FGS) requirements model. In particular, the safety properties desired of the FGS model are identified and the presence of the safety properties in the model is formally verified. Chapter 1 provides an introduction to the entire project, while Chapter 2 gives a brief overview of the problem domain, the nature of accidents, model based development, and the four-variable model. Chapter 3 outlines the approach. Chapter 4 presents the results of the traditional safety analysis techniques and illustrates how the hazardous conditions associated with the system trace into specific safety properties. Chapter 5 presents the results of the formal methods analysis technique model checking that was used to verify the presence of the safety properties in the requirements model. Finally, Chapter 6 summarizes the main conclusions of the study, first and foremost that model checking is a very effective verification technique to use on discrete models with reasonable state spaces. Additional supporting details are provided in the appendices.

Butler, Ricky W.↗
NASA NTRS2004

Portable Wireless LAN Device and Two-Way Radio Threat Assessment for Aircraft VHF Communication Radio Band

This document summarizes the safety analysis performed on a Flight Guidance System (FGS) requirements model. In particular, the safety properties desired of the FGS model are identified and the presence of the safety properties in the model is formally verified. Chapter 1 provides an introduction to the entire project, while Chapter 2 gives a brief overview of the problem domain, the nature of accidents, model based development, and the four-variable model. Chapter 3 outlines the approach. Chapter 4 presents the results of the traditional safety analysis techniques and illustrates how the hazardous conditions associated with the system trace into specific safety properties. Chapter 5 presents the results of the formal methods analysis technique model checking that was used to verify the presence of the safety properties in the requirements model. Finally, Chapter 6 summarizes the main conclusions of the study, first and foremost that model checking is a very effective verification technique to use on discrete models with reasonable state spaces. Additional supporting details are provided in the appendices.

Nguyen, Truong X.↗
NASA NTRS2004

Verification of Java Programs using Symbolic Execution and Invariant Generation

Software verification is recognized as an important and difficult problem. We present a norel framework, based on symbolic execution, for the automated verification of software. The framework uses annotations in the form of method specifications an3 loop invariants. We present a novel iterative technique that uses invariant strengthening and approximation for discovering these loop invariants automatically. The technique handles different types of data (e.g. boolean and numeric constraints, dynamically allocated structures and arrays) and it allows for checking universally quantified formulas. Our framework is built on top of the Java PathFinder model checking toolset and it was used for the verification of several non-trivial Java programs.

Pasareanu, Corina↗
NASA NTRS2004

Manipulation of Microenvironment with a Built-in Electrochemical Actuator in Proximity of a Dissolved Oxygen Microsensor

Abstract - Biochemical sensors for continuous monitoring require dependable periodic self- diagnosis with acceptable simplicity to check its functionality during operation. An in situ self- diagnostic technique for a dissolved oxygen microsensor is proposed in an effort to devise an intelligent microsensor system with an integrated electrochemical actuation electrode. With a built- in platinum microelectrode that surrounds the microsensor, two kinds of microenvironments, called the oxygen-saturated or oxygen-depleted phases, can be created by water electrolysis depending on the polarity. The functionality of the microsensor can be checked during these microenvironment phases. The polarographic oxygen microsensor is fabricated on a flexible polyimide substrate (Kapton) and the feasibility of the proposed concept is demonstrated in a physiological solution. The sensor responds properly during the oxygen-generating and oxygen- depleting phases. The use of these microenvironments for in situ self-calibration is discussed to achieve functional integration as well as structural integration of the microsensor system.

Kim, Chang-Soo↗
NASA NTRS2004

Variable Step Integration Coupled with the Method of Characteristics Solution for Water-Hammer Analysis, A Case Study

One-dimensional water-hammer modeling involves the solution of two coupled non-linear hyperbolic partial differential equations (PDEs). These equations result from applying the principles of conservation of mass and momentum to flow through a pipe, and usually the assumption that the speed at which pressure waves propagate through the pipe is constant. In order to solve these equations for the interested quantities (i.e. pressures and flow rates), they must first be converted to a system of ordinary differential equations (ODEs) by either approximating the spatial derivative terms with numerical techniques or using the Method of Characteristics (MOC). The MOC approach is ideal in that no numerical approximation errors are introduced in converting the original system of PDEs into an equivalent system of ODEs. Unfortunately this resulting system of ODEs is bound by a time step constraint so that when integrating the equations the solution can only be obtained at fixed time intervals. If the fluid system to be modeled also contains dynamic components (i.e. components that are best modeled by a system of ODEs), it may be necessary to take extremely small time steps during certain points of the model simulation in order to achieve stability and/or accuracy in the solution. Coupled together, the fixed time step constraint invoked by the MOC, and the occasional need for extremely small time steps in order to obtain stability and/or accuracy, can greatly increase simulation run times. As one solution to this problem, a method for combining variable step integration (VSI) algorithms with the MOC was developed for modeling water-hammer in systems with highly dynamic components. A case study is presented in which reverse flow through a dual-flapper check valve introduces a water-hammer event. The predicted pressure responses upstream of the check-valve are compared with test data.

Turpin, Jason B.↗
NASA NTRS2004

An Empirical Evaluation of Automated Theorem Provers in Software Certification

We describe a system for the automated certification of safety properties of NASA software. The system uses Hoare-style program verification technology to generate proof obligations which are then processed by an automated first-order theorem prover (ATP). We discuss the unique requirements this application places on the ATPs, focusing on automation, proof checking, and usability. For full automation, however, the obligations must be aggressively preprocessed and simplified, and we demonstrate how the individual simplification stages, which are implemented by rewriting, influence the ability of the ATPs to solve the proof tasks. Our results are based on 13 certification experiments that lead to more than 25,000 proof tasks which have each been attempted by Vampire, Spass, e-setheo, and Otter. The proofs found by Otter have been proof-checked by IVY.

Denney, Ewen↗
NASA NTRS2001

Flight Test Results of a Synthetic Vision Elevation Database Integrity Monitor

This paper discusses the flight test results of a real-time Digital Elevation Model (DEM) integrity monitor for Civil Aviation applications. Providing pilots with Synthetic Vision (SV) displays containing terrain information has the potential to improve flight safety by improving situational awareness and thereby reducing the likelihood of Controlled Flight Into Terrain (CFIT). Utilization of DEMs, such as the digital terrain elevation data (DTED), requires a DEM integrity check and timely integrity alerts to the pilots when used for flight-critical terrain-displays, otherwise the DEM may provide hazardous misleading terrain information. The discussed integrity monitor checks the consistency between a terrain elevation profile synthesized from sensor information, and the profile given in the DEM. The synthesized profile is derived from DGPS and radar altimeter measurements. DEMs of various spatial resolutions are used to illustrate the dependency of the integrity monitor s performance on the DEMs spatial resolution. The paper will give a description of proposed integrity algorithms, the flight test setup, and the results of a flight test performed at the Ohio University airport and in the vicinity of Asheville, NC.

deHaag, Maarten Uijt↗
NASA NTRS2004

Performance Trade-Offs for MBG Using Different Bandgap Pairs

Present GAInP2/GAAs cell grown on Ge (or GaAs) substrates have demonstrates high efficiency, However, the individual bandgaps (1.85 eV, 1.42 eV respectively) are not the optimum match to convert the AM0 spectrum efficiently, although by reducing the thickness of the GaInP2 cell, good efficiencies have been achieved. Within the III-V alloys, modeling shows that several dual junction cells, comprising different bandgap pairs, could give higher efficiency. This paper outlines the modeling used, the bandgap pairs selected, and projections for the AM0 efficiency assuming that the effects of lattice mismatch associated with the bandgap can be reduced. We also present preliminary data on I-V performance for the selected top and bottom cells and for some full cascade cells. We have included some characterization results to check the bandgaps and lattice strain, to check how closely the fabricated cells conform to the model,

Iles, P. A.↗