SEARCH · Search NASA

Results for “software estimate”

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 307 records · Page 17

All sources NASA NTRS DOE OSTI

NASA NTRS1991

An experimental evaluation of software redundancy as a strategy for improving reliability

The strategy of using multiple versions of independently developed software as a means to tolerate residual software design faults is suggested by the success of hardware redundancy for tolerating hardware failires. Although, as generally accepted, the independence of hardware failures resulting from physical wearout can lead to substantial increases in reliability for redundant hardware structures, a similar conclusion is not immediate for software. The degree to which design faults are manifested as independent failures determines the effectiveness of redundancy as a method for improving software reliability. Interest in multi-version software centers on whether it provides an adequate measure of increased reliability to warrant its use in critical applications. The effectiveness of multi-version software is studied by comparing estimates of the failure probabilities of these systems with the failure probabilities of single versions. The estimates are obtained under a model of dependent failures and compared with the estimates obtained when failures are assumed to be independent. The experimental results are based on twenty versions of an aerospace application developed and certified by sixty programmers from four universities. Descriptions of the application, development and certifications processes, and operational evaluation are given together with an analysis of the twenty versions.

Eckhardt, Dave E.↗

NASA NTRS2006

DORIS Satellite Phase Center Determination and Consequences on the Derived Scale of the Terrestrial Reference Frame

This slide presentation reports on the analysis of several years of Delft Object-oriented Radar Interferometric Software (Doris) data undertaken to estimate daily determination of satellite antenna phase center corrections. This was done on a satellite by satellite basis. For each DORIS satellite, we considered long-term time series of such individual estimations, looking for possible biases, discontinuities, trends or annual signals. The analysis compared DORIS to GPS estimates for common satellites (Jason and TOPEX/Poseidon).

terrestrial reference frame scale↗

NASA NTRS2007

NASA Tech Briefs, October 2007

Topics covered include; Wirelessly Interrogated Position or Displacement Sensors; Ka-Band Radar Terminal Descent Sensor; Metal/Metal Oxide Differential Electrode pH Sensors; Improved Sensing Coils for SQUIDs; Inductive Linear-Position Sensor/Limit-Sensor Units; Hilbert-Curve Fractal Antenna With Radiation- Pattern Diversity; Single-Camera Panoramic-Imaging Systems; Interface Electronic Circuitry for an Electronic Tongue; Inexpensive Clock for Displaying Planetary or Sidereal Time; Efficient Switching Arrangement for (N + 1)/N Redundancy; Lightweight Reflectarray Antenna for 7.115 and 32 GHz; Opto-Electronic Oscillator Using Suppressed Phase Modulation; Alternative Controller for a Fiber-Optic Switch; Strong, Lightweight, Porous Materials; Nanowicks; Lightweight Thermal Protection System for Atmospheric Entry; Rapid and Quiet Drill; Hydrogen Peroxide Concentrator; MMIC Amplifiers for 90 to 130 GHz; Robot Would Climb Steep Terrain; Measuring Dynamic Transfer Functions of Cavitating Pumps; Advanced Resistive Exercise Device; Rapid Engineering of Three-Dimensional, Multicellular Tissues With Polymeric Scaffolds; Resonant Tunneling Spin Pump; Enhancing Spin Filters by Use of Bulk Inversion Asymmetry; Optical Magnetometer Incorporating Photonic Crystals; WGM-Resonator/Tapered-Waveguide White-Light Sensor Optics; Raman-Suppressing Coupling for Optical Parametric Oscillator; CO2-Reduction Primary Cell for Use on Venus; Cold Atom Source Containing Multiple Magneto- Optical Traps; POD Model Reconstruction for Gray-Box Fault Detection; System for Estimating Horizontal Velocity During Descent; Software Framework for Peer Data-Management Services; Autogen Version 2.0; Tracking-Data-Conversion Tool; NASA Enterprise Visual Analysis; Advanced Reference Counting Pointers for Better Performance; C Namelist Facility; and Efficient Mosaicking of Spitzer Space Telescope Images.

Source record↗

NASA NTRS2011

Autonomous Aerobraking: A Design, Development, and Feasibility Study

Aerobraking has been used four times to decrease the apoapsis of a spacecraft in a captured orbit around a planetary body with a significant atmosphere utilizing atmospheric drag to decelerate the spacecraft. While aerobraking requires minimum fuel, the long time required for aerobraking requires both a large operations staff, and large Deep Space Network resources. A study to automate aerobraking has been sponsored by the NASA Engineering and Safety Center to determine initial feasibility of equipping a spacecraft with the onboard capability for autonomous aerobraking, thus saving millions of dollars incurred by a large aerobraking operations workforce and continuous DSN coverage. This paper describes the need for autonomous aerobraking, the development of the Autonomous Aerobraking Development Software that includes an ephemeris estimator, an atmospheric density estimator, and maneuver calculation, and the plan forward for continuation of this study.

