Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “error detection”

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 433 records · Page 24
All sourcesNASA NTRSDOE OSTI
NASA NTRS2001

Java PathExplorer: A Runtime Verification Tool

We describe recent work on designing an environment called Java PathExplorer for monitoring the execution of Java programs. This environment facilitates the testing of execution traces against high level specifications, including temporal logic formulae. In addition, it contains algorithms for detecting classical error patterns in concurrent programs, such as deadlocks and data races. An initial prototype of the tool has been applied to the executive module of the planetary Rover K9, developed at NASA Ames. In this paper we describe the background and motivation for the development of this tool, including comments on how it relates to formal methods tools as well as to traditional testing, and we then present the tool itself.

Havelund, Klaus↗
NASA NTRS2003

Experiments with Test Case Generation and Runtime Analysis

Software testing is typically an ad hoc process where human testers manually write many test inputs and expected test results, perhaps automating their execution in a regression suite. This process is cumbersome and costly. This paper reports preliminary results on an approach to further automate this process. The approach consists of combining automated test case generation based on systematically exploring the program's input domain, with runtime analysis, where execution traces are monitored and verified against temporal logic specifications, or analyzed using advanced algorithms for detecting concurrency errors such as data races and deadlocks. The approach suggests to generate specifications dynamically per input instance rather than statically once-and-for-all. The paper describes experiments with variants of this approach in the context of two examples, a planetary rover controller and a space craft fault protection system.

Artho, Cyrille↗
NASA NTRS2002

Formal verification of human-automation interaction

This paper discusses a formal and rigorous approach to the analysis of operator interaction with machines. It addresses the acute problem of detecting design errors in human-machine interaction and focuses on verifying the correctness of the interaction in complex and automated control systems. The paper describes a systematic methodology for evaluating whether the interface provides the necessary information about the machine to enable the operator to perform a specified task successfully and unambiguously. It also addresses the adequacy of information provided to the user via training material (e.g., user manual) about the machine's behavior. The essentials of the methodology, which can be automated and applied to the verification of large systems, are illustrated by several examples and through a case study of pilot interaction with an autopilot aboard a modern commercial aircraft. The expected application of this methodology is an augmentation and enhancement, by formal verification, of human-automation interfaces.

Aviation↗
NASA NTRS2004

The Curious Behavior of PSR JO537-6910

We report results from an extensive timing monitoring campaign of PSR JO537-6910, the 16-ms pulsar in the Large Magellanic Cloud, The source has been monitored using the Rossi X-ray Timing Explorer since January, 1999, and at least 18 glitches in its rotation rate have been seen. Despite this extreme activity, phase-connected timing solutions are maintained between the glitches. In addition to its high rotation rate and frequent large glitches, the pulsar has other unusual characteristics. First, a precursor is sometimes seen before the large glitches in which a large phase error is detected several days before the glitch. with no measurable change in pulsar frequency. Second, the size of a glitch is correlated with the time since the previous glitch. Third, phases measured during observations for several weeks after a glitch are often slightly below the extrapolation of best-fit model for the subsequent post-glitch data. It appears that a small fraction of the sudden increase in frequency decays with an e-folding time scale of about a week. We discuss the implications of these phenomena.

Marshall, Francis E.↗
NASA NTRS2004

Mars Exploration Rovers orbit determination filter strategy

The successful delivery of the Mars Exploration Rover (MER) landers to well within the boundaries of their surface target areas in January of 2004 was the culmination of years of orbit determination analysis. The process began with a careful consideration of the filter parameters used for pre-launch covariance studies, and continued with the refinement of the filter after launch based on operational experience. At the same time, tools were developed to run a plethora of variations around the nominal filter and analyze the results in ways that had never been previously attempted for an interplanetary mission. In addition to achieving sub-kilometer Mars-relative orbit determination knowledge, the filter strategy and process detected unexpected error sources, while at the same time proving robust by indicating thecorrect solution. Consequently, MER orbit determination set a new standard for interplanetary navigation.

Mars Exploration Rover (MER)↗
NASA NTRS2007

Definition and maintenance of a telemetry database dictionary

