Search NASA⌕ Search

SEARCH · Search NASA

Results for “space flight software”

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 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
NASA NTRS1996

Quantitative Measures for Software Independent Verification and Validation

As software is maintained or reused, it undergoes an evolution which tends to increase the overall complexity of the code. To understand the effects of this, we brought in statistics experts and leading researchers in software complexity, reliability, and their interrelationships. These experts' project has resulted in our ability to statistically correlate specific code complexity attributes, in orthogonal domains, to errors found over time in the HAL/S flight software which flies in the Space Shuttle. Although only a prototype-tools experiment, the result of this research appears to be extendable to all other NASA software, given appropriate data similar to that logged for the Shuttle onboard software. Our research has demonstrated that a more complete domain coverage can be mathematically demonstrated with the approach we have applied, thereby ensuring full insight into the cause-and-effects relationship between the complexity of a software system and the fault density of that system. By applying the operational profile we can characterize the dynamic effects of software path complexity under this same approach We now have the ability to measure specific attributes which have been statistically demonstrated to correlate to increased error probability, and to know which actions to take, for each complexity domain. Shuttle software verifiers can now monitor the changes in the software complexity, assess the added or decreased risk of software faults in modified code, and determine necessary corrections. The reports, tool documentation, user's guides, and new approach that have resulted from this research effort represent advances in the state of the art of software quality and reliability assurance. Details describing how to apply this technique to other NASA code are contained in this document.

Lee, Alice↗
NASA NTRS1997

STIS target acquisition

We describe the STIS autonomous target acquisition capabilities. We also present the results of dedicated tests executed as part of Cycle 7 calibration, following post-launch improvements to the Space Telescope Imaging Spectrograph (STIS) flight software. The residual pointing error from the acquisitions are < 0.5 CCD pixels, which is better than preflight estimates. Execution of peakups show clear improvement of target centering for slits of width 0.1 sec or smaller. These results may be used by Guest Observers in planning target acquisitions for their STIS programs.

Kraemer, Steve↗
NASA NTRS1999

Testing of the International Space Station and X-38 Crew Return Vehicle GPS Receiver

This paper discusses the process and results of the performance testing of the GPS receiver planned for use on the International Space Station (ISS) and the X- 38CrewReturnVehicle(CRV). The receiver is a Force-19 unit manufactured by Trimble Navigation and modified in software by NASA:s Goddard Space Flight Center (GSFC) to perform navigation and attitude determination in space. The receiver is the primary source of navigation and attitude information for ISS and CRV. Engineers at GSFC have developed and tested the new receiver with a Global Simulation Systems Ltd (GSS) GPS Signal Generator (GPSSG). This paper documents the unique aspects of ground testing a GPS receiver that is designed for use in space. A discussion of the design of tests using the GPSSG, documentation, data capture, data analysis, and lessons learned will precede an overview of the performance of the new receiver. A description of the challenges that were overcome during this testing exercise will be presented. Results from testing show that the receiver will be within or near the specifications for ISS attitude and navigation performance. The process for verifying other requirements such as Time to First Fix, Time to First Attitude, selection/deselection of a specific GPS satellite vehicles (SV), minimum signal strength while still obtaining attitude and navigation, navigation and attitude output coverage, GPS week rollover, and Y2K requirements are also given in this paper.

Simpson, James↗
NASA NTRS1999

Testing of the International Space Station and X-38 Crew Return Vehicle GPS Receiver

This paper discusses the process and results of the performance testing of the GPS receiver planned for use on the International Space Station (ISS) and the X-38 Crew Return Vehicle (CRV). The receiver is a Force-19 unit manufactured by Trimble Navigation and Modified in software by the NASA Goddard Space Flight Center (GSFC) to perform navigation and attitude determination in space. The receiver is the primary source of navigation and attitude information for ISS and CRV. Engineers at GSFC have developed and tested the new receiver with a Global Simulation Systems Ltd (GSS) GPS Signal Generator (GPSSG). This paper documents the unique aspects of ground testing a GPS receiver that is designed for use in space. A discussion of the design and tests using the GPSSG, documentation, data capture, data analysis, and lessons learned will precede an overview of the performance of the new receiver. A description of the challenges of that were overcome during this testing exercise will be presented. Results from testing show that the receiver will be within or near the specifications for ISS attitude and navigation performance. The process for verifying other requirements such as Time to First Fix, Time to First Attitude, selection/deselection of a specific GPS satellite vehicles (SV), minimum signal strength while still obtaining attitude and navigation, navigation and attitude output coverage, GPS week rollover, and Y2K requirements are also given in this paper.

