Search NASA⌕ Search

SEARCH · Search NASA

Results for “Software Test Tool”

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.

At least 469 records · Page 26

Simscape Modeling Verification in the Simulink Development Environment

The purpose of the Simulation Product Group of the Control and Data Systems division of the NASA Engineering branch at Kennedy Space Center is to provide a realtime model and simulation of the Ground Subsystems participating in vehicle launching activities. The simulation software is part of the Spaceport Command and Control System (SCCS) and is designed to support integrated launch operation software verification, and console operator training. Using Mathworks Simulink tools, modeling engineers currently build models from the custom-built blocks to accurately represent ground hardware. This is time consuming and costly due to required rigorous testing and peer reviews to be conducted for each custom-built block. Using Mathworks Simscape tools, modeling time can be reduced since there would be no custom-code developed. After careful research, the group came to the conclusion it is feasible to use Simscape's blocks in MatLab's Simulink. My project this fall was to verify the accuracy of the Crew Access Arm model developed using Simscape tools running in the Simulink development environment.

SIMSCAPE↗

Making or Breaking a Rover: System Engineering Parameters On-Board the Mars 2020 Perseverance Rover

On February 18, 2021, Perseverance, NASA’s Jet Propulsion Laboratory’s (JPL’s) Mars 2020 Rover, successfully landed on Mars with all systems nominal, despite the risk surrounding the over 200,000 internal flight parameters that had to be properly configured. The Perseverance team defines these parameters as software variables that are configurable, commandable and retrievable from Earth. In 2015, the Mars 2020 project leaders focused on improving systems engineering of parameters based on their experiences from parameter management on previous Mars rovers (Curiosity, Opportunity, Spirit, and Pathfinder) and parameter failures of past missions, such as the mission-ending parameter of the Mars Climate Orbiter. The new rigorous development process allowed for efficient certification and effective implementation of the parameters, allowing the rover to approach and land on the red planet (the most challenging phase of the mission) with zero parameter issues. Although successful, the Perseverance team learned many lessons for how to better manage parameters for the continued surface operations of the Mars 2020 mission and future missions. This paper will discuss eight parameter-management topics for the Perseverance Mission. The first is parameter definition: how we define parameters on our mission, where they are physically located on the vehicle, and why we have so many of them. The second topic is the updated parameter flight software module from Curiosity, including details on the 99% reduction in parameter commands, new bulk configuration capabilities, and improved parameter traceability. The third topic is parameter selection for different mission phases; this includes improving and tweaking our preferred parameter settings until they become certification candidates and managing parameter configurations based on test venue throughout the mission life cycle. The fourth topic is our flight certification process; this includes certification of flight values for four different epochs in the mission: Launch, Entry Decent and Landing (EDL) - 6days, Landing + 5 Sols (Martian Days, still on Cruise Flight Software), and once are on Surface Flight Software (FSW). The fifth topic covers in-flight command implementation, along with details on testing, validation, and verification of those commands. In the sixth section, we will explain our use of open-source management tools, including how we used GitHub for version control and management approvals. The seventh topic will describe the ground tools used in operations, including capabilities of the in-house built tool called Parasol. The eighth and final topic will dig into lessons learned for improving parameter management in the future of this mission and others.

Roth, Brian↗

Making or Breaking a Rover- Systems Engineering Parameters On-Board the Mars 2020 Perseverance Rover

On February 18, 2021, Perseverance, NASA’s Jet Propulsion Laboratory’s (JPL’s) Mars 2020 Rover, successfully landed on Mars with all systems nominal, despite the risk surrounding the over 200,000 internal flight parameters that had to be properly configured. The Perseverance team defines these parameters as software variables that are configurable, commandable and retrievable from Earth. In 2015, the Mars 2020 project leaders focused on improving systems engineering of parameters based on their experiences from parameter management on previous Mars rovers (Curiosity, Opportunity, Spirit, and Pathfinder) and parameter failures of past missions, such as the mission-ending parameter of the Mars Climate Orbiter. The new rigorous development process allowed for efficient certification and effective implementation of the parameters, allowing the rover to approach and land on the red planet (the most challenging phase of the mission) with zero parameter issues. Although successful, the Perseverance team learned many lessons for how to better manage parameters for the continued surface operations of the Mars 2020 mission and future missions. This paper will discuss eight parameter-management topics for the Perseverance Mission. The first is parameter definition: how we define parameters on our mission, where they are physically located on the vehicle, and why we have so many of them. The second topic is the updated parameter flight software module from Curiosity, including details on the 99% reduction in parameter commands, new bulk configuration capabilities, and improved parameter traceability. The third topic is parameter selection for different mission phases; this includes improving and tweaking our preferred parameter settings until they become certification candidates and managing parameter configurations based on test venue throughout the mission life cycle. The fourth topic is our flight certification process; this includes certification of flight values for four different epochs in the mission: Launch, Entry Decent and Landing (EDL) - 6days, Landing + 5 Sols (Martian Days, still on Cruise Flight Software), and once are on Surface Flight Software (FSW). The fifth topic covers in-flight command implementation, along with details on testing, validation, and verification of those commands. In the sixth section, we will explain our use of open-source management tools, including how we used GitHub for version control and management approvals. The seventh topic will describe the ground tools used in operations, including capabilities of the in-house built tool called Parasol. The eighth and final topic will dig into lessons learned for improving parameter management in the future of this mission and others.