A telemetry dictionary database includes a component for receiving spreadsheet workbooks of telemetry data over a web-based interface from other computer devices. Another component routes the spreadsheet workbooks to a specified directory on the host processing device. A process then checks the received spreadsheet workbooks for errors, and if no errors are detected the spreadsheet workbooks are routed to another directory to await initiation of a remote database loading process. The loading process first converts the spreadsheet workbooks to comma separated value (CSV) files. Next, a network connection with the computer system that hosts the telemetry dictionary database is established and the CSV files are ported to the computer system that hosts the telemetry dictionary database. This is followed by a remote initiation of a database loading program. Upon completion of loading a flatfile generation program is manually initiated to generate a flatfile to be used in a mission operations environment by the core ground system.

Knopf, William P.↗
NASA NTRS2008

Orchestrator Telemetry Processing Pipeline

Orchestrator is a software application infrastructure for telemetry monitoring, logging, processing, and distribution. The architecture has been applied to support operations of a variety of planetary rovers. Built in Java with the Eclipse Rich Client Platform, Orchestrator can run on most commonly used operating systems. The pipeline supports configurable parallel processing that can significantly reduce the time needed to process a large volume of data products. Processors in the pipeline implement a simple Java interface and declare their required input from upstream processors. Orchestrator is programmatically constructed by specifying a list of Java processor classes that are initiated at runtime to form the pipeline. Input dependencies are checked at runtime. Fault tolerance can be configured to attempt continuation of processing in the event of an error or failed input dependency if possible, or to abort further processing when an error is detected. This innovation also provides support for Java Message Service broadcasts of telemetry objects to clients and provides a file system and relational database logging of telemetry. Orchestrator supports remote monitoring and control of the pipeline using browser-based JMX controls and provides several integration paths for pre-compiled legacy data processors. At the time of this reporting, the Orchestrator architecture has been used by four NASA customers to build telemetry pipelines to support field operations. Example applications include high-volume stereo image capture and processing, simultaneous data monitoring and logging from multiple vehicles. Example telemetry processors used in field test operations support include vehicle position, attitude, articulation, GPS location, power, and stereo images.

Powell, Mark↗
NASA NTRS2009

Systems and methods for detecting a failure event in a field programmable gate array

An embodiment generally relates to a method of self-detecting an error in a field programmable gate array (FPGA). The method includes writing a signature value into a signature memory in the FPGA and determining a conclusion of a configuration refresh operation in the FPGA. The method also includes reading an outcome value from the signature memory.

Ng, Tak-Kwong↗
NASA NTRS2010

SimCheck: An Expressive Type System for Simulink

MATLAB Simulink is a member of a class of visual languages that are used for modeling and simulating physical and cyber-physical systems. A Simulink model consists of blocks with input and output ports connected using links that carry signals. We extend the type system of Simulink with annotations and dimensions/units associated with ports and links. These types can capture invariants on signals as well as relations between signals. We define a type-checker that checks the wellformedness of Simulink blocks with respect to these type annotations. The type checker generates proof obligations that are solved by SRI's Yices solver for satisfiability modulo theories (SMT). This translation can be used to detect type errors, demonstrate counterexamples, generate test cases, or prove the absence of type errors. Our work is an initial step toward the symbolic analysis of MATLAB Simulink models.

Roy, Pritam↗
NASA NTRS2010

The Geostationary Operational Satellite R Series SpaceWire Based Data System Architecture

The GOES-R program selected SpaceWire as the best solution to satisfy the desire for simple and flexible instrument to spacecraft command and telemetry communications. Data generated by GOES-R instruments is critical for meteorological forecasting, public safety, space weather, and other key applications. In addition, GOES-R instrument data is provided to ground stations on a 24/7 basis. GOES-R requires data errors be detected and corrected from origin to final destination. This paper describes GOES-R developed strategy to satisfy this requirement

Krimchansky, Alexander↗
NASA NTRS2009

A Game-Theoretic Approach to Branching Time Abstract-Check-Refine Process