Simpson, James↗
NASA NTRS1999

Testing of the International Space Station and X-38 Crew Return Vehicle GPS Receiver

This paper discusses the process and results of the performance testing of the GPS receiver planned for use on the International Space Station (ISS) and the X-38 Crew Return Vehicle (CRV). The receiver is a Force-19 unit manufactured by Trimble Navigation and modified in software by the NASA Goddard Space Flight Center (GSFC) to perform navigation and attitude determination in space. The receiver is the primary source of navigation and attitude information for ISS and CRV. Engineers at GSFC have developed and tested the new receiver with a Global Simulation Systems Ltd (GSS) GPS Signal Generator (GPSSG). This paper documents the unique aspects of ground testing a GPS receiver that is designed for use in space. A discussion of the design of tests using the GPSSG, documentation, data capture, data analysis, and lessons learned will precede an overview of the performance of the new receiver. A description of the challenges that were overcome during this testing exercise will be presented. Results from testing show that the receiver will be within or near the specifications for ISS attitude and navigation performance. The process for verifying other requirements such as Time to First Fix, Time to First Attitude, selection/deselection of a specific GPS satellite vehicles (SV), minimum signal strength while still obtaining attitude and navigation, navigation and attitude output coverage, GPS week rollover, and Y2K requirements are also given in this paper.

Simpson, James↗
NASA NTRS2004

Science Goal Monitor: Science Goal Driven Automation for NASA Missions

Infusion of automation technologies into NASA s future missions will be essential because of the need to: (1) effectively handle an exponentially increasing volume of scientific data, (2) successfully meet dynamic, opportunistic scientific goals and objectives, and (3) substantially reduce mission operations staff and costs. While much effort has gone into automating routine spacecraft operations to reduce human workload and hence costs, applying intelligent automation to the science side, i.e., science data acquisition, data analysis and reactions to that data analysis in a timely and still scientifically valid manner, has been relatively under-emphasized. In order to introduce science driven automation in missions, we must be able to: capture and interpret the science goals of observing programs, represent those goals in machine interpretable language; and allow spacecrafts onboard systems to autonomously react to the scientist's goals. In short, we must teach our platforms to dynamically understand, recognize, and react to the scientists goals. The Science Goal Monitor (SGM) project at NASA Goddard Space Flight Center is a prototype software tool being developed to determine the best strategies for implementing science goal driven automation in missions. The tools being developed in SGM improve the ability to monitor and react to the changing status of scientific events. The SGM system enables scientists to specify what to look for and how to react in descriptive rather than technical terms. The system monitors streams of science data to identify occurrences of key events previously specified by the scientist. When an event occurs, the system autonomously coordinates the execution of the scientist s desired reactions. Through SGM, we will improve om understanding about the capabilities needed onboard for success, develop metrics to understand the potential increase in science returns, and develop an operational prototype so that the perceived risks associated with increased use of automation can be reduced.

Koratkar, Anuradha↗
NASA NTRS2001

Advances in autonomous systems for space exploration missions

This paper focuses on new and innovative software for remote, autonomous, space systems flight operation, including distributed autonomous systems, flight test results, and implications and directions for future systems.

autonomy core technologies↗
NASA NTRS2001

Information Handling is the Problem

This slide presentation reviews the concerns surrounding the automation of information handling. There are two types of decision support software that supports most Space Station Flight Controllers. one is very simple, and the other is very complex. A middle ground is sought. This is the reason for the Human Centered Autonomous and Assistant Systems Testbed (HCAAST) Project. The aim is to study flight controllers at work, and in the bigger picture, with particular attention to how they handle information and how coordination of multiple teams is performed. The focus of the project is on intelligent assistants to assist in handling information for the flight controllers.

Malin, Jane T.↗
NASA NTRS2016

In-Space Networking on NASA's SCAN Testbed

The NASA Space Communications and Navigation (SCaN) Testbed, an external payload onboard the International Space Station, is equipped with three software defined radios and a flight computer for supporting in-space communication research. New technologies being studied using the SCaN Testbed include advanced networking, coding, and modulation protocols designed to support the transition of NASAs mission systems from primarily point to point data links and preplanned routes towards adaptive, autonomous internetworked operations needed to meet future mission objectives. Networking protocols implemented on the SCaN Testbed include the Advanced Orbiting Systems (AOS) link-layer protocol, Consultative Committee for Space Data Systems (CCSDS) Encapsulation Packets, Internet Protocol (IP), Space Link Extension (SLE), CCSDS File Delivery Protocol (CFDP), and Delay-Tolerant Networking (DTN) protocols including the Bundle Protocol (BP) and Licklider Transmission Protocol (LTP). The SCaN Testbed end-to-end system provides three S-band data links and one Ka-band data link to exchange space and ground data through NASAs Tracking Data Relay Satellite System or a direct-to-ground link to ground stations. The multiple data links and nodes provide several upgradable elements on both the space and ground systems. This paper will provide a general description of the testbeds system design and capabilities, discuss in detail the design and lessons learned in the implementation of the network protocols, and describe future plans for continuing research to meet the communication needs for evolving global space systems.

