Flight packaged onboard checkout systems development unit. Software documentation, overall specification, level 2 - Test Oriented Onboard Language system /TOOL/
Test Oriented Onboard Language /TOOL/ system for spacecraft checkout
Source record↗
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.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
Data reduction software for LORAN-C flight test evaluation
A set of programs designed to be run on an IBM 370/158 computer to read the recorded time differences from the tape produced by the LORAN data collection system, convert them to latitude/longitude and produce various plotting input files are described. The programs were written so they may be tailored easily to meet the demands of a particular data reduction job. The tape reader program is written in 370 assembler language and the remaining programs are written in standard IBM FORTRAN-IV language. The tape reader program is dependent upon the recording format used by the data collection system and on the I/O macros used at the computing facility. The other programs are generally device-independent, although the plotting routines are dependent upon the plotting method used. The data reduction programs convert the recorded data to a more readily usable form; convert the time difference (TD) numbers to latitude/longitude (lat/long), to format a printed listing of the TDs, lat/long, reference times, and other information derived from the data, and produce data files which may be used for subsequent plotting.
Fischer, J. P.↗
An analysis of the effects of coincident errors on multi-version software
The present study is concerned with the application of a model which provides a basis for analytical investigations of redundant software. The model links certain basic quantities with the experimental process of testing independently designed software components. The model is employed to provide insight into the effects of coincident errors on an N-version software structure in which the structure fails if at least a majority of its components fail. Attention is given to coincident errors, the intensity distribution for coincident errors, the coincident errors model, and a condition for redundancy to improve reliability.
Eckhardt, D. E., Jr.↗
An assessment of space shuttle flight software development processes
In early 1991, the National Aeronautics and Space Administration's (NASA's) Office of Space Flight commissioned the Aeronautics and Space Engineering Board (ASEB) of the National Research Council (NRC) to investigate the adequacy of the current process by which NASA develops and verifies changes and updates to the Space Shuttle flight software. The Committee for Review of Oversight Mechanisms for Space Shuttle Flight Software Processes was convened in Jan. 1992 to accomplish the following tasks: (1) review the entire flight software development process from the initial requirements definition phase to final implementation, including object code build and final machine loading; (2) review and critique NASA's independent verification and validation process and mechanisms, including NASA's established software development and testing standards; (3) determine the acceptability and adequacy of the complete flight software development process, including the embedded validation and verification processes through comparison with (1) generally accepted industry practices, and (2) generally accepted Department of Defense and/or other government practices (comparing NASA's program with organizations and projects having similar volumes of software development, software maturity, complexity, criticality, lines of code, and national standards); (4) consider whether independent verification and validation should continue. An overview of the study, independent verification and validation of critical software, and the Space Shuttle flight software development process are addressed. Findings and recommendations are presented.
Source record↗
Development of an Expert System for Representing Procedural Knowledge
A high level of automation is of paramount importance in most space operations. It is critical for unmanned missions and greatly increases the effectiveness of manned missions. However, although many functions can be automated by using advanced engineering techniques, others require complex reasoning, sensing, and manipulatory capabilities that go beyond this technology. Automation of fault diagnosis and malfunction handling is a case in point. The military have long been interested in this problem, and have developed automatic test equipment to aid in the maintenance of complex military hardware. These systems are all based on conventional software and engineering techniques. However, the effectiveness of such test equipment is severely limited. The equipment is inflexible and unresponsive to the skill level of the technicians using it. The diagnostic procedures cannot be matched to the exigencies of the current situation nor can they cope with reconfiguration or modification of the items under test. The diagnosis cannot be guided by useful advice from technicians and, when a fault cannot be isolated, no explanation is given as to the cause of failure. Because these systems perform a prescribed sequence of tests, they cannot utilize knowledge of a particular situation to focus attention on more likely trouble spots. Consequently, real-time performance is highly unsatisfactory. Furthermore, the cost of developing test software is substantial and time to maturation is excessive. Significant advances in artificial intelligence (AI) have recently led to the development of powerful and flexible reasoning systems, known as expert or knowledge-based systems. We have devised a powerful and theoretically sound scheme for representing and reasoning about procedural knowledge.
Georgeff, Michael P.↗
Software Manages Documentation in a Large Test Facility
The 3MCS computer program assists and instrumentation engineer in performing the 3 essential functions of design, documentation, and configuration management of measurement and control systems in a large test facility. Services provided by 3MCS are acceptance of input from multiple engineers and technicians working at multiple locations;standardization of drawings;automated cross-referencing; identification of errors;listing of components and resources; downloading of test settings; and provision of information to customers.
Gurneck, Joseph M.↗
Guidance and Control Software Project Data - Volume 3: Verification Documents
The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the verification documents from the GCS project. Volume 3 contains four appendices: A. Software Verification Cases and Procedures for the Guidance and Control Software Project; B. Software Verification Results for the Pluto Implementation of the Guidance and Control Software; C. Review Records for the Pluto Implementation of the Guidance and Control Software; and D. Test Results Logs for the Pluto Implementation of the Guidance and Control Software.
Hayhurst, Kelly J.↗
SMC Message Browser Projects
I work directly with the System Monitoring and Control (SMC) software engineers who develop, test and release custom and commercial software in support of the Kennedy Space Center Spaceport Command and Control System. (SCCS). SMC uses Commercial Off-The-Shelf (COTS) Enterprise Management Systems (EMS) software which provides a centralized subsystem for configuring, monitoring, and controlling SCCS hardware and software used in the Control Rooms. There are multiple projects being worked on using the COTS EMS software. I am currently working with the HP Operations Manager for UNIX (OMU) software which allows Master Console Operators (MCO) to access, view and interpret messages regarding the status of the SCCS hardware and software. The OMU message browser gets cluttered with messages which can make it difficult for the MCO to manage. My main project involves determining ways to reduce the number of messages being displayed in the OMU message browser. I plan to accomplish this task in two different ways: (1) by correlating multiple messages into one single message being displayed and (2) to create policies that will determine the significance of each message and whether or not it needs to be displayed to the MCO. The core idea is to lessen the number of messages being sent to the OMU message browser so the MCO can more effectively use it.
OMU↗
Testing and Application of Commercial Thermodynamics Software for Solid-Gas Equilibria in Planetary Science Applications
The ability to calculate chemical equilibria from thermochemical constants (e.g., H, S, Cp) or other experimental data is a tool widely employed by scientists. However, phase equilibria for planetary science problems is limited by easy access to libraries of thermochemical data, as well as the software to invert that data. Many academic software packages are focused on specific types of problems (e.g., aqueous solutions or melting and crystallization of magmas). This focus makes them excellent tools for specific uses, but poorer tools for other scenarios, especially those involving elements or chemical species that are less well-studied in that specific scientific field (e.g. NaCl vapor). Amongst the more general thermodynamic software tools, there are closed academic software packages, open-source options, as well as commercial software. We have explored the extent to which commercial chemistry/chemical engineering software may be able to satisfy the need for thermochemical modeling packages that can accommodate the diverse species and conditions of planetary science problems. Here we compare the output of software package HSC Chemistry™ (Metso Outotec) to published vapor-solid phase diagrams for a variety of major and minor elements. HSC Chemistry™ has been used in several recent geochemical studies of terrestrial volcanic systems [2- 4]. However, it has not to our knowledge been benchmarked against peer-reviewed model results for the conditions and compositions relevant to planetary science. We present one such comparison here, the low- pressure environment of the solar nebula, using literature data. In short, we find excellent agreement between HSC Chemistry™ and the well-regarded academic software package CONDOR. These preliminary results suggest that at least some commercial software packages are capable of robust thermochemical calculations for planetary science.
planetary science↗
ECS Artemis II Upgrades
The National Aeronautics and Space Administration (NASA) actively works to further the expectations of space exploration and research. NASA has been able to develop innovative technology and methods that has allowed for continued discovery and innovation. NASA is in the midst of work for the Artemis mission, which is to return to the moon in an effort to prepare for future Mars exploration. After the successful launch of Artemis I last November, our sights have shifted to Artemis II, which is set to launch next year and bring humans into the lunar orbit for the first time in over fifty years. Artemis II will be the first crewed mission for the program and will represent another step forward in our mission to advance our knowledge of the universe around us. From there, the Artemis program will move onto building a permanent site on the moon that will allow us to eventually reach Mars. During my time at NASA, I was able to work with the NE-XF Branch, also known as the Environmental and Life Support Systems Branch. I specifically worked with the Environmental Control Systems (ECS) team. During my time here, construction on the system in the Vehicle Assembly Building (VAB) and at Launchpad 39B have been progressing at full force. ECS is used to provide processed and purged air at specific temperatures, pressures, and humidity’s to fulfill requirements necessary to support Orion and the SLS. While the Pad has been undergoing upgrades from the original Artemis I configuration, the VAB has a completely new ECS very similar to it. While both systems have been undergoing upgrades, we have been able to transition into testing the systems as we prepare for stacking in the VAB early next year. My role has allowed me to learn about how the systems work and function through walkdowns and visits out to both the Pad and the VAB. I’ve been able to see firsthand how the system operates and have learned how the system affects the vehicle. I’ve been able to shadow my mentor, my coworkers, and COMET operators to oversee the construction efforts of the system along with the testing of the software and the system itself. I even was able to aid in testing at the console myself at Pad 39B. Additionally, I am also revising and reviewing displays for Artemis IV that will be used to remotely control parts of the system. Eventually these displays will be used to support the future of Artemis.
Monique Toon↗
Using Penelope to assess the correctness of NASA Ada software: A demonstration of formal methods as a counterpart to testing
Life-critical applications warrant a higher level of software reliability than has yet been achieved. Since it is not certain that traditional methods alone can provide the required ultra reliability, new methods should be examined as supplements or replacements. This paper describes a mathematical counterpart to the traditional process of empirical testing. ORA's Penelope verification system is demonstrated as a tool for evaluating the correctness of Ada software. Grady Booch's Ada calendar utility package, obtained through NASA, was specified in the Larch/Ada language. Formal verification in the Penelope environment established that many of the package's subprograms met their specifications. In other subprograms, failed attempts at verification revealed several errors that had escaped detection by testing.
Eichenlaub, Carl T.↗
Advances in High-rate Delay Tolerant Networking On-board the International Space Station
The High-rate Delay Tolerant Networking (HDTN) project at the NASA John H. Glenn Research Center (GRC) is developing a performance optimized Delay Tolerant Networking (DTN) implementation which is able to provide reliable multigigabit per second automated network communications for near-Earth and deep space missions. To that end, this paper provides an overview of the testing and integration efforts culminating in a high-rate DTN demonstration onboard the International Space Station (ISS). Over several years, the HDTN team has performed a series of end-to-end tests between the Software Development and Integration Laboratory (SDIL) at the Lyndon B. Johnson Space Center (JSC) and Marshall Space Flight Center’s Huntsville Operations Support Center (HOSC). The testing has focused on a realistic emulation of the ISS Ku-band RF link, which operates at a maximum of 500 Mbps downlink with a 600 ms round-trip time. In this environment, the HDTN onboard gateway has been tested for interoperability with ISS payload nodes and the DTN ground gateway, store and forward capability, reliable transport using the Licklider Transmission Protocol (LTP), and successful recovery from unexpected loss of signal. In addition to integration testing, HDTN has developed a series of software engineering practices to ensure the stability and maturity of the implementation. As the result, HDTN has successfully demonstrated high-rate DTN services onboard the ISS. This paper concludes with a summary of preliminary flight testing results from the Integrated LCRD LEO User Modem and Amplifier Terminal networking experiments.
Delay tolerant networking↗
Fault-tolerance experiments with the JPL STAR computer.
Results of fault-tolerance experiments performed using an experimental computer with dynamic (standby) redundancy, including replaceable subsystems and a 'program rollback' provision to eliminate transient-caused errors. After a brief review of the specification of fault-tolerance with respect to transient faults, including a description of the method of injection of transient faults in software and system tests, fault-tolerance experiments carried out with this computer with regard to the determination of fault classes, software verification, system verification, and recovery stability are summarized. A test and repair processor is described which constitutes a special monitor unit of the computer and is used to obtain information for fault detection in the other subsystems of the computer and to ensure that proper recovery occurs when a fault is detected.
Avizienis, A.↗
Integrated testing and verification system for research flight software design document
The NASA Langley Research Center is developing the MUST (Multipurpose User-oriented Software Technology) program to cut the cost of producing research flight software through a system of software support tools. The HAL/S language is the primary subject of the design. Boeing Computer Services Company (BCS) has designed an integrated verification and testing capability as part of MUST. Documentation, verification and test options are provided with special attention on real time, multiprocessing issues. The needs of the entire software production cycle have been considered, with effective management and reduced lifecycle costs as foremost goals. Capabilities have been included in the design for static detection of data flow anomalies involving communicating concurrent processes. Some types of ill formed process synchronization and deadlock also are detected statically.
Taylor, R. N.↗
Load Control System Reliability
This report summarizes the results of the Load Control System Reliability project (DOE Award DE-FC26-06NT42750). The original grant was awarded to Montana Tech April 2006. Follow-on DOE awards and expansions to the project scope occurred August 2007, January 2009, April 2011, and April 2013. In addition to the DOE monies, the project also consisted of matching funds from the states of Montana and Wyoming. Project participants included Montana Tech; the University of Wyoming; Montana State University; NorthWestern Energy, Inc., and MSE. Research focused on two areas: real-time power-system load control methodologies; and, power-system measurement-based stability-assessment operation and control tools. The majority of effort was focused on area 2. Results from the research includes: development of fundamental power-system dynamic concepts, control schemes, and signal-processing algorithms; many papers (including two prize papers) in leading journals and conferences and leadership of IEEE activities; one patent; participation in major actual-system testing in the western North American power system; prototype power-system operation and control software installed and tested at three major North American control centers; and, the incubation of a new commercial-grade operation and control software tool. Work under this grant certainly supported the DOE-OE goals in the area of “Real Time Grid Reliability Management.”
29 ENERGY PLANNING, POLICY, AND ECONOMY↗
Moment Closures on Two-Dimensional Cartesian Grids
Some moment methods for kinetic equations are complicated and take time to develop. Over the course of a couple years, this software was developed to test different closures on standard test problems in the literature. With this software, researchers in the field of moment closures will be able to rapidly test new methods.
Garrett, CharlesK.↗
Moment Closures on Two-Dimensional Cartesian Grids
Some moment methods for kinetic equations are complicated and take time to develop. Over the course of a couple years, this software was developed to test different closures on standard test problems in the literature. With this software, researchers in the field of moment closures will be able to rapidly test new methods.
Garrett, Charles K.↗
Extended Bandwidth Spread Spectrum Time Domain Reflectometry Cable Test for Thermal Aging, Low Resistance Fault, and Water Detection
In 2022, researchers at Pacific Northwest National Laboratory (PNNL) used the Accelerated and Real-Time Environmental Nodal Assessment (ARENA) cable and motor test bed to characterize spread spectrum time domain reflectometry (SSTDR) and compare the responses of an SSTDR instrument to those of a frequency domain reflectometry (FDR) instrument. Results showed both techniques could detect and locate cable anomalies such as phase-to-phase low resistance and shorts, thermal insulation damage, mechanical insulation damage, and the presence or absence of water in some conditions. The SSTDR tests used a commercial instrument provided by LiveWire Innovations Inc. This commercial instrument performed tests at 6, 12, 24, and 48 MHz bandwidth. The results of these tests were compared to FDR tests where bandwidths could be extended up to 1.3 GHz, although the best responses for cable tests were from 100 to 500 MHz. Lower bandwidth signals can propagate better along the cable while higher bandwidths have higher resolution for impedance change reflections allowing more precise indication of location and separation of anomalies. The 2022 research found that FDR responses were clearer than SSTDR and speculated that a higher bandwidth SSTDR could more successfully detect and locate cable anomalies. One advantage of the SSTDR system investigated was that it was designed for energized online use up to 1,000 volts, which may be a significant advantage for nuclear power plant use. The LiveWire SSTDR instrument is an established product in the rail and aircraft industry and updating the SSTDR hardware parameters is difficult to justify without more conclusive testing. Therefore, a software adjustable laboratory SSTDR instrument was developed by PNNL and was used to test extended bandwidth SSTDR cable tests. Within the ARENA test bed, 42 cable conditions were tested with the PNNL SSTDR, FDR, and the LiveWire SSTDR—each operating at four different bandwidths. Observations and conclusions regarding the relative performance of the three instruments over different bandwidths are note below. Responses of the PNNL SSTDR (at 50 MHz) and the LiveWire SSTDR (at 48 MHz) were similar. The PNNL SSTDR higher frequency bandwidths behaved as expected showing sharper peaks and higher noise. This validated the PNNL SSTDR as a reasonable implementation of the SSTDR technology. Lower bandwidth SSTDR responses (particularly 6 and 12 MHz) may have increased value for use within longer cables but were not particularly effective at identifying anomalous cable behavior in the 100 ft cables tested here. The higher bandwidths of the PNNL SSTDR (50, 100, 200, and 400 MHz) did not provide substantially clearer cable reflectometry responses, but having the higher frequency responses available did add to the cable test evaluation. Strong responses to shorts and low impedance faults between phases were particularly evident in the higher bandwidth PNNL SSTDR and the FDR data. Measurements were repeatable, with similar responses obtained from a thermally aged cable for tests taken a month apart. Signal noise was affected in the unshielded cable by the local in-tray cable arrangement including proximity to metal edges and rungs of the cable tray. Foam isolation of the cable from the tray metal reduced in both FDR and SSTDR responses. Cable condition monitoring in nuclear power plants will likely benefit from both more informative off-line testing methods and from the development of on-line methods for continuous monitoring of cables in use. The LWRS-funded ARENA test bed was a valuable resource for this development and direct comparison of nuclear electrical cable condition monitoring technologies. Test results are targeted to guide industry advancement of testing and monitoring tools for cable aging management.
21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