Roth, Brian↗

PROTECT: Production and Reuse of Thermally Efficient Ceramic Thermal Protection Systems

PROTECT (Production and Reuse Of Thermally Efficient Ceramic TPS) is a NASA Early Career Initiative focused on developing the next generation of reusable ceramic thermal protection systems (TPS). This project addresses key challenges in TPS design, including temperature capability, thermal stability, and refurbishment time, by integrating novel material development with predictive modeling. Leveraging enhanced capabilities in NASA’s Porous Microstructure Analysis (PuMA) software, PROTECT introduces new modeling tools to predict the thermal and mechanical behavior of fibrous ceramic materials. These tools enable accurate prediction of performance metrics such as thermal conductivity and structural integrity, reducing reliance on costly physical testing. Preliminary advances in these areas will be presented. To support model validation, PROTECT is building a comprehensive database of raw material properties using advanced characterization techniques, including micro computed tomography (CT) scanning in collaboration with the University of Illinois Urbana-Champaign (UIUC). The presentation will detail the sampling workflows and analysis methods used to generate this detailed microstructural data and how it is used to develop improved models in PuMA. This multi-center collaboration, spanning NASA (JSC, ARC, KSC, GRC), Oak Ridge National Laboratory, UIUC, and SpaceX, is developing tailored TPS solutions for LEO, lunar, and Martian missions. By bridging heritage systems with the demands of modern spaceflight, PROTECT contributes to the advancement of reusable TPS technologies for future exploration missions.

Propulsion, Refractory, and Coating Materials↗

PROTECT: Production and Reuse of Thermally Efficient Ceramic Thermal Protection Systems

PROTECT (Production and Reuse Of Thermally Efficient Ceramic TPS) is a NASA Early Career Initiative focused on developing the next generation of reusable ceramic thermal protection systems (TPS). This project addresses key challenges in TPS design, including temperature capability, thermal stability, and refurbishment time, by integrating novel material development with predictive modeling. Leveraging enhanced capabilities in NASA’s Porous Microstructure Analysis (PuMA) software, PROTECT introduces new modeling tools to predict the thermal and mechanical behavior of fibrous ceramic materials. These tools enable accurate prediction of performance metrics such as thermal conductivity and structural integrity, reducing reliance on costly physical testing. Preliminary advances in these areas will be presented. To support model validation, PROTECT is building a comprehensive database of raw material properties using advanced characterization techniques, including micro computed tomography (CT) scanning in collaboration with the University of Illinois Urbana-Champaign (UIUC). The presentation will detail the sampling workflows and analysis methods used to generate this detailed microstructural data and how it is used to develop improved models in PuMA. This multi-center collaboration, spanning NASA (JSC, ARC, KSC, GRC), Oak Ridge National Laboratory, UIUC, and SpaceX, is developing tailored TPS solutions for LEO, lunar, and Martian missions. By bridging heritage systems with the demands of modern spaceflight, PROTECT contributes to the advancement of reusable TPS technologies for future exploration missions.

Propulsion, Refractory, and Coating Materials↗

A Multiple Parameters Biodosimetry Tool with Various Blood Cell Counts - the Hemodose Approach

