SEARCH · Search NASA

Results for “latent error”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 19 records

All sources NASA NTRS DOE OSTI

NASA NTRS1984

A model for the prediction of latent errors using data obtained during the development process

A model implemented in a program that runs on the IBM PC for estimating the latent (or post ship) content of a body of software upon its initial release to the user is presented. The model employs the count of errors discovered at one or more of the error discovery processes during development, such as a design inspection, as the input data for a process which provides estimates of the total life-time (injected) error content and of the latent (or post ship) error content--the errors remaining a delivery. The model presented presumes that these activities cover all of the opportunities during the software development process for error discovery (and removal).

Gaffney, J. E., Jr.↗

DOE OSTI2022

EFCOG Best Practice HPI for Knowledge Workers ISM-HPI-22-02

This document is a collection of these best practices as determined by team members. This best practice attempts to: Realize opportunities to break the myth where people believe that HPI does not apply to them as they perform no physical work. Recommend options to create an environment that promotes intellectual collaboration and trust, enabling candor and vulnerability. Explain how errors manifest differently from the same human fallibility. Knowledge workers (KW) have errors that take different perspectives to find and mitigate the unique manifestation of these conditions. Help KW identify the critical steps (or risk important steps) in their processes. Reduce risk/consequence from KW errors (limit latent errors as well as finding latent conditions), building resiliency into KW tasks. Mitigation strategies may be different.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

NASA NTRS1994

A rose by any other name: Certification seen as process rather than content

Green (1990) believes that the two main factors safeguarding flying from human error are both related to certification and regulation. First is the increasingly proceduralized nature of flying whereby as much as possible is reduced to a rule-based activity. Second is the emphasis placed upon training and competency checking of aircrew in simulators and in the air, both generally and for all particular types of aircraft flown. This leaves, believes Green, other human factors that are relatively unaddressed as yet and which can give rise to human reliability problems. These include: hardware factors and especially pilot/co-pilot relationships; and system factors including fatigue and cost/safety trade-offs. He also, importantly, identifies problems with the integration of the 'electronic crew member' following increased automation. Human reliability failures with artificial intelligence and automation, due to over-reliance on the system fail-safe mechanisms, or to operator under- confidence in the integrity or self-regulating capacity of the system, or to out-of-loop effects, are widely accepted as being due to deficiencies in plant design, planning, management and maintenance more than to 'operator error' - Reason's (1990) latent error or organization pathogens argument. Reliability failures in complex systems are well enough documented to give cause for concern and at least promote a debate on the merits of a full certification program. The purpose of this short paper is to seek out and explore what is valuable in certification, at the least to show that the benefits outweigh the disadvantages and at best to identify positive outcomes perhaps not obtainable in other ways. On both sides of the debate on certification there is general agreement on the need for a better human factors perspective and effort in complex aviation systems design. What is at issue is how this is to be promoted. It is incumbent upon opponents of certification to say how else such promotion be enabled. This is an exploratory and philosophical review, not a focused and specific one, and it will draw upon much that is not firmly in the domain of complex aviation systems.

Wilson, John R.↗

NASA NTRS1987

Measurement-based analysis of error latency

This paper demonstrates a practical methodology for the study of error latency under a real workload. The method is illustrated with sampled data on the physical memory activity, gathered by hardware instrumentation on a VAX 11/780 during the normal workload cycle of the installation. These data are used to simulate fault occurrence and to reconstruct the error discovery process in the system. The technique provides a means to study the system under different workloads and for multiple days. An approach to determine the percentage of undiscovered errors is also developed and a verification of the entire methodology is performed. This study finds that the mean error latency, in the memory containing the operating system, varies by a factor of 10 to 1 (in hours) between the low and high workloads. It is found that of all errors occurring within a day, 70 percent are detected in the same day, 82 percent within the following day, and 91 percent within the third day. The increase in failure rate due to latency is not so much a function of remaining errors but is dependent on whether or not there is a latent error.

Chillarege, Ram↗

NASA NTRS1983

Analysis of the impact of error detection on computer performance

