SEARCH · Engineering Papers

Results for “software testing”

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 1,513 records · Page 84

All sources NASA NTRS DOE OSTI

NASA NTRS1975

Automatic documentation system extension to multi-manufacturers' computers and to measure, improve, and predict software reliability

The DOMONIC system has been modified to run on the Univac 1108 and the CDC 6600 as well as the IBM 370 computer system. The DOMONIC monitor system has been implemented to gather data which can be used to optimize the DOMONIC system and to predict the reliability of software developed using DOMONIC. The areas of quality metrics, error characterization, program complexity, program testing, validation and verification are analyzed. A software reliability model for estimating program completion levels and one on which to base system acceptance have been developed. The DAVE system which performs flow analysis and error detection has been converted from the University of Colorado CDC 6400/6600 computer to the IBM 360/370 computer system for use with the DOMONIC system.

Simmons, D. B.↗

NASA NTRS1991

Tethered satellite system dynamics and control review panel and related activities, phase 3

Two major tests of the Tethered Satellite System (TSS) engineering and flight units were conducted to demonstrate the functionality of the hardware and software. Deficiencies in the hardware/software integration tests (HSIT) led to a recommendation for more testing to be performed. Selected problem areas of tether dynamics were analyzed, including verification of the severity of skip rope oscillations, verification or comparison runs to explore dynamic phenomena observed in other simulations, and data generation runs to explore the performance of the time domain and frequency domain skip rope observers.

Source record↗

NASA NTRS2002

Software for Improved Extraction of Data From Tape Storage

A computer program has been written to replace the original software of Racal Storeplex Delta tape recorders, which are still used at Stennis Space Center but have been discontinued by the manufacturer. Whereas the original software could be activated by a command-line interface only, the present software offers the option of a command-line or graphical user interface. The present software also offers the option of batch-file operation (activation by a file that contains command lines for operations performed consecutively). The present software is also more reliable than was the original software: The original software was plagued by several deficiencies that made it difficult to execute, modify, and test. In addition, when using the original software to extract data that had been recorded within specified intervals of time, the resolution with which one could control starting and stopping times was no finer than about a second (or, in some cases, several seconds). In contrast, the present software is capable of controlling playback times to within 1/100 second of times specified by the user, assuming that the tape-recorder clock is accurate to within 1/100 second.

Cheng, Chiu-Fu↗

NASA NTRS2002

Software Safety Assurance of Programmable Logic

Programmable Logic (PLC, FPGA, ASIC) devices are hybrids - hardware devices that are designed and programmed like software. As such, they fall in an assurance gray area. Programmable Logic is usually tested and verified as hardware, and the software aspects are ignored, potentially leading to safety or mission success concerns. The objective of this proposal is to first determine where and how Programmable Logic (PL) is used within NASA and document the current methods of assurance. Once that is known, raise awareness of the PL software aspects within the NASA engineering community and provide guidance for the use and assurance of PL form a software perspective.

Berens, Kalynnda↗

NASA NTRS2002

Software for Improved Extraction of Data From Tape Storage

Cheng, Chiu-Fu↗

NASA NTRS2003

Software for Improved Extraction of Data From Tape Storage

A computer program has been written to replace the original software of Racal Storeplex Delta tape recorders, which are used at Stennis Space Center. The original software could be activated by a command- line interface only; the present software offers the option of a command-line or graphical user interface. The present software also offers the option of batch-file operation (activation by a file that contains command lines for operations performed consecutively). The present software is also more reliable than was the original software: The original software was plagued by several deficiencies that made it difficult to execute, modify, and test. In addition, when using the original software to extract data that had been recorded within specified intervals of time, the resolution with which one could control starting and stopping times was no finer than about a second (or, in some cases, several seconds). In contrast, the present software is capable of controlling playback times to within 1/100 second of times specified by the user, assuming that the tape-recorder clock is accurate to within 1/100 second.

Cheng, Chiu-Fu↗

NASA NTRS2024

Integration of Automated Systems Test Campaign NC-IAS

