SEARCH · Search NASA

Results for “Software errors”

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 721 records · Page 40

All sources NASA NTRS DOE OSTI

NASA NTRS1991

On the use and the performance of software reliability growth models

We address the problem of predicting future failures for a piece of software. The number of failures occurring during a finite future time interval is predicted from the number failures observed during an initial period of usage by using software reliability growth models. Two different methods for using the models are considered: straightforward use of individual models, and dynamic selection among models based on goodness-of-fit and quality-of-prediction criteria. Performance is judged by the relative error of the predicted number of failures over future finite time intervals relative to the number of failures eventually observed during the intervals. Six of the former models and eight of the latter are evaluated, based on their performance on twenty data sets. Many open questions remain regarding the use and the performance of software reliability growth models.

Keiller, Peter A.↗

NASA NTRS2013

Analysis of a Split-Plot Experimental Design Applied to a Low-Speed Wind Tunnel Investigation

A procedure to analyze a split-plot experimental design featuring two input factors, two levels of randomization, and two error structures in a low-speed wind tunnel investigation of a small-scale model of a fighter airplane configuration is described in this report. Standard commercially-available statistical software was used to analyze the test results obtained in a randomization-restricted environment often encountered in wind tunnel testing. The input factors were differential horizontal stabilizer incidence and the angle of attack. The response variables were the aerodynamic coefficients of lift, drag, and pitching moment. Using split-plot terminology, the whole plot, or difficult-to-change, factor was the differential horizontal stabilizer incidence, and the subplot, or easy-to-change, factor was the angle of attack. The whole plot and subplot factors were both tested at three levels. Degrees of freedom for the whole plot error were provided by replication in the form of three blocks, or replicates, which were intended to simulate three consecutive days of wind tunnel facility operation. The analysis was conducted in three stages, which yielded the estimated mean squares, multiple regression function coefficients, and corresponding tests of significance for all individual terms at the whole plot and subplot levels for the three aerodynamic response variables. The estimated regression functions included main effects and two-factor interaction for the lift coefficient, main effects, two-factor interaction, and quadratic effects for the drag coefficient, and only main effects for the pitching moment coefficient.

Erickson, Gary E.↗

DOE OSTI2025

Commercialization of a Non-Intrusive Optical (NIO) Technology to Measure Heliostat Optical Errors in Utility-Scale Concentrating Solar Power Plants: Final TCF Report

The drone-based Non-Intrusive Optical (NIO) Technology has been developed at NREL to allow for efficient and automated optical characterization of heliostats in Concentrating Solar Power (CSP) plants. For this project, the technology will be developed into a commercial tool package, including software and user-interface (UI), operations manual, and training and support services. The project team will partner with Tietronix to perform market assessment and stakeholder engagement, develop the tool package and business model, and perform data collection and analysis to demonstrate and refine the capabilities for use at a commercial plant. The team will collaborate with a commercial plant to conduct the data collection operations and provide optical error deliverables. The goal of the project is to advance the commercialization of the technology to a stage where a beta version can be demonstrated at additional commercial plants and developed into a licensable product.

14 SOLAR ENERGY↗

NASA NTRS2004

Mars Exploration Rovers navigation results