There continue to be important concerns about the possibility of the occurrence of acute radiation syndromes following nuclear and radiological terrorism or accidents that may result in mass casualties in densely populated areas. To guide medical personnel in their clinical decisions for effective medical management and treatment of the exposed individuals, biological markers are usually applied to examine radiation induced biological changes to assess the severity of radiation injury to sensitive organ systems. Among these the peripheral blood cell counts are widely used to assess the extent of radiation induced bone marrow injury. This is due to the fact that the hematopoietic system is the most vulnerable part of the human body to radiation damage. Particularly, the lymphocyte, granulocyte, and platelet cells are the most radiosensitive of the blood elements, and monitoring their changes after exposure is regarded as a practical and recommended laboratory test to estimate radiation dose and injury. Based upon years of physiological and pathophysiological investigation of mammalian hematopoietic systems, and rigorous coarse-grained bio-mathematical modeling and validation on species from mouse, to dog, monkey, and human, we have developed a set of software tools Hemodose, which can use single or serial granulocyte, lymphocyte, leukocyte, or platelet counts after exposure to estimate absorbed doses of adult victims very rapidly and accurately. Some patient data from historical accidents are utilized as examples to demonstrate the capabilities of these tools as a rapid point-of-care diagnostic or centralized high-throughput assay system in a large-scale radiological disaster scenario. Most significant to the improvement of national and local preparedness of a potential nuclear/radiological disaster, this HemoDose approach establishes robust correlations between the absorbed doses and victim's various types of blood cell counts not only in the early time window (1 or 2 days), but also in the very late phase (up to 4 weeks) after exposure.

Hu, Shaowen↗

Radio-frequency interference effects of continuous sinewave signals on telemetry data

Continuous sinewave interference effects on telemetry data obtained at the Goldstone Deep Space Station (DSS 11) were analyzed. The continuous sinewave interference is treated as an extraneous noise. Empirical telemetry data degradation and drop-lock models were then developed based on test data and certain physical characteristics of the telemetry data processing system. These models will be used as a portion of the radio frequency interference detection tools in the first version of the Deep Space Interference Prediction software.

Low, P. W.↗

A strip chart recorder pattern recognition tool kit for Shuttle operations

During Space Shuttle operations, Mission Control personnel monitor numerous mission-critical systems such as electrical power; guidance, navigation, and control; and propulsion by means of paper strip chart recorders. For example, electrical power controllers monitor strip chart recorder pen traces to identify onboard electrical equipment activations and deactivations. Recent developments in pattern recognition technologies coupled with new capabilities that distribute real-time Shuttle telemetry data to engineering workstations make it possible to develop computer applications that perform some of the low-level monitoring now performed by controllers. The number of opportunities for such applications suggests a need to build a pattern recognition tool kit to reduce software development effort through software reuse. We are building pattern recognition applications while keeping such a tool kit in mind. We demonstrated the initial prototype application, which identifies electrical equipment activations, during three recent Shuttle flights. This prototype was developed to test the viability of the basic system architecture, to evaluate the performance of several pattern recognition techniques including those based on cross-correlation, neural networks, and statistical methods, to understand the interplay between an advanced automation application and human controllers to enhance utility, and to identify capabilities needed in a more general-purpose tool kit.

Hammen, David G.↗

Low-Earth-Orbiter resource allocation and capacity planning for the DSN using LEO4CAST

The Deep Space Network provides tracking and communication services for a number of U.S. and international low-Earth-orbiting (LEO) and near-Earth missions. This service is supplied by the 26-m subnet (located at each of the DSN complexes), the 9-m and the 34-m Antenna Research System antennas at Goldstone, and the 11-m antennas (following the orbital VLBI mission). An increasing number of LEO missions are planned for DSN support, which will result in increasingly complex ground resource allocation and mission support trades. To support TDA decision making on mission support and cost-effective ground system evolution for this 26-m subnet, LEO4CAST has been developed. LEO4CAST is a tool that uses statistical approaches to provide useful information for long-term ground system capacity planning and near-term resource allocation (prior to detailed time-of-day scheduling). LEO4CAST is currently beta-test software and is being exercised by both the Office of Telecommunications and Data Acquisition (TDA) and the JPL Systems Division.

Fox, G.↗

Software Simulates Sight: Flat Panel Mura Detection

