Empirical analysis of safety - critical software anomalies post-launch
Explore the source record for details and available documents.
anomalies post-launch software safety↗
SEARCH · Search NASA
Results for “post-launch anomaly analysis”
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.
Analyzing post-launch anomalies at JPL
Explore the source record for details and available documents.
post-launch anomaly analysis↗
JPL Test Effectiveness Analysis
1) The pilot study provided meaningful conclusions that are generally consistent with the earlier Test Effectiveness work done between 1992 and 1994: a) Analysis of pre-launch problem/failure reports is consistent with earlier work. b) Analysis of post-launch early mission anomaly reports indicates that there are more software issues in newer missions, and the no-test category for identification of post-launch failures is more significant than in the earlier analysis. 2) Future work includes understanding how differences in Missions effect these analyses: a) There are large variations in the number of problem reports and issues that are documented by the different Projects/Missions. b) Some missions do not have any reported environmental test anomalies, even though environmental tests were performed. 3) Each project/mission has different standards and conventions for filling out the PFR forms, the industry may wish to address this issue: a) Existing problem reporting forms are to document and track problems, failures, and issues (etc.) for the projects, to ensure high quality. b) Existing problem reporting forms are not intended for data mining.
failure cause↗
Analysis of Phoenix Anomalies and IV & V Findings Applied to the GRAIL Mission
NASA IV&V was established in 1993 to improve safety and cost-effectiveness of mission critical software. Since its inception the tools and strategies employed by IV&V have evolved. This paper examines how lessons learned from the Phoenix project were developed and applied to the GRAIL project. Shortly after selection, the GRAIL project initiated a review of the issues documented by IV&V for Phoenix. The motivation was twofold: the learn as much as possible about the types of issues that arose from the flight software product line slated for use on GRAIL, and to identify opportunities for improving the effectiveness of IV&V on GRAIL. The IV&V Facility provided a database dump containing 893 issues. These were categorized into 16 bins, and then analyzed according to whether the project responded by changing the affected artifacts or using as-is. The results of this analysis were compared to a similar assessment of post-launch anomalies documented by the project. Results of the analysis were discussed with the IV&V team assigned to GRAIL. These discussions led to changes in the way both the project and IV&V approached the IV&V task, and improved the efficiency of the activity.
Larson, Steve↗
Analysis of Phoenix Anomalies and IV and V Findings Applied to the GRAIL Mission
Analysis of patterns in IV&V findings and their correlation with post-launch anomalies allowed GRAIL to make more efficient use of IV&V services . Fewer issues. . Higher fix rate. . Better communication. . Increased volume of potential issues vetted, at lower cost. . Hard to make predictions of post-launch performance based on IV&V findings . Phoenix made sound fix/use as-is decisions . Things that were fixed eliminated some problems, but hard to quantify. . Broad predictive success in one area, but inverse relationship in others.
Gravity Recovery and Interior Laboratory (GRAIL)↗
Understanding and Resolution of the Block 2 SSME, STS-104 Engine Shutdown Pressure Surge In-flight Anomaly
STS-104, launched July 2001, marked the first flight of a single Block 2 Space Shuttle Main Engine (SSME). This new configuration of the SSME is the culmination of well over a decade of gradual engine system upgrades. The launch and mission were a success. However, in the process of post-launch data analysis a Main Propulsion System (MPS) anomaly was noted and tied directly to the shutdown of the Block 2 SSME. An investigation into this anomaly was organized across NASA facilities and across the various hardware component contractors. This paper is a very brief summary of the eventual understanding of the root causes of the anomaly and the process whereby an appropriate mitigation action was proposed. An analytical model of the High Pressure Fuel Pump (HPFP) and the low pressure fuel system of the SSME is presented to facilitate the presentation of this summary. The proposed mitigation action is discussed and, with the launch of STS-108 in November 2001, successfully demonstrated under flight conditions.
Greene, William D.↗
Formalized pilot study of safety-critical software anomalies: final report
This report describes both the research techniques and the application results from the analysis of safety-critical software anomalies recorded post-launch on seven spacecraft: Galileo, Mars Global Surveyor, Cassini/Huygens, Deep Space 1, Mars Climate Orbiter, Mars Polar Lander, and Stardust.
software anomalies pilot study software safety↗
3D GeoWall Analysis System for Shuttle External Tank Foreign Object Debris Events
An analytical, advanced imaging method has been developed for the initial monitoring and identification of foam debris and similar anomalies that occur post-launch in reference to the space shuttle s external tank (ET). Remote sensing technologies have been used to perform image enhancement and analysis on high-resolution, true-color images collected with the DCS 760 Kodak digital camera located in the right umbilical well of the space shuttle. Improvements to the camera, using filters, have added sharpness/definition to the image sets; however, image review/analysis of the ET has been limited by the fact that the images acquired by umbilical cameras during launch are two-dimensional, and are usually nonreferenceable between frames due to rotation translation of the ET as it falls away from the space shuttle. Use of stereo pairs of these images can enable strong visual indicators that can immediately portray depth perception of damaged areas or movement of fragments between frames is not perceivable in two-dimensional images. A stereoscopic image visualization system has been developed to allow 3D depth perception of stereo-aligned image pairs taken from in-flight umbilical and handheld digital shuttle cameras. This new system has been developed to augment and optimize existing 2D monitoring capabilities. Using this system, candidate sequential image pairs are identified for transformation into stereo viewing pairs. Image orientation is corrected using control points (similar points) between frames to place the two images in proper X-Y viewing perspective. The images are then imported into the WallView stereo viewing software package. The collected control points are used to generate a transformation equation that is used to re-project one image and effectively co-register it to the other image. The co-registered, oriented image pairs are imported into a WallView image set and are used as a 3D stereo analysis slide show. Multiple sequential image pairs can be used to allow forensic review of temporal phenomena between pairs. The observer, while wearing linear polarized glasses, is able to review image pairs in passive 3D stereo.
Brown, Richard↗
Reliability inputs to Mariner 9 data explosion
This paper describes the prelaunch and post-launch reliability functions which contributed to the success of the Mariner 9 spacecraft. Examples are included to illustrate how each reliability activity was a vital part of each phase of the project. Prelaunch reliability functions included: (1) establishing, negotiating, and monitoring system and subsystem requirements, (2) participating in spacecraft system and subsystem design/hardware reviews, (3) monitoring preparation of failure mode effects and criticality analyses (FMECA), (4) establishing and managing a problem failure reporting (PFR) system for the spacecraft and its support equipment, (5) monitoring electronic parts activities, and (6) participating in spacecraft reviews. Particular emphasis is placed on mission operations reliability assurance activities, which included: (1) spacecraft problem/failure reporting, (2) managing an integrating failure reporting system which covered all mission operations activities, (3) real-time analysis of spacecraft anomalies, and (4) risk assessment.
Macgregor, D. S.↗
Topic Modeling of NASA Space System Problem Reports: Research in Practice
Problem reports at NASA are similar to bug reports: they capture defects found during test, post-launch operational anomalies, and document the investigation and corrective action of the issue. These artifacts are a rich source of lessons learned for NASA, but are expensive to analyze since problem reports are comprised primarily of natural language text. We apply topic modeling to a corpus of NASA problem reports to extract trends in testing and operational failures. We collected 16,669 problem reports from six NASA space flight missions and applied Latent Dirichlet Allocation topic modeling to the document corpus. We analyze the most popular topics within and across missions, and how popular topics changed over the lifetime of a mission. We find that hardware material and flight software issues are common during the integration and testing phase, while ground station software and equipment issues are more common during the operations phase. We identify a number of challenges in topic modeling for trend analysis: 1) that the process of selecting the topic modeling parameters lacks definitive guidance, 2) defining semantically-meaningful topic labels requires nontrivial effort and domain expertise, 3) topic models derived from the combined corpus of the six missions were biased toward the larger missions, and 4) topics must be semantically distinct as well as cohesive to be useful. Nonetheless,topic modeling can identify problem themes within missions and across mission lifetimes, providing useful feedback to engineers and project managers.
Data Mining↗
Scientific and technical support for the Galileo net flux radiometer experiment
This report describes work supported by a post-launch grant (NCC 2-679) that originally covered the period from 1 January 1990 through 31 December 1992. This was extended an additional nine months at no cost until 30 September 1993, and once more until to 30 November 93. A final report on the effort from 1 January 1990 through 30 November 1993 (anticipated) is provided following the background discussion. Tasks required during the post launch period are briefly as follows: (1) attend PSG (Project Science Group) meetings; (2) support in-flight checkouts; maintain and keep safe the spare instrument and GSE (Ground Support Equipment); (3) organize and maintain documentation; (4) finish calibration measurements, documentation, and analysis; (5) characterize and diagnose instrument anomalies; (6) develop descent data analysis tools; and (7) science data analysis and publication. The following sections provide background information on the NFR instrument followed by the complete progress report.
Sromovsky, Lawrence A.↗