Prince, Jill L. H.↗

NASA NTRS2011

Implementation and Simulation Results using Autonomous Aerobraking Development Software

An Autonomous Aerobraking software system is currently under development with support from the NASA Engineering and Safety Center (NESC) that would move typically ground-based operations functions to onboard an aerobraking spacecraft, reducing mission risk and mission cost. The suite of software that will enable autonomous aerobraking is the Autonomous Aerobraking Development Software (AADS) and consists of an ephemeris model, onboard atmosphere estimator, temperature and loads prediction, and a maneuver calculation. The software calculates the maneuver time, magnitude and direction commands to maintain the spacecraft periapsis parameters within design structural load and/or thermal constraints. The AADS is currently tested in simulations at Mars, with plans to also evaluate feasibility and performance at Venus and Titan.

Maddock, Robert W.↗

NASA NTRS2000

Software Fault Tolerance: A Tutorial

Because of our present inability to produce error-free software, software fault tolerance is and will continue to be an important consideration in software systems. The root cause of software design errors is the complexity of the systems. Compounding the problems in building correct software is the difficulty in assessing the correctness of software for highly complex systems. After a brief overview of the software development processes, we note how hard-to-detect design faults are likely to be introduced during development and how software faults tend to be state-dependent and activated by particular input sequences. Although component reliability is an important quality measure for system level analysis, software reliability is hard to characterize and the use of post-verification reliability estimates remains a controversial issue. For some applications software safety is more important than reliability, and fault tolerance techniques used in those applications are aimed at preventing catastrophes. Single version software fault tolerance techniques discussed include system structuring and closure, atomic actions, inline fault detection, exception handling, and others. Multiversion techniques are based on the assumption that software built differently should fail differently and thus, if one of the redundant versions fails, it is expected that at least one of the other versions will provide an acceptable output. Recovery blocks, N-version programming, and other multiversion techniques are reviewed.

Torres-Pomales, Wilfredo↗

NASA NTRS1992

Object-oriented productivity metrics

Software productivity metrics are useful for sizing and costing proposed software and for measuring development productivity. Estimating and measuring source lines of code (SLOC) has proven to be a bad idea because it encourages writing more lines of code and using lower level languages. Function Point Analysis is an improved software metric system, but it is not compatible with newer rapid prototyping and object-oriented approaches to software development. A process is presented here for counting object-oriented effort points, based on a preliminary object-oriented analysis. It is proposed that this approach is compatible with object-oriented analysis, design, programming, and rapid prototyping. Statistics gathered on actual projects are presented to validate the approach.

Connell, John L.↗

NASA NTRS2021

An Innovative Approach to Modeling VIPER Rover Software Life Cycle Cost

NASA’s “Volatiles Investigating Polar Exploration Rover” (VIPER) will be the first robotic mission to prospect for water ice near the south pole of the Moon in late 2023 on a 100-Earth-day mission. The information that the VIPER rover provides will help improve understanding of the composition, distribution, and accessibility of Lunar polar volatiles and will help determine how the Moon’s resources can support future human space exploration. VIPER, however, represents a radical departure from the way that NASA has traditionally developed planetary robotic missions. A key consequence of these differences is that estimating the cost of VIPER’s rover software is challenging and complex.For example, VIPER is being developed using management procedures typically applied to NASA research and technology projects, rather than space flight programs. In addition, key portions of the rover’s software are being designed as ground software to run on mission control computers (rather than on-board the rover as flight software as with prior planetary missions) taking advantage of continuous, interactive data communications between the Moon and Earth and higher performance computing available on the ground. Moreover, the rover’s software is being engineered using Agile software development practices and incorporates a significant amount of open-source, rather than following traditional (spiral, waterfall, etc.) development methods and in-house code. In this paper, we present an innovative process to estimate the life cycle cost of VIPER’s rover software. We first describe how we modeled the architecture and code counts for three software elements: Rover Flight Software (RFSW), Rover Ground Software (RGSW), and Rover Simulation Software (RSIM). We then discuss key challenges and unique aspects of our approach, such as the lack of Lunar rover analogies, the need to integrate and test large open source software, and the strategies developed to account for use of non-space flight management practices and the impact of the COVID-19 pandemic. We conclude with a summary of our results, including cumulative distribution, nearest neighbors and cluster analysis, as well as heuristics used to confirm the reasonableness of the cost estimate.

Utz, Hans↗

NASA NTRS1984

Yaw Attitude Estimation for the Tracking and Data Relay Satellite System