NASA’s 2022 strategic plan included the goal to catalyze economic growth and drive innovation in the aviation industry, and to address challenges in air transportation and airspace management within the National Airspace System (NAS). The Aeronautics Research Mission Directorate (ARMD) specifically was tasked with leading aviation innovation to enable safe and sustainable air transportation through revolutionary vehicle advances and efficient flight operations. As a part of meeting these objectives and advancing air mobility concepts, NASA initiated the National Campaign (NC) in the Advanced Air Mobility (AAM) Project within the Airspace Operations and Safety Program (AOSP). The NC was designed to support operational demonstrations with industry as well as the research and development needed to support NASA-led research flight demonstrations. Within NC, the Integration of Automated Systems (IAS), an NC activity, tested and evaluated flight deck automation and airspace operations management functions needed to enable Urban Air Mobility (UAM) operations. This was accomplished through a partnership with Sikorsky Aircraft (specifically Sikorsky Innovations), a Lockheed Martin company, and DARPA (Defense Advanced Research Projects Agency), by leveraging two automation-enabled helicopters equipped with unique capabilities that enabled NASA to develop and test two-ship conflict encounters to demonstrate flight path management and hazard avoidance technologies. The enabler in this testing was NASA-developed “Middleware” (MW) software (also known as Expandable Variable Autonomy Architecture, or EVAA), which among other things allowed multiple algorithms to be incorporated into one software build that was hosted on the dissimilar-type Sikorsky helicopters. The IAS test campaign period of performance was from March 2022 through October 2023 and was structured as a phased, or spiral, approach that ultimately led to the first-ever demonstration of two-ship UAM/AAM operations designed to safely choreograph specific conflict encounters and mission scenarios to test the research algorithms for strategic and tactical aircraft deconfliction. Lessons learned are included in the body of the report. Data collected will be used to inform FAA and industry standards groups on the increasingly automated systems needed for future AAM operations. The test encounters developed for these flight tests were proven to be highly predictable, repeatable, and safely exercised flight path planning and Detect and Avoid (DAA) algorithms. These same test encounters should be leveraged by future flight test campaigns to verify that operational safety is not compromised as the AAM architecture matures. Next steps include repeating similar encounters using unmanned aircraft carrying DAA sensors in the National Airspace.

AAM↗

NASA NTRSDate not supplied

Flight Software for the LOFTID Re-Entry Vehicle

NASA’s Low-Earth Orbit Flight Test of an Inflatable Decelerator, or LOFTID, demonstrated re-entry from low-Earth orbit of a 6-meter aeroshell designed to be used as a heat shield that is larger than the rocket shroud, enabling the return of much greater mass. The LOFTID Flight Software was developed in-house and consists of three components: the Power Distribution software, the Data Recorder software, and the Camera Controller software, along with the Ground Software used for testing, operations, data integrity, and data processing. This presentation will discuss issues found in developing the Power Distribution software in cFS on a non-Linux POSIX platform, designing an efficient architecture for recording of high bandwidth data, controlling over a dozen cameras in-flight, and creating the ground support tools to verify data integrity and support the post-processing of flight data.

Paul Brewster↗

NASA NTRS2010

Configuring the Orion Guidance, Navigation, and Control Flight Software for Automated Sequencing

The Orion Crew Exploration Vehicle is being designed with greater automation capabilities than any other crewed spacecraft in NASA s history. The Guidance, Navigation, and Control (GN&C) flight software architecture is designed to provide a flexible and evolvable framework that accommodates increasing levels of automation over time. Within the GN&C flight software, a data-driven approach is used to configure software. This approach allows data reconfiguration and updates to automated sequences without requiring recompilation of the software. Because of the great dependency of the automation and the flight software on the configuration data, the data management is a vital component of the processes for software certification, mission design, and flight operations. To enable the automated sequencing and data configuration of the GN&C subsystem on Orion, a desktop database configuration tool has been developed. The database tool allows the specification of the GN&C activity sequences, the automated transitions in the software, and the corresponding parameter reconfigurations. These aspects of the GN&C automation on Orion are all coordinated via data management, and the database tool provides the ability to test the automation capabilities during the development of the GN&C software. In addition to providing the infrastructure to manage the GN&C automation, the database tool has been designed with capabilities to import and export artifacts for simulation analysis and documentation purposes. Furthermore, the database configuration tool, currently used to manage simulation data, is envisioned to evolve into a mission planning tool for generating and testing GN&C software sequences and configurations. A key enabler of the GN&C automation design, the database tool allows both the creation and maintenance of the data artifacts, as well as serving the critical role of helping to manage, visualize, and understand the data-driven parameters both during software development and throughout the life of the Orion project.

Odegard, Ryan G.↗

NASA NTRS1992

Estimation and enhancement of real-time software reliability through mutation analysis