Since the complexity of software systems continues to grow, most engineers face two serious problems: the state space explosion problem and the problem of how to debug systems. In this paper, we propose a game-theoretic approach to full branching time model checking on three-valued semantics. The three-valued models and logics provide successful abstraction that overcomes the state space explosion problem. The game style model checking that generates counter-examples can guide refinement or identify validated formulas, which solves the system debugging problem. Furthermore, output of our game style method will give significant information to engineers in detecting where errors have occurred and what the causes of the errors are.

Wang, Yi↗
NASA NTRS2012

Method and system for redundancy management of distributed and recoverable digital control system

A method and system for redundancy management is provided for a distributed and recoverable digital control system. The method uses unique redundancy management techniques to achieve recovery and restoration of redundant elements to full operation in an asynchronous environment. The system includes a first computing unit comprising a pair of redundant computational lanes for generating redundant control commands. One or more internal monitors detect data errors in the control commands, and provide a recovery trigger to the first computing unit. A second redundant computing unit provides the same features as the first computing unit. A first actuator control unit is configured to provide blending and monitoring of the control commands from the first and second computing units, and to provide a recovery trigger to each of the first and second computing units. A second actuator control unit provides the same features as the first actuator control unit.

Stange, Kent↗
NASA NTRS2013

Comparison of Force and Moment Coefficients for the Same Test Article in Multiple Wind Tunnels

This paper compares the results of force and moment measurements made on the same test article and with the same balance in three transonic wind tunnels. Comparisons are made for the same combination of Reynolds number, Mach number, sideslip angle, control surface configuration, and angle of attack range. Between-tunnel force and moment differences are quantified. An analysis of variance was performed at four unique sites in the design space to assess the statistical significance of between-tunnel variation and any interaction with angle of attack. Tunnel to tunnel differences too large to attribute to random error were detected were observed for all forces and moments. In some cases these differences were independent of angle of attack and in other cases they changed with angle of attack.

Deloach, Richard↗
NASA NTRS2014

Property Differencing for Incremental Checking

This paper introduces iProperty, a novel approach that facilitates incremental checking of programs based on a property di erencing technique. Speci cally, iProperty aims to reduce the cost of checking properties as they are initially developed and as they co-evolve with the program. The key novelty of iProperty is to compute the di erences between the new and old versions of expected properties to reduce the number and size of the properties that need to be checked during the initial development of the properties. Furthermore, property di erencing is used in synergy with program behavior di erencing techniques to optimize common regression scenarios, such as detecting regression errors or checking feature additions for conformance to new expected properties. Experimental results in the context of symbolic execution of Java programs annotated with properties written as assertions show the e ectiveness of iProperty in utilizing change information to enable more ecient checking.

Yang, Guowei↗
NASA NTRS2013

CALIOP and AERONET Aerosol Optical Depth Comparisons: One Size Fits None

We compare the aerosol optical depths (AOD) retrieved from backscatter measurements of the Cloud-Aerosol Lidar with Orthogonal Polarization (CALIOP) aboard the Cloud Aerosol Lidar Infrared Pathfinder Satellite Observations (CALIPSO) satellite with coincident Aerosol Robotic Network (AERONET) measurements. Overpass coincidence criteria of +/- 2 h and within a 40 km radius are satisfied at least once at 149 globally distributed AERONET sites from 2006 to 2010. Most data pairs (>80%) use AERONET measurements acquired +/- 30 min of the overpass. We examine the differences in AOD estimates between CALIOP and AERONET for various aerosol, environmental, and geographic conditions. Results show CALIOP AOD are lower than AERONET AOD especially at low optical depths as measured by AERONET (500 nm AOD<0.1). Furthermore, the median relative AOD difference between the two measurements is 25% of the AERONET AOD for AOD>0.1. Differences in AOD between CALIOP and AERONET are possibly due to cloud contamination, scene inhomogeneity, instrument view angle differences, CALIOP retrieval errors, and detection limits. Comparison of daytime to nighttime number of 5 km 60m (60m in the vertical) features detected by CALIOP show that there are 20% more aerosol features at night. We find that CALIPSO and AERONET do not agree on the cloudiness of scenes. Of the scenes that meet the above coincidence criteria, CALIPSO finds clouds in more than 45% of the coincident atmospheric columns AERONET classifies as clear.

Omar, A. H.↗