Conventionally, reliability analyses either assume that a fault/error is detected immediately following its occurrence, or neglect damages caused by latent errors. Though unrealistic, this assumption was imposed in order to avoid the difficulty of determining the respective probabilities that a fault induces an error and the error is then detected in a random amount of time after its occurrence. As a remedy for this problem a model is proposed to analyze the impact of error detection on computer performance under moderate assumptions. Error latency, the time interval between occurrence and the moment of detection, is used to measure the effectiveness of a detection mechanism. This model is used to: (1) predict the probability of producing an unreliable result, and (2) estimate the loss of computation due to fault and/or error.

Shin, K. C.↗

NASA NTRS1991

Error latency measurements in symbolic architectures

Error latency, the time that elapses between the occurrence of an error and its detection, has a significant effect on reliability. In computer systems, failure rates can be elevated during a burst of system activity due to increased detection of latent errors. A hybrid monitoring environment is developed to measure the error latency distribution of errors occurring in main memory. The objective of this study is to develop a methodology for gauging the dependability of individual data categories within a real-time application. The hybrid monitoring technique is novel in that it selects and categorizes a specific subset of the available blocks of memory to monitor. The precise times of reads and writes are collected, so no actual faults need be injected. Unlike previous monitoring studies that rely on a periodic sampling approach or on statistical approximation, this new approach permits continuous monitoring of referencing activity and precise measurement of error latency.

Young, L. T.↗

DOE OSTI2016

Exploring versioned distributed arrays for resilience in scientific applications: Global view resilience

Exascale studies project reliability challenges for future HPC systems. We present the Global View Resilience (GVR) system, a library for portable resilience. GVR begins with a subset of the Global Arrays interface, and adds new capabilities to create versions, name versions, and compute on version data. Applications can focus versioning where and when it is most productive, and customize for each application structure independently. This control is portable, and its embedding in application source makes it natural to express and easy to maintain. The ability to name multiple versions and “partially materialize” them efficiently makes ambitious forward-recovery based on “data slices” across versions or data structures both easy to express and efficient. Using several large applications (OpenMC, preconditioned conjugate gradient (PCG) solver, ddcMD, and Chombo), we evaluate the programming effort to add resilience. The required changes are small (< 2% lines of code (LOC)), localized and machine-independent, and perhaps most important, require no software architecture changes. We also measure the overhead of adding GVR versioning and show that overheads < 2% are generally achieved. This overhead suggests that GVR can be implemented in large-scale codes and support portable error recovery with modest investment and runtime impact. Our results are drawn from both IBM BG/Q and Cray XC30 experiments, demonstrating portability. We also present two case studies of flexible error recovery, illustrating how GVR can be used for multi-version rollback recovery, and several different forward-recovery schemes. GVR’s multi-version enables applications to survive latent errors (silent data corruption) with significant detection latency, and forward recovery can make that recovery extremely efficient. Lastly, our results suggest that GVR is scalable, portable, and efficient. GVR interfaces are flexible, supporting a variety of recovery schemes, and altogether GVR embodies a gentle-slope path to tolerate growing error rates in future extreme-scale systems.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2015

A Review of Human Reliability Needs in the U.S. Nuclear Industry

In this survey, 34 subject matter experts from the U.S. nuclear industry were interviewed to determine specific needs for human reliability analysis (HRA). Conclusions from the interviews are detailed in this article. A summary of the findings includes: (1) The need for improved guidance on the use of HRA methods generally and for specific applications. (2) The need for additional training in HRA to provide more hands-on experience in the application of HRA methods. (3) Thedevelopment of HRA approaches suitable for advanced reactors, severe accident situations, and low-power and shutdown applications. (4) The refinement of HRA methods to account forfactors such as crew variability, latent errors, more sophisticated dependency modeling, and errors of commission. (5) The continued need for simplified HRA methods appropriate for field applications. (6) The need for tighter coupling of HRA and human factors. (7) The need for improvements in the quantitative basis of HRA methods. These findings suggest the field of HRA is mature but still benefits from refinements.

human reliability analysis↗

NASA NTRS1989

A methodology for validating software reliability

A significant problem associated with fault tolerant computer system design is how to insure that there are no embedded software errors, so that an avionics computer system meets the required reliability level. To accomplish this, it is necessary to associate a 'probability of failure' with the operational flight program. It would be more correct to say that the probability of excitation of existing latent design errors within the program is required. In this sense, latent software errors are like latent hardware faults, and techniques that were previously used to measure the probability of failure of hardware due to fault latency can be used to measure the probability of failure of the software. A methodology was developed and applied to a flight control program that was known to operate in a well defined environment. The results indicated that the technique could be used to provide a final validation of the software to a specified reliability level and to evaluate the role of flight test in software validation.