A simulation-based technique for obtaining numerical estimates of the reliability of N-version, real-time software is presented. An extended stochastic Petri net is employed to represent the synchronization structure of N versions of the software, where dependencies among versions are modeled through correlated sampling of module execution times. Test results utilizing specifications for NASA's planetary lander control software indicate that mutation-based testing could hold greater potential for enhancing reliability than the desirable but perhaps unachievable goal of independence among N versions.

Geist, Robert↗

NASA NTRSDate not supplied

Supporting Exploration Missions by Enabling Exploration Mission System Software

Future exploration missions will consist of a multitude of data sources, systems, and operators collaborating to complete mission objectives. Presently, NASA is instantiating the contractual mechanisms, such as the Exploration Extravehicular Activity Services (xEVAS) and Human Landing System (HLS) contracts, to produce these mission assets. Architectural planning is also underway to establish the networking protocols and infrastructure to digitally create and connect mission elements, such as LunaNET. However, without new horizontally integrated data systems, these advancements will be limited in their ability to get mission data appropriately integrated into the plan, train, fly, explore workflow of the flight operations workforce. Here we describe several mission system software development efforts underway that are designed to support human spaceflight missions. This paper describes the current iterations of a suite of tools to support EVA procedure authoring and execution, and mission context creation for both International Space Station (ISS) and Artemis missions. These tools have been developed iteratively and continue to be used in present-day ISS operations on orbit and in several NASA facilities such as the Neutral Buoyancy Lab (NBL) and Artemis field testing. These solutions demonstrate how software development can be aligned with ongoing operations development activities to discover the features that best support both current and future human spaceflight missions.

Matthew J. Miller↗

NASA NTRSDate not supplied

Supporting Exploration Missions by Enabling Exploration Mission System Software

Matthew Miller↗

NASA NTRS2001

Architectures and Evaluation for Adjustable Control Autonomy for Space-Based Life Support Systems

In the past five years, a number of automation applications for control of crew life support systems have been developed and evaluated in the Adjustable Autonomy Testbed at NASA's Johnson Space Center. This paper surveys progress on an adjustable autonomous control architecture for situations where software and human operators work together to manage anomalies and other system problems. When problems occur, the level of control autonomy can be adjusted, so that operators and software agents can work together on diagnosis and recovery. In 1997 adjustable autonomy software was developed to manage gas transfer and storage in a closed life support test. Four crewmembers lived and worked in a chamber for 91 days, with both air and water recycling. CO2 was converted to O2 by gas processing systems and wheat crops. With the automation software, significantly fewer hours were spent monitoring operations. System-level validation testing of the software by interactive hybrid simulation revealed problems both in software requirements and implementation. Since that time, we have been developing multi-agent approaches for automation software and human operators, to cooperatively control systems and manage problems. Each new capability has been tested and demonstrated in realistic dynamic anomaly scenarios, using the hybrid simulation tool.

Malin, Jane T.↗

DOE OSTI2021

Predicting Deformation of Parts from HP Printers due to Sintering with Modeling and Simulation (CRADA NFE-18-07363)

This work proposes to leverage Oak Ridge National Laboratory’s (ORNL) sintering simulation software developed at the Manufacturing Demonstration Facility to 1) investigate the deformation of sintered parts and 2) to develop fast surrogate-based optimization methods for HP Inc. This includes the development of ORNL’s software on HP systems, integration and testing with HP part geometries and material properties, the development of surrogate models based on the results of the simulation, and modifications to the software based on feedback from HP. The expected impacts of this work are a drastic reduction in print costs, an increase in printer throughput, and the identification of novel, possibly exotic materials for 3D printing. This work will also decrease the time to market for HP’s print technology by decreasing the amount of resources and type dedicated to physical testing.

42 ENGINEERING↗

DOE OSTI2020

Simulation of DWPF Chemical Process Cell Using a Reaction Calorimeter