The Tracking and Data Relay Satellite System (TDRSS) uses a groundbased attitude determination algorithm to open loop point the satellite's high data rate antennas. The spacecraft is able to measure its pitch and roll attitude, but its yaw attitude is periodically unobservable. The ground software uses a state-space estimator, an adaptation of a Luenberger observer, to predict the spacecraft yaw angle during these unobservable periods. It contains states associated with the roll/yaw dynamics and the on-board control law. The accuracy is limited by the modeling fidelity of the disturbance torques acting on the spacecraft. After initial operating problems were cleared up, the operation of the estimator has converged to predicted performance.

Staich, S.↗

NASA NTRS1986

A study of fault prediction and reliability assessment in the SEL environment

An empirical study on estimation and prediction of faults, prediction of fault detection and correction effort, and reliability assessment in the Software Engineering Laboratory environment (SEL) is presented. Fault estimation using empirical relationships and fault prediction using curve fitting method are investigated. Relationships between debugging efforts (fault detection and correction effort) in different test phases are provided, in order to make an early estimate of future debugging effort. This study concludes with the fault analysis, application of a reliability model, and analysis of a normalized metric for reliability assessment and reliability monitoring during development of software.

Basili, Victor R.↗

NASA NTRS1998

Software Evolution and the Fault Process

In developing a software system, we would like to estimate the way in which the fault content changes during its development, as well determine the locations having the highest concentration of faults.

software↗

NASA NTRS2024

Smallsat 2024 - Starling Cubesat Swarm Technology Demonstration Flight Results

The Starling swarm of four 6U CubeSats launched in July 2023 to test four key technologies to enable future swarm missions: 1) Mobile Ad-Hoc Networking (MANET) over a crosslink radio network 2) Autonomous onboard decision-making for operations 3) Optical-based absolute and relative navigation 4) Autonomous maneuver planning and execution The Starling team implemented the Better Approach to Mobile Ad-hoc Networking (B.A.T.M.A.N.) protocol to automatically manage the crosslink network of four satellites. The B.A.T.M.A.N. protocol uses a decentralized approach to managing a multi-hop mesh network of devices, in this case, a satellite swarm. The four satellites were able to successfully establish a network at multiple data rates and demonstrate file transfer and command issuance between spacecraft over the network. Starling incorporated Distributed Spacecraft Autonomy's (DSA) software to demonstrate onboard decision-making. The DSA software takes L1/L2 band GPS measurements and uses them to estimate the relative Total Electron Count (TEC) in the ionosphere. The onboard software then determines if there are any features of interest and provides that information to the other satellites over the crosslink network. The swarm of satellites then reaches a consensus on the optimal TEC observation strategy and adjusts its measurement collection tactics autonomously. The Starling Formation-Flying Optical Experiment (StarFOX), produced by Stanford's Space Rendezvous Laboratory, uses the onboard star trackers to collect images of the other swarm spacecraft and produce angles-only navigation estimates. This system is envisioned to be valuable in applications in which Global Navigation Satellite Systems (GNSS) are not available, such as in cis-lunar or deep space. StarFOX successfully applied its algorithms to multiple simultaneous spacecraft targets using the star tracker imagery. Finally, Starling used Emergent Space's Cluster Flight Application (CFA) software suite for the Reconfiguration and Orbit Maintenance Experiments Onboard (ROMEO) demonstration of autonomously planning and executing propulsive maneuvers. Large swarms will need to be able to maintain formation requirements with minimal operator involvement, especially as the size of the swarm scales up. Results from the ROMEO experiment are presented. Starling is funded by the Small Spacecraft Technology (SST) program out of NASA's Space Technology Mission Directorate (STMD).

distributed systems↗

NASA NTRS2017

The Flight Optimization System Weights Estimation Method

FLOPS has been the primary aircraft synthesis software used by the Aeronautics Systems Analysis Branch at NASA Langley Research Center. It was created for rapid conceptual aircraft design and advanced technology impact assessments. FLOPS is a single computer program that includes weights estimation, aerodynamics estimation, engine cycle analysis, propulsion data scaling and interpolation, detailed mission performance analysis, takeoff and landing performance analysis, noise footprint estimation, and cost analysis. It is well known as a baseline and common denominator for aircraft design studies. FLOPS is capable of calibrating a model to known aircraft data, making it useful for new aircraft and modifications to existing aircraft. The weight estimation method in FLOPS is known to be of high fidelity for conventional tube with wing aircraft and a substantial amount of effort went into its development. This report serves as a comprehensive documentation of the FLOPS weight estimation method. The development process is presented with the weight estimation process.

Wells, Douglas P.↗

NASA NTRS2007

Single-Frequency GPS Relative Navigation in a High Ionosphere Orbital Environment