Swern, Frederic L.↗

DOE OSTI2014

Task Decomposition in Human Reliability Analysis

In the probabilistic safety assessments (PSAs) used in the nuclear industry, human failure events (HFEs) are determined as a subset of hardware failures, namely those hardware failures that could be triggered by human action or inaction. This approach is top-down, starting with hardware faults and deducing human contributions to those faults. Elsewhere, more traditionally human factors driven approaches would tend to look at opportunities for human errors first in a task analysis and then identify which of those errors is risk significant. The intersection of top-down and bottom-up approaches to defining HFEs has not been carefully studied. Ideally, both approaches should arrive at the same set of HFEs. This question remains central as human reliability analysis (HRA) methods are generalized to new domains like oil and gas. The HFEs used in nuclear PSAs tend to be top-down— defined as a subset of the PSA—whereas the HFEs used in petroleum quantitative risk assessments (QRAs) are more likely to be bottom-up—derived from a task analysis conducted by human factors experts. The marriage of these approaches is necessary in order to ensure that HRA methods developed for top-down HFEs are also sufficient for bottom-up applications.

error of commission↗

NASA NTRS2010

Injecting Errors for Testing Built-In Test Software

Two algorithms have been conceived to enable automated, thorough testing of Built-in test (BIT) software. The first algorithm applies to BIT routines that define pass/fail criteria based on values of data read from such hardware devices as memories, input ports, or registers. This algorithm simulates effects of errors in a device under test by (1) intercepting data from the device and (2) performing AND operations between the data and the data mask specific to the device. This operation yields values not expected by the BIT routine. This algorithm entails very small, permanent instrumentation of the software under test (SUT) for performing the AND operations. The second algorithm applies to BIT programs that provide services to users application programs via commands or callable interfaces and requires a capability for test-driver software to read and write the memory used in execution of the SUT. This algorithm identifies all SUT code execution addresses where errors are to be injected, then temporarily replaces the code at those addresses with small test code sequences to inject latent severe errors, then determines whether, as desired, the SUT detects the errors and recovers

Gender, Thomas K.↗

DOE OSTI2022

Estimation of Corn Latent Heat Flux from High Resolution Thermal Imagery

Crop evapotranspiration (ET), which is directly related to latent heat flux, is also a key indicator in determining the water status of crops. In order to estimate the latent heat flux, two-source energy balance (TSEB) models have been developed for thermal imagery from satellite platforms. However, because of the coarse resolution of thermal sensors on the satellite, distinguishing soil and vegetation is difficult which complicates the calculation process and introduces errors in latent heat estimates. In this research, high-resolution thermal datasets (0.05 m) and corresponding RGB datasets (0.03 m) were used for calculating crop latent heat flux using an adapted TSEB model. The RGB datasets were used for supervised classification of soil and vegetation, and the classification results were then used to filter the thermal mosaics to separate vegetation and soil temperatures. The vegetation temperature is used for calculating latent heat flux and the results are validated against the ground reference measurements of latent heat using a handheld porometer. The objective of this research is to introduce a workflow including an adapted TSEB model which is customized for high resolution thermal images from unmanned aircraft systems (UAS) to estimate the latent heat flux of row crops in agricultural fields. Nine dates of data collection in 2018 and 2020 have been evaluated and the root mean square error (RMSE) varies between 16 to 106 W/m2 depending on the days after planting (DAP) and the time of measurement for each day. The results indicate that the workflow introduced here is able to provide estimates of instantaneous latent heat flux (evapotranspiration) measurements for row crops in agricultural fields which will enable people to make reliable decisions related to irrigation scheduling.

54 ENVIRONMENTAL SCIENCES↗

NASA NTRS2001

Integrating Safety in the Aviation System: Interdepartmental Training for Pilots and Maintenance Technicians

The study of human factors has had a decisive impact on the aviation industry. However, the entire aviation system often is not considered in researching, training, and evaluating human factors issues especially with regard to safety. In both conceptual and practical terms, we argue for the proactive management of human error from both an individual and organizational systems perspective. The results of a multidisciplinary research project incorporating survey data from professional pilots and maintenance technicians and an exploratory study integrating students from relevant disciplines are reported. Survey findings suggest that latent safety errors may occur during the maintenance discrepancy reporting process because pilots and maintenance technicians do not effectively interact with one another. The importance of interdepartmental or cross-disciplinary training for decreasing these errors and increasing safety is discussed as a primary implication.