space networks↗
NASA NTRS2017

Implementation of Real-Time Hardware in the Loop Simulation for WAVE Instrument Avionics

The Regolith and Environment Science and Oxygen and Lunar Volatile Extraction (RESOLVE) payload will lead the Resource Prospector rover to hydrogen-rich locations on the moon supporting NASA's in-situ resource utilization (ISRU) mission. The Water Analysis and Volatile Extraction (WAVE) system will be responsible for heating up regolith samples and analyzing their volatiles in a vaporized state. Given the space environment, testing flight hardware and software using the scientific instruments can be costly and time consuming, which can hold back progress involving the instruments. A hardware-in-the-loop (HITL) simulation will test the Avionics Data Acquisition as well as the Instrument Interface Unit, through simulating sensors and actuators involved in supporting the WAVE instruments. HITL is a platform for testing and developing WAVE's avionics and software, where the simulation plant will imitate the LAVA and OVEN instruments, thus allowing for an accessible, efficient, and replicable testing environment.

Al Qaraghuli, Ali↗
NASA NTRS2018

GOES-16 ABI Navigation Assessment

The US Geostationary Operational Environmental Satellite – R Series (GOES-R) was launched on November 19, 2016and was designated GOES-16 upon reaching geostationary orbit ten days later. After checkout and calibration, GOES-16 was relocated to its operational location of 75.2 degrees west and officially became GOES East on December 18, 2017. The Advanced Baseline Imager (ABI) is the primary instrument on the GOES-R series for imaging Earth's surface and atmosphere to significantly improve the detection and observation of severe environmental phenomena. A team supporting the GOES-R Flight Project at NASA's Goddard Space Flight Center developed algorithms and software for independent verification of ABI Image Navigation and Registration (INR), which became known as the INR Performance Assessment Tool Set (IPATS). In this paper, we will briefly describe IPATS on top concept level, and then introduce the Landsat chips, chip registration algorithms, and how IPATS measurements are filtered. We present GOES-16 navigation (NAV) errors from flight data from January 2017 to May 2018. The results show a) IPATS characterized INR variations throughout the post-launch test phase; and b) ABI INR has improved over time as post-launch tests were performed and corrections applied. Finally, we will describe how estimated NAV errors have been used to assess and understand satellite attitude anomalies and scale errors etc. This paper shows that IPATS is an effective tool for assessing and improving GOES-16 ABI INR and is also useful for INR long-term monitoring.

GOES-R↗
NASA NTRS2021

Trust in Collaborative Automation in High Stakes Software Engineering Work

The amount of autonomy in software engineering tools is increasing as developers build increasingly complex systems. Research in other domains shows that too much or too little trust in autonomous tools can have negative consequences, but we are not aware of any study that has investigated trust in autonomous tools in the highly interactive context of a software engineering workplace. We present the results of a ten week ethnographic case study of engineers collaborating with autonomous tools to write flight software at a large national space exploration organization to support high stakes missions. We find that trust in an autonomous software engineering tool in this setting was influenced by four main factors: the tool’s transparency, social context, an organization’s associated processes, and its usability. We outline theoretical implications for future research into trust in autonomous software engineering tools, and practical implications for tool designers and organizations conducting high stakes work with autonomous tools.

Davidoff, Scott↗
NASA NTRS2008

Closing the Certification Gaps in Adaptive Flight Control Software

Over the last five decades, extensive research has been performed to design and develop adaptive control systems for aerospace systems and other applications where the capability to change controller behavior at different operating conditions is highly desirable. Although adaptive flight control has been partially implemented through the use of gain-scheduled control, truly adaptive control systems using learning algorithms and on-line system identification methods have not seen commercial deployment. The reason is that the certification process for adaptive flight control software for use in national air space has not yet been decided. The purpose of this paper is to examine the gaps between the state-of-the-art methodologies used to certify conventional (i.e., non-adaptive) flight control system software and what will likely to be needed to satisfy FAA airworthiness requirements. These gaps include the lack of a certification plan or process guide, the need to develop verification and validation tools and methodologies to analyze adaptive controller stability and convergence, as well as the development of metrics to evaluate adaptive controller performance at off-nominal flight conditions. This paper presents the major certification gap areas, a description of the current state of the verification methodologies, and what further research efforts will likely be needed to close the gaps remaining in current certification practices. It is envisioned that closing the gap will require certain advances in simulation methods, comprehensive methods to determine learning algorithm stability and convergence rates, the development of performance metrics for adaptive controllers, the application of formal software assurance methods, the application of on-line software monitoring tools for adaptive controller health assessment, and the development of a certification case for adaptive system safety of flight.