In the increasingly sophisticated world of high-definition flat screen monitors and television screens, image clarity and the elimination of distortion are paramount concerns. As the devices that reproduce images become more and more sophisticated, so do the technologies that verify their accuracy. By simulating the manner in which a human eye perceives and interprets a visual stimulus, NASA scientists have found ways to automatically and accurately test new monitors and displays. The Spatial Standard Observer (SSO) software metric, developed by Dr. Andrew B. Watson at Ames Research Center, measures visibility and defects in screens, displays, and interfaces. In the design of such a software tool, a central challenge is determining which aspects of visual function to include while accuracy and generality are important, relative simplicity of the software module is also a key virtue. Based on data collected in ModelFest, a large cooperative multi-lab project hosted by the Optical Society of America, the SSO simulates a simplified model of human spatial vision, operating on a pair of images that are viewed at a specific viewing distance with pixels having a known relation to luminance. The SSO measures the visibility of foveal spatial patterns, or the discriminability of two patterns, by incorporating only a few essential components of vision. These components include local contrast transformation, a contrast sensitivity function, local masking, and local pooling. By this construction, the SSO provides output in units of "just noticeable differences" (JND) a unit of measure based on the assumed smallest difference of sensory input detectable by a human being. Herein is the truly amazing ability of the SSO, while conventional methods can manipulate images, the SSO models human perception. This set of equations actually defines a mathematical way of working with an image that accurately reflects the way in which the human eye and mind behold a stimulus. The SSO is intended for a wide variety of applications, such as evaluating vision from unmanned aerial vehicles, measuring visibility of damage to aircraft and to the space shuttles, predicting outcomes of corrective laser eye surgery, inspecting displays during the manufacturing process, estimating the quality of compressed digital video, evaluating legibility of text, and predicting discriminability of icons or symbols in a graphical user interface.

Source record↗

Copernicus Spacecraft Trajectory Design and Optimization Program

Copernicus is a spacecraft trajectory design and optimization application developed at the NASA Johnson Space Center. Copernicus is written in Fortran and uses many features of the latest language standards. The tool is used for a wide range of projects at NASA, including the upcoming Artemis missions to flight test the Orion spacecraft and then return humans to the Moon. This presentation gives a brief overview of the software, its history, how it was designed, and how it is used.

Copernicus↗

Internet Technology on Spacecraft

The Operating Missions as Nodes on the Internet (OMNI) project has shown that Internet technology works in space missions through a demonstration using the UoSAT-12 spacecraft. An Internet Protocol (IP) stack was installed on the orbiting UoSAT-12 spacecraft and tests were run to demonstrate Internet connectivity and measure performance. This also forms the basis for demonstrating subsequent scenarios. This approach provides capabilities heretofore either too expensive or simply not feasible such as reconfiguration on orbit. The OMNI project recognized the need to reduce the risk perceived by mission managers and did this with a multi-phase strategy. In the initial phase, the concepts were implemented in a prototype system that includes space similar components communicating over the TDRS (space network) and the terrestrial Internet. The demonstration system includes a simulated spacecraft with sample instruments. Over 25 demonstrations have been given to mission and project managers, National Aeronautics and Space Administration (NASA), Department of Defense (DoD), contractor technologists and other decisions makers, This initial phase reached a high point with an OMNI demonstration given from a booth at the Johnson Space Center (JSC) Inspection Day 99 exhibition. The proof to mission managers is provided during this second phase with year 2000 accomplishments: testing the use of Internet technologies onboard an actual spacecraft. This was done with a series of tests performed using the UoSAT-12 spacecraft. This spacecraft was reconfigured on orbit at very low cost. The total period between concept and the first tests was only 6 months! On board software was modified to add an IP stack to support basic IP communications. Also added was support for ping, traceroute and network timing protocol (NTP) tests. These tests show that basic Internet functionality can be used onboard spacecraft. The performance of data was measured to show no degradation from current approaches. The cost to implement is much less than current approaches due to the availability of highly reliable and standard Internet tools. Use of standard Internet applications onboard reduces the risk of obsolescence inherent in custom protocols due to extremely wide use across all domains. These basic building blocks provide the framework for building onboard software to support direct user communication with payloads including payload control. Other benefits are payload to payload communication from dissimilar spacecraft, constellations of spacecraft, and reconfigurability on orbit. This work is funded through contract with the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC).

Rash, James↗

A History of Orion Mission Design, Copernicus Software Development, and the Artemis I Trajectory

This paper describes the history of the on-orbit trajectory design and optimization for the Orion spacecraft at NASA JSC, from the initial design through the execution of the Artemis I test flight. In parallel, the Copernicus trajectory optimization tool was also being developed and was the main tool used for Orion trajectory design during this period. Finally, the paper gives an overview of the Artemis I trajectory that was flown during the Artemis I mission from November 16 - December 11, 2022.

Orion↗

Library reuse in a rapid development environment