Mattson, Marifran↗

NASA NTRS1982

Care 3 phase 2 report, maintenance manual

CARE 3 (Computer-Aided Reliability Estimation, version three) is a computer program designed to help estimate the reliability of complex, redundant systems. Although the program can model a wide variety of redundant structures, it was developed specifically for fault-tolerant avionics systems--systems distinguished by the need for extremely reliable performance since a system failure could well result in the loss of human life. It substantially generalizes the class of redundant configurations that could be accommodated, and includes a coverage model to determine the various coverage probabilities as a function of the applicable fault recovery mechanisms (detection delay, diagnostic scheduling interval, isolation and recovery delay, etc.). CARE 3 further generalizes the class of system structures that can be modeled and greatly expands the coverage model to take into account such effects as intermittent and transient faults, latent faults, error propagation, etc.

Bryant, L. A.↗

NASA NTRS1982

The CARE 3 Phase 3 Report: Test and Evaluation

CARE 3 (Computer-Aided Reliability Estimation, version three) is a computer program designed to help estimate the reliability of complex, redundant systems; although the program can model a wide variety of redundant structures, it was developed specifically for fault-tolerant avionics systems, systems distinguished by the need for extremely reliable performance since a system failure could well result in the loss of human life. CARE 3 further generalizes the class of system structures that can be modeled and greatly expands the coverage model to take into account such effects as intermittent and transient faults, latent faults, error propagation, etc. The initial test and evaluation of CARE 3 are reported.

Stiffler, J. J.↗

NASA NTRS1985

SSME digital control design characteristics

To protect against a latent programming error (software fault) existing in an untried branch combination that would render the space shuttle out of control in a critical flight phase, the Backup Flight System (BFS) was chartered to provide a safety alternative. The BFS is designed to operate in critical flight phases (ascent and descent) by monitoring the activities of the space shuttle flight subsystems that are under control of the primary flight software (PFS) (e.g., navigation, crew interface, propulsion), then, upon manual command by the flightcrew, to assume control of the space shuttle and deliver it to a noncritical flight condition (safe orbit or touchdown). The problems associated with the selection of the PFS/BFS system architecture, the internal BFS architecture, the fault tolerant software mechanisms, and the long term BFS utility are discussed.

Mitchell, W. T.↗

NASA NTRS1989

Transient fault behavior in a microprocessor: A case study

An experimental analysis is described which studies the susceptibility of a microprocessor based jet engine controller to upsets caused by current and voltage transients. A design automation environment which allows the run time injection of transients and the tracing from their impact device to the pin level is described. The resulting error data are categorized by the charge levels of the injected transients by location and by their potential to cause logic upsets, latched errors, and pin errors. The results show a 3 picoCouloumb threshold, below which the transients have little impact. An Arithmetic and Logic Unit transient is most likely to result in logic upsets and pin errors (i.e., impact the external environment). The transients in the countdown unit are potentially serious since they can result in latched errors, thus causing latent faults. Suggestions to protect the processor against these errors, by incorporating internal error detection and transient suppression techniques, are also made.

Duba, Patrick↗

DOE OSTI2016

Investigation of a “Sharps” Incident

Special nuclear material research, process development, technology demonstration, and manufacturing capabilities are provided at the Los Alamos National Laboratory Plutonium Facility. Engineered barriers provide the most effective protection from radioactive and hazardous materials. The Worker Safety Security Team augments these passive safety feature by investigating incidents to identify appropriate prevention and mitigation measures. “Learning Teams” facilitate employee feedback loop and integration toward process improvement. Here, this article reports an investigation of a “Sharps” incident and reviews a case study of a technician that cuts his left thumb while making a gasket. Causal analysis of the sharps incident uncovered contributing factors that created the environment in which the incident occurred. Finally, latent organizational conditions that created error-likely situations or weakened defenses were identified and controlled. Effective improvements that reduce the probability or consequence of similar sharps incidents were implemented.

61 RADIATION PROTECTION AND DOSIMETRY↗