Jacklin, Stephen A.↗
NASA NTRS1982

Geographic information systems at the Goddard Space Flight Center

The basic functions of a Geographic Information System (GIS) and the different ways that a GIS may be implemented are described. It surveys that GIS software packages that are currently in operation at the Goddard Space Flight Center and discusses the types of applications for which they are best suited. Future plans for in-house GIS research and development are outlined.

Goldberg, M.↗
NASA NTRS2010

Results from the NASA Spacecraft Fault Management Workshop: Cost Drivers for Deep Space Missions

Fault Management, the detection of and response to in-flight anomalies, is a critical aspect of deep-space missions. Fault management capabilities are commonly distributed across flight and ground subsystems, impacting hardware, software, and mission operations designs. The National Aeronautics and Space Administration (NASA) Discovery & New Frontiers (D&NF) Program Office at Marshall Space Flight Center (MSFC) recently studied cost overruns and schedule delays for five missions. The goal was to identify the underlying causes for the overruns and delays, and to develop practical mitigations to assist the D&NF projects in identifying potential risks and controlling the associated impacts to proposed mission costs and schedules. The study found that four out of the five missions studied had significant overruns due to underestimating the complexity and support requirements for fault management. As a result of this and other recent experiences, the NASA Science Mission Directorate (SMD) Planetary Science Division (PSD) commissioned a workshop to bring together invited participants across government, industry, and academia to assess the state of the art in fault management practice and research, identify current and potential issues, and make recommendations for addressing these issues. The workshop was held in New Orleans in April of 2008. The workshop concluded that fault management is not being limited by technology, but rather by a lack of emphasis and discipline in both the engineering and programmatic dimensions. Some of the areas cited in the findings include different, conflicting, and changing institutional goals and risk postures; unclear ownership of end-to-end fault management engineering; inadequate understanding of the impact of mission-level requirements on fault management complexity; and practices, processes, and tools that have not kept pace with the increasing complexity of mission requirements and spacecraft systems. This paper summarizes the findings and recommendations from that workshop, particularly as fault management development issues affect operations and the development of operations capabilities.

Newhouse, Marilyn E.↗
NASA NTRSDate not supplied

Stochastic Verification by Analysis for Autonomous Systems Management Architecture (ASMA)

The Gateway Vehicle Systems Manager (VSM) is the top-level of a distributed, hierarchical software control system. VSM is data-driven and will make decisions related to mission, fault, resource management and vehicle control. These attributes combined with a high degree of autonomy make it susceptible to emergent behavior. In order to achieve the high level of confidence needed in this critical system, the VSM team has developed a multifaceted verification strategy employing traditional verification techniques, simulation, model checking, and runtime verification. Individual algorithms are verified using conventional testing and model checking using assume-guarantee contracts. A discrete event-based simulation approach is being developed to verify timelines. This presentation describes an enhancement to the verification approach using analysis to enhance system robustness by detecting and resolving the potential for emergent behavior. The verification by analysis employs a Software in the Loop (SITL) environment with real flight software executing on emulated processors, simulations of vehicle subsystems, flight dynamics, and human inputs. Since the possible input space and configuration data set are too large for exhaustive testing, a Monte Carlo approach is used to cover feasible scenarios, augmented with corner cases and known higher-risk scenarios. A key problem in using Monte Carlo-based system verification is evaluating test results to ensure that system behavior is correct. The presentation describes the approach the VSM team uses to monitor behavior for compliance with predetermined boundaries and to identify anomalous behavior for further analysis. This presentation describes the multi-level systems approach to verification, and the simulation-based layer that covers the feasible state space: 1. Overview of the Gateway VSM 2. Special challenges due to heterogeneous, hierarchical architecture 3. Modeling and simulation environment using flight software and system simulations 4. Developing input sets to ensure state-space coverage 5. Developing model and data configuration sets to ensure model coverage 6. Interpreting results without predetermined outcomes 7. Lessons learned and future work

Verification and Validation↗