The Aeroscience and Flight Mechanics Division (AFMD) established a Rapid Development Laboratory (RDL) to investigate and improve new 'rapid development' software production processes and refine the use of commercial, off-the-shelf (COTS) tools. These tools and processes take an avionics design project from initial inception through high fidelity, real-time, hardware-in-the-loop (HIL) testing. One central theme of a rapid development process is the use and integration of a variety of COTS tools: This paper discusses the RDL MATRIX(sub x)(R) libraries, as well as the techniques for managing and documenting these libraries. This paper also shows the methods used for building simulations with the Advanced Simulation Development System (ASDS) libraries, and provides metrics to illustrate the amount of reuse for five complete simulations. Combining ASDS libraries with MATRIX(sub x)(R) libraries is discussed.

Uhde, JO↗

Program For Editing Graphical Displays Of Schedules

XOPPS is window-based software tool from graphics providing easy and fast "what you see is what you get" (WYSIWYG) on-screen editing capabilities. Provides area, analogous to canvas, displaying full image of schedule being edited. Canvas contains header area (for test) and schedule area (for plotting graphical representations of milestone objects in flexible time line). Written in C language.

Mulnix, Cassie L.↗

Analysis of The Interaction of Space Tethers with Catalogued Space Objects

The potential for collisions or close passes with other space objects presents a significant issue for many space tether applications, representing a potential risk both to the integrity of the tether system and t o the safety of other spacecraft. Potential collisions between tethers and other space objects may be possible to avoid if close encounters can be predicted with sufficient precision and advance notice. In order to provide a method for predicting the frequency with which a tether must be maneuvered to avoid collisions, and to provide a resource for accurate close-encounter prediction during tether flight experiments, we have developed a software tool that compares the trajectory of a tether object with that of all of the objects in the NORAD space catalogue. In this paper we describe the models and algorithms used in this tool, and discuss results of test cases conducted to predict the close-encounter frequency of a tether systems ranging from a short nanosatellite-based tether experiment to a hundred-kilometer long MXER tether system.

Bonometti, Joseph↗

Lessons Learned During the Refurbishment and Testing of an Observatory After Long-Term Storage

Thermal Fluids Analysis Workshop (TFAWS) 2015, Silver Spring, MD NCTS 21070-15. This paper addresses the lessons learned during the refurbishment and testing of the thermal control system for a spacecraft which was placed into long-term storage. The DSCOVR (Deep Space Climate Observatory) Observatory (formerly known as Triana) was originally scheduled to launch on the Space Shuttle in 2002. With the Triana spacecraft nearly complete, the mission was canceled and the satellite was abruptly put into storage in 2001. In 2008 the observatory was removed from storage to begin refurbishment and testing. Problems arose associated with hardware that was not currently manufactured, coatings degradation, and a significant lack of documentation. Also addressed is the conversion of the thermal and geometric math models for use with updated thermal analysis software tools.

Thermal Control System↗

Leveraging Commercial Software Defined Radio for Low Cost Deep Space Testing

In a typical space mission development life cycle, there is a stage where the spacecraft needs to test against the ground station for interface compatibility to ensure that the spacecraft will be properly tracked after launch. This testing normally requires the spacecraft team to bring their flight equipment to the ground station facility. While recognizing that testing with actual flight or engineering module is the most preferred option because of maximum fidelity, there are occasion when the use of actual flight hardware is a logistically challenge because of spacecraft development. Having another test tool that can emulate the spacecraft signal – by recording the signal transmitted by the spacecraft and regenerate an RF signal for ground system testing - would be very useful. It is even more an attractive option if such spacecraft emulator is inexpensive and highly portable. In this paper, we describe a low-cost, light-weight recorder/playback assembly (RPA) that supports deep space missions testing. The equipment leverages on commercially available software defined radios (SDR) and public-domain software. The RPA has been used to support two missions. One effort is to validate that the Uchinoura 34-m tracking station of the Japanese Aerospace Exploration Agency (JAXA) would be able to track the upcoming NASA Exploration Mission 1 (EM-1) spacecraft, scheduled for launch in 2019. The second effort is to help with the testing and certification of the 21-m antenna ground station at the Morehead State University (MSU) in Kentucky, United States, prior to the time when the Lunar IceCube spacecraft is ready for actual compatibility testing. The RPA also enables students/staff training of the new ground station, using the RPA signal as test input into the system. This low-cost test signal allows the MSU team to save money on not having to develop a full-scale self-generated telemetry test signal source.

White, Leslie↗