The Global Positioning System (GPS) provides a convenient source for space vehicle relative navigation measurements, especially for low Earth orbit formation flying and autonomous rendezvous mission concepts. For single-frequency GPS receivers, ionospheric path delay can be a significant error source if not properly mitigated. In particular, ionospheric effects are known to cause significant radial position error bias and add dramatically to relative state estimation error if the onboard navigation software does not force the use of measurements from common or shared GPS space vehicles. Results from GPS navigation simulations are presented for a pair of space vehicles flying in formation and using GPS pseudorange measurements to perform absolute and relative orbit determination. With careful measurement selection techniques relative state estimation accuracy to less than 20 cm with standard GPS pseudorange processing and less than 10 cm with single-differenced pseudorange processing is shown.

Conrad, Patrick R.↗

DOE OSTI2025

SITCOMTN-154: Initial studies of photometric redshifts with LSSTComCam from DP1

This technote holds reports based on the first analyses of the Data Preview 1 (DP1) data by the Science Unit for photometric redshifts. Although photometric redshifts are not an official DP1 data product, the "Photo-z Science Unit" generated photo-z estimates for every galaxy in DP1 using the available multi-band imaging on a best-effort basis. This work included developing training and test datasets by matching DP1 data to high-quality reference redshifts obtained with spectroscopy, Grism data, and multi-band photometry. The Science Unit used the RAIL software package to make photometric redshift estimates using eight different algorithms, developed simple scientific performance metrics, used those metrics to explore how the performance of the algorithms varied with configuration changes, derived more optimized configurations of the algorithms and tested the performance of those configurations. This work, the resulting data products and expected data distribution mechanism are all described there.

79 ASTRONOMY AND ASTROPHYSICS↗

NASA NTRS1976

Earth-moon system: Dynamics and parameter estimation; numerical considerations and program documentation

Major activities included coding and verifying equations of motion for the earth-moon system. Some attention was also given to numerical integration methods and parameter estimation methods. Existing analytical theories such as Brown's lunar theory, Eckhardt's theory for lunar rotation, and Newcomb's theory for the rotation of the earth were coded and verified. These theories serve as checks for the numerical integration. Laser ranging data for the period January 1969 - December 1975 was collected and stored on tape. The main goal of this research is the development of software to enable physical parameters of the earth-moon system to be estimated making use of data available from the Lunar Laser Ranging Experiment and the Very Long Base Interferometry experiment of project Apollo. A more specific goal is to develop software for the estimation of certain physical parameters of the moon such as inertia ratios, and the third and fourth harmonic gravity coefficients.

Breedlove, W. J., Jr.↗

NASA NTRS1999

A Methodology for the Measurement of Test Effectiveness

In developing a software system, we would like to estimate the total number of faults inserted in to the system, its residual fault content at any given time, and the efficacy of the testing activity in executing the code containing the newly inserted faults.

software reliability software faults software faul↗

NASA NTRSDate not supplied

Sleep, Sleepiness, and Performance Across Three In-Flight Bunk Rest Opportunities

Introduction: Airline pilots are required to take a rest break in a bunk during long-haul flights in an effort to reduce sleepiness during critical phases of flight. It is unclear, however, whether each rest break affords equal opportunity for sleep. We aimed to characterize sleep, sleepiness, and performance outcomes across three in-flight rest breaks during long-haul flights. Methods: Thirty-seven pilots wore actiwatches and completed sleep diaries for approximately two weeks while flying a variety of long-haul routes (n=126 flights). Self-reported in-flight bunk rest (BR) periods were used to set rest intervals and sleep was estimated within these intervals using actigraphy software (wake threshold set to medium). Pilots provided Karolinska Sleepiness Scale ratings (KSS) and performed a 5-minute psychomotor vigilance task (PVT) before landing. A linear mixed-effects model with participant included as a random effect and allowed to vary by intercept was used to assess differences between BR opportunities. Results : The majority (97%, n=122) of bunk rest periods contained sleep (as estimated by actigraphy). The mean (+/- standard deviation) sleep duration for the first, middle, and third BR opportunity was 152.8 (69.7), 149.2 (44.1), 125.2 (44.9) minutes, respectively. There was a significant effect of BR opportunity for sleep duration (F2,54 = 3.747, p=.03) and KSS (F2,44 = 7.869, p=.001). Bonferroni adjusted planned pairwise contrasts revealed that pilots using the third BR obtained significantly less sleep than in the first BR (p=.029). KSS ratings prior to landing were higher for the third BR compared to both the first (p=.001) and middle BR (p=.017). There were no significant differences for PVT speed or lapses (all p>05). Conclusion: These results suggest that the last rest break is associated with shorter sleep, lower alertness, and no differences in performance relative to the other rest breaks. Further analysis is required to determine whether the higher KSS ratings following the third rest break are associated with sleep inertia, or whether other factors may be involved.

sleepiness↗