The twin Mars Exploration Rovers, Spirit and Opportunity, were launched on June 10, 2003(dagger), and July 8, 2003, from Cape Canaveral, Florida. Spirit and Opportunity were targeted for landings at Gusev Crater (arrival on January 4, 2004) and Meridiani Planum (arrival on January 25, 2004). The primary navigation challenge was to deliver each spacecraft to the desired atmospheric entry interface point with sufficient accuracy such that each lander would touch down within a specified landing ellipse (about 70 km x 5 km) determined to be safe for landing and also judged to be scientifically interesting. In order to achieve landing within the target ellipse, precise control of the inertial entry flight path angle (FPA) at atmospheric entry was required. The maximum allowable errors in FPA following TCM-5 (trajectory correction maneuver #5) at Entry (E) - 2 days were +/-0.12(deg) (3(sigma)) for Spirit and +/-0.14(deg) (3(sigma)) for Opportunity. Achieving these entry delivery accuracies necessitated significant improvements to the interplanetary avigation system used for MER. These improvements included new processes and software for orbit determination, propulsive maneuver design, and entry, descent, and landing (EDL) trajectory simulation. The actual achieved atmospheric entry accuracies for Spirit and Opportunity significantly exceeded the requirements. At the navigation data cutoff for the TCM-5 final design, the orbit determination FPA knowledge error was +/-0.028(deg) (3(sigma) ) for Spirit and +/-0.035(deg) (3(sigma)) for Opportunity. Because of exceptionally accurate navigation performance, TCM-5 (E - 2 days) and TCM-6 (E - 4 hours) were canceled for both Spirit and Opportunity. The actual landing locations (determined from in-situ Doppler tracking between the MER rovers and the Mars Odyssey orbiter) differed from the target landing points by 10.1 km (downtrack) for Spirit and 24.6 km (downtrack) for Opportunity. The majority of the landing position offsets for both landers was primarily caused by variations in atmosphere and spacecraft aerodynamic modeling from what was predicted. The amount of the landing position offset caused by navigation-only errors was only 3.3 km (uptrack) for Spirit and 9.7 km (downtrack) for Opportunity.

Mars Exploration Rover (MER)↗

NASA NTRS2004

Mars Exploration Rovers navigation results

The twin Mars Exploration Rovers, Spirit and Opportunity, were launched on June 10, 2003, and July 8, 2003, from Cape Canaveral, Florida. Spirit and Opportunity were targeted for landings at Gusev Crater (arrival on January 4, 2004) and Meridiani Planum (arrival on January 25, 2004). The primary navigation challenge was to deliver each spacecraft to the desired atmospheric entry interface point with sufficient accuracy such that each lander would touch down within a specified landing ellipse (about 70 km x 5 km) determined to be safe for landing and also judged to be scientifically interesting. In order to achieve landing within the target ellipse, precise control of the inertial entry flight path angle (FPA) at atmospheric entry was required. The maximum allowable errors in FPA following TCM-5 (trajectory correction maneuver #5) at Entry (E) -2 days were +/-0.12 deg(3 sigma) for Spirit and +/-0.14 deg(3 sigma) for Opportunity. Achieving these entry delivery accuracies necessitated significant improvements to the interplanetary navigation system used for MER. These improvements included new processes and software for orbit determination, propulsive maneuver design, and entry, descent, and landing (EDL) trajectory simulation. The actual achieved atmospheric entry accuracies for Spirit and Opportunity significantly exceeded the requirements. At the navigation data cutoff for the TCM-5 final design, the orbit determination FPA knowledge error was 0.028 deg(3 sigma) for Spirit and 0.035 deg(3 sigma) for Opportunity. Because of exceptionally accurate navigation performance, TCM-5 (E - 2 days) and TCM-6 (E - 4 hours) were canceled for both Spirit and Opportunity. The actual landing locations (determined from in-situ Doppler tracking between the MER rovers and the Mars Odyssey orbiter) differed from the target landing points by 10.1 km (downtrack) for Spirit and 24.6 km (downtrack) for Opportunity. The majority of the landing position offsets for both landers was primarily caused by variations in atmosphere and spacecraft aerodynamic modeling from what was predicted. The amount of the landing position offset caused by navigation-only errors was only 3.3 km (uptrack) for Spirit and 9.7 km (downtrack) for Opportunity.

Mars Exploration Rover (MER)↗

NASA NTRS1984

A robust pseudo-inverse spectral filter applied to the Earth Radiation Budget Experiment (ERBE) scanning channels

Computer simulations of a least squares estimator operating on the ERBE scanning channels are discussed. The estimator is designed to minimize the errors produced by nonideal spectral response to spectrally varying and uncertain radiant input. The three ERBE scanning channels cover a shortwave band a longwave band and a ""total'' band from which the pseudo inverse spectral filter estimates the radiance components in the shortwave band and a longwave band. The radiance estimator draws on instantaneous field of view (IFOV) scene type information supplied by another algorithm of the ERBE software, and on a priori probabilistic models of the responses of the scanning channels to the IFOV scene types for given Sun scene spacecraft geometry. It is found that the pseudoinverse spectral filter is stable, tolerant of errors in scene identification and in channel response modeling, and, in the absence of such errors, yields minimum variance and essentially unbiased radiance estimates.

Avis, L. M.↗

NASA NTRS1975

Post-test navigation data analysis techniques for the shuttle ALT

Postflight test analysis data processing techniques for shuttle approach and landing tests (ALT) navigation data are defined. Postfight test processor requirements are described along with operational and design requirements, data input requirements, and software test requirements. The postflight test data processing is described based on the natural test sequence: quick-look analysis, postflight navigation processing, and error isolation processing. Emphasis is placed on the tradeoffs that must remain open and subject to analysis until final definition is achieved in the shuttle data processing system and the overall ALT plan. A development plan for the implementation of the ALT postflight test navigation data processing system is presented. Conclusions are presented.

Source record↗

NASA NTRS1979

Space Shuttle ascent guidance, navigation, and control

The factors leading to the particular design of the Shuttle guidance, navigation and control software are discussed. The derivation of explicit guidance equations satisfying a wide range of different maneuver constraints and steering equations that create attitude steering errors from the guidance solutions is presented, as are navigation equations, and equations for identifying faulty instruments from sets of redundant instrument measurements.

R. L. Mchenry↗

NASA NTRS1992

VOUS Software Facilitates Development Of Other Software

Visual Object Oriented Unification System (VOUS) computer program provides facility for development of other, high-level software. Does not replace, but rather extends, preexisting software tools for development of other software. Provides comprehensive, graphical, interactive medium for all phases in development of computer code from early exploration of concepts, through detailed coding-and-error-checking process, to final reporting of finished code and compilation of instruction manual for its use. Simplifies and partly automates programmer's task.

Oliger, Joseph↗

NASA NTRS1992

Estimating the probability of failure when testing reveals no failures

Formulas for estimating the probability of failure when testing reveals no errors are introduced. These formulas incorporate random testing results, information about the input distribution, and prior assumptions about the probability of failure of the software. The formulas are not restricted to equally likely input distributions, and the probability of failure estimate can be adjusted when assumptions about the input distribution change. The formulas are based on a discrete sample space statistical model of software and include Bayesian prior assumptions. Reusable software and software in life-critical applications are particularly appropriate candidates for this type of analysis.

Miller, Keith W.↗

NASA NTRS2009

Deductive Verification of Cryptographic Software

We report on the application of an off-the-shelf verification platform to the RC4 stream cipher cryptographic software implementation (as available in the openSSL library), and introduce a deductive verification technique based on self-composition for proving the absence of error propagation.

Almeida, Jose Barcelar↗

NASA NTRS2014

OMPS Limb Profiler Instrument Performance Assessment

Following the successful launch of the Ozone Mapping and Profiler Suite (OMPS) aboard the Suomi National Polar-orbiting Partnership (SNPP) spacecraft, the NASA OMPS Limb team began an evaluation of instrument and data product performance. The focus of this paper is the instrument performance in relation to the original design criteria. Performance that is closer to expectations increases the likelihood that limb scatter measurements by SNPP OMPS and successor instruments can form the basis for accurate long-term monitoring of ozone vertical profiles. The team finds that the Limb instrument operates mostly as designed and basic performance meets or exceeds the original design criteria. Internally scattered stray light and sensor pointing knowledge are two design challenges with the potential to seriously degrade performance. A thorough prelaunch characterization of stray light supports software corrections that are accurate to within 1% in radiances up to 60 km for the wavelengths used in deriving ozone. Residual stray light errors at 1000nm, which is useful in retrievals of stratospheric aerosols, currently exceed 10%. Height registration errors in the range of 1 km to 2 km have been observed that cannot be fully explained by known error sources. An unexpected thermal sensitivity of the sensor also causes wavelengths and pointing to shift each orbit in the northern hemisphere. Spectral shifts of as much as 0.5nm in the ultraviolet and 5 nm in the visible, and up to 0.3 km shifts in registered height, must be corrected in ground processing.

ozone↗

NASA NTRS2012

Irreducible Tests for Space Mission Sequencing Software

As missions extend further into space, the modeling and simulation of their every action and instruction becomes critical. The greater the distance between Earth and the spacecraft, the smaller the window for communication becomes. Therefore, through modeling and simulating the planned operations, the most efficient sequence of commands can be sent to the spacecraft. The Space Mission Sequencing Software is being developed as the next generation of sequencing software to ensure the most efficient communication to interplanetary and deep space mission spacecraft. Aside from efficiency, the software also checks to make sure that communication during a specified time is even possible, meaning that there is not a planet or moon preventing reception of a signal from Earth or that two opposing commands are being given simultaneously. In this way, the software not only models the proposed instructions to the spacecraft, but also validates the commands as well.To ensure that all spacecraft communications are sequenced properly, a timeline is used to structure the data. The created timelines are immutable and once data is as-signed to a timeline, it shall never be deleted nor renamed. This is to prevent the need for storing and filing the timelines for use by other programs. Several types of timelines can be created to accommodate different types of communications (activities, measurements, commands, states, events). Each of these timeline types requires specific parameters and all have options for additional parameters if needed. With so many combinations of parameters available, the robustness and stability of the software is a necessity. Therefore a baseline must be established to ensure the full functionality of the software and it is here where the irreducible tests come into use.

sequencing test↗

NASA NTRS2015

Generation of Simulated Tracking Data for LADEE Operational Readiness Testing

Operational Readiness Tests were an important part of the pre-launch preparation for the LADEE mission. The generation of simulated tracking data to stress the Flight Dynamics System and the Flight Dynamics Team was important for satisfying the testing goal of demonstrating that the software and the team were ready to fly the operational mission. The simulated tracking was generated in a manner to incorporate the effects of errors in the baseline dynamical model, errors in maneuver execution and phenomenology associated with various tracking system based components. The ability of the mission team to overcome these challenges in a realistic flight dynamics scenario indicated that the team and flight dynamics system were ready to fly the LADEE mission. Lunar Atmosphere and Dust Environment.

Tracking↗

NASA NTRS2016

A Multi-Center Space Data System Prototype Based on CCSDS Standards

Deep space missions beyond earth orbit will require new methods of data communications in order to compensate for increasing Radio Frequency (RF) propagation delay. The Consultative Committee for Space Data Systems (CCSDS) standard protocols Spacecraft Monitor & Control (SM&C), Asynchronous Message Service (AMS), and Delay/Disruption Tolerant Networking (DTN) provide such a method. However, the maturity level of this protocol stack is insufficient for mission inclusion at this time. This Space Data System prototype is intended to provide experience which will raise the Technical Readiness Level (TRL) of this protocol set. In order to reduce costs, future missions can take advantage of these standard protocols, which will result in increased interoperability between control centers. This prototype demonstrates these capabilities by implementing a realistic space data system in which telemetry is published to control center applications at the Jet Propulsion Lab (JPL), the Marshall Space Flight Center (MSFC), and the Johnson Space Center (JSC). Reverse publishing paths for commanding from each control center are also implemented. The target vehicle consists of realistic flight computer hardware running Core Flight Software (CFS) in the integrated Power, Avionics, and Power (iPAS) Pathfinder Lab at JSC. This prototype demonstrates a potential upgrade path for future Deep Space Network (DSN) modification, in which the automatic error recovery and communication gap compensation capabilities of DTN would be exploited. In addition, SM&C provides architectural flexibility by allowing new service providers and consumers to be added efficiently anywhere in the network using the common interface provided by SM&C's Message Abstraction Layer (MAL). In FY 2015, this space data system was enhanced by adding telerobotic operations capability provided by the Robot API Delegate (RAPID) family of protocols developed at NASA. RAPID is one of several candidates for consideration and inclusion in a new international standard being developed by the CCSDS Telerobotic Operations Working Group. Software gateways for the purpose of interfacing RAPID messages with the existing SM&C based infrastructure were developed. Telerobotic monitor, control, and bridge applications were written in the RAPID framework, which were then tailored to the NAO telerobotic test article hardware, a product of Aldebaran Robotics.

Rich, Thomas M.↗

NASA NTRS2012

A Change Impact Analysis to Characterize Evolving Program Behaviors

Change impact analysis techniques estimate the potential effects of changes made to software. Directed Incremental Symbolic Execution (DiSE) is an intraprocedural technique for characterizing the impact of software changes on program behaviors. DiSE first estimates the impact of the changes on the source code using program slicing techniques, and then uses the impact sets to guide symbolic execution to generate path conditions that characterize impacted program behaviors. DiSE, however, cannot reason about the flow of impact between methods and will fail to generate path conditions for certain impacted program behaviors. In this work, we present iDiSE, an extension to DiSE that performs an interprocedural analysis. iDiSE combines static and dynamic calling context information to efficiently generate impacted program behaviors across calling contexts. Information about impacted program behaviors is useful for testing, verification, and debugging of evolving programs. We present a case-study of our implementation of the iDiSE algorithm to demonstrate its efficiency at computing impacted program behaviors. Traditional notions of coverage are insufficient for characterizing the testing efforts used to validate evolving program behaviors because they do not take into account the impact of changes to the code. In this work we present novel definitions of impacted coverage metrics that are useful for evaluating the testing effort required to test evolving programs. We then describe how the notions of impacted coverage can be used to configure techniques such as DiSE and iDiSE in order to support regression testing related tasks. We also discuss how DiSE and iDiSE can be configured for debugging finding the root cause of errors introduced by changes made to the code. In our empirical evaluation we demonstrate that the configurations of DiSE and iDiSE can be used to support various software maintenance tasks

Rungta, Neha Shyam↗

NASA NTRS2007

Algorithm-Based Fault Tolerance for Numerical Subroutines

A software library implements a new methodology of detecting faults in numerical subroutines, thus enabling application programs that contain the subroutines to recover transparently from single-event upsets. The software library in question is fault-detecting middleware that is wrapped around the numericalsubroutines. Conventional serial versions (based on LAPACK and FFTW) and a parallel version (based on ScaLAPACK) exist. The source code of the application program that contains the numerical subroutines is not modified, and the middleware is transparent to the user. The methodology used is a type of algorithm- based fault tolerance (ABFT). In ABFT, a checksum is computed before a computation and compared with the checksum of the computational result; an error is declared if the difference between the checksums exceeds some threshold. Novel normalization methods are used in the checksum comparison to ensure correct fault detections independent of algorithm inputs. In tests of this software reported in the peer-reviewed literature, this library was shown to enable detection of 99.9 percent of significant faults while generating no false alarms.

Tumon, Michael↗

DOE OSTI2025

Verification of the REBUS Software

Ongoing design activities at Argonne National Laboratory are requiring a thorough verification of the Argonne Reactor Computation codes be performed. REBUS is central to this system. The driver for this effort requires the Triangular-Z and hexagonal-Z core geometry options of REBUS to be verified. Previous work identified the REBUS features required to be verified to support current design activities, features of which are generally applicable to hexagonal-Z fast reactor designs. The scope of this verification effort includes verifying REBUS’s ability to correctly intepret the user input model, verifying that the features identified yield the intended results, and verifying the correctness of the REBUS output tables. The REBUS software verification relies heavily upon the accuracy of the embedded DIF3D software, the verification of which was completed and documented elsewhere. Given that DIF3D produces an accurate solution, the primary focus of the verification in the REBUS software is to ensure that it properly uses the DIF3D solution and that the depletion system (Bateman equations) are correctly implemented. This manuscript reiterates the verification tasks and displays results with respect to the features needed for current design activities. Analytic solutions of the Batemen equations are displayed and the results calculated with REBUS are displayed demonstrating the accuracy. Since coupled Bateman and neutron diffusion/transport solutions are extremely difficult to obtain, much of the focus is placed on how REBUS uses a given DIF3D solution assuming the accuracy of the DIF3D solution. The verification effort identified no issues that are debilitating or otherwise impactful to the design usage of REBUS, and thus REBUS version 11.0, release 3012 is considered verified. It is important to note that several outputs of REBUS are identified to be inaccurate, such as burnup in MWD/MT. Most of the relevant ones for VTR are generally accurate with 10-20% errors which is not impactful as all regular REBUS users are aware of this issue and know how to hand calculate the results. The REBUS manual further makes it clear that these values are consistent with the methodology being used by REBUS and thus the “errors” are more of an inconsistent definition with respect to what a user would expect given a definition in literature. Other issues that were identified included unclear documentation and software bugs all of which were inconsequential to the final results.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