The Defense Waste Processing Facility (DWPF) converts liquid radioactive waste into glass using a Sludge Receipt Adjustment Tank (SRAT) and Slurry Mix Evaporator (SME) in addition to other processes. The SRAT and SME processes can be simulated on a small-scale using the Mettler-Toledo Reaction Calorimeter (RC1). This equipment is able to automate the execution and monitoring of experiments involving nonradioactive chemical simulants. During the chemical processing of sludge in the SRAT process, foam begins to form and can foam over the reaction vessel. The current antifoam used at DWPF creates a risk of increased flammability and has a limited pH range. Usually, mercury is circulated back into the reaction vessel during the SRAT process, making it difficult to remove. To combat foam over, novel antifoams will be tested during the boil-up process using the RC1. To improve mercury extraction, 3D-printed coalescer columns will be tested within the Mercury Water Wash Tank (MWWT) of the RC1. Testing of Simulant Sludge Batch 6 (SB6) was performed to ensure: the sludge would form a stable foam at boiling during full SRAT/SME runs; the antifoam would reduce the amount of foam within the vessel The sludge and a Precipitate Reactor Feed Tank (PRFT) simulant with monosodium titanate (MST) were mixed separately, combined, and then heated to boiling. As shown below, the antifoam used was able to eliminate the foam within the vessel, as expected. The FormLabs Form2 3D Printer can be used to create roughly 3-inch tall and 1-inch diameter columns from clear and ceramic resins. The columns will utilize chemical and physical forces to draw the mercury out of a condensed offgas stream leaving the RC1 reaction vessel. These columns will be tested during full SRAT/SME runs on the basis of how well they are able to collect elemental mercury. In preparation for full-scale runs, the RC1 equipment was assembled onto a custom table and tested with water runs. The software used to control automation, iControl, has a user-friendly interface that allows the experiment to be altered as needed. An example of the data recorded during an experimental run is represented in Figure 1 below. Water runs were utilized as a way to prove if the RC1 system was functioning in the following areas: Boil-up rates, Chemical additions using pumps, Temperature readings, Balance readings, Probe readings, Offgas system, Agitation. Future Plans: Five novel antifoams will be tested during full SRAT/SME runs. The most effective antifoam will be utilized in DWPF's Chemical Process Cell. The design of the Mercury Extraction Coalescer can be further manipulated to increase the extraction of not only elemental mercury, but other heavy metals in environmental remediation processes as well.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

NASA NTRS1987

X-29A flight control system performance during flight test

An account is given of flight control system performance results for the X-29A forward-swept wing 'Advanced Technology Demonstrator' fighter aircraft, with attention to its software and hardware components' achievement of the requisite levels of system stability and desirable aircraft handling qualities. The Automatic Camber Control Logic is found to be well integrated with the stability loop of the aircraft. A number of flight test support software programs developed by NASA facilitated monitoring of the X-29A's stability in real time, and allowed the test team to clear the envelope with confidence.

Chin, J.↗

DOE OSTI2020

Data-driven Alignment of the Tracker for the Mu2e Experiment

An alignment of the Mu2e Tracker is investigated using the Mu2e Offline Software and Millepede-II. Simulated misalignments of Tracker planes were inserted between Monte-Carlo event generation and before reconstruction using randomly generated $(x,y,z)$-translations and rotations of the rigid-body planes in the detector model. Cosmic ray muons, with no magnetic field present in the Detector Solenoid, will follow a straight-line trajectory. A maximum-likelihood fit is used to reconstruct a track and determine its parameters. Tracks traversing at least four planes, with ten registered straw hits, and a maximum time residual of $20$ ns are selected to be used in an alignment sample. The cuts were chosen to discard tracks with low information content, such as those with high levels of multiple scattering or those with low numbers of measurements contributing to a single track fit. Millepede-II produces the resulting alignment constants according to a simultaneous least-squares fit of the alignment parameters and the track parameters for all input tracks. The improved alignment constants are used to repeat the process and recover an increased number of suitable tracks, further improving the estimate of the alignment constants in subsequent iterations. A performance study of the process was conducted on a misaligned Tracker in the case of translation-only, and translation plus rotational misalignments. In both cases, the correct alignment constants were recovered to within statistical error after three global fit iterations. Additionally, a continuous integration system was developed for the \texttt{Mu2e/Offline} GitHub repository, introducing a convenient automated testing process for all proposed changes (``pull requests"). The tests developed included a full build of the software, followed by tests of the validation routines, geometry overlap checking, and multi-threading mode. Additionally, code quality checks and low-statistics physics comparison checks a re also available.

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗

NASA NTRS1993

How well does voice interaction work in space?

The methods and results of an evaluation of the Voice Navigator software package are discussed. The first phase or ground phase of the study consisted of creating, or training, computer voice files of specific commands. This consisted of repeating each of six commands eight times. The files were then tested for recognition accuracy by the software aboard the microgravity aircraft. During the second phase, both voice training and testing were performed in microgravity. Inflight training was done due to problems encountered in phase one which were believed to be caused by ambient noise levels. Both quantitative and qualitative data were collected. Only one of the commands was found to offer consistently high recognition rates across subjects during the second phase.

Morris, Randy B.↗