Engineering topics
Johnson, Stephen
Publications and source records attributed to Johnson, Stephen.
A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk
No abstract available
A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASA's Space Launch System
The engineering development of the new Space Launch System (SLS) launch vehicle requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The characteristics of these spacecraft systems must be matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex system engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in specialized Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model based algorithms and their development lifecycle from inception through Flight Software certification are an important focus of this development effort to further insure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. NASA formed a dedicated M&FM team for addressing fault management early in the development lifecycle for the SLS initiative. As part of the development of the M&FM capabilities, this team has developed a dedicated testbed that integrates specific M&FM algorithms, specialized nominal and off-nominal test cases, and vendor-supplied physics-based launch vehicle subsystem models. Additionally, the team has developed processes for implementing and validating these algorithms for concept validation and risk reduction for the SLS program. The flexibility of the Vehicle Management End-to-end Testbed (VMET) enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS. The intent of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software development infrastructure and its related testing entities. In any software development process there is inherent risk in the interpretation and implementation of concepts into software through requirements and test cases into flight software compounded with potential human errors throughout the development lifecycle. Risk reduction is addressed by the M&FM analysis group working with other organizations such as S&MA, Structures and Environments, GNC, Orion, the Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission and Loss of Crew probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses that can be tested in VMET to ensure that failures can be detected, and confirm that responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - ARINC 653 partitioned OS, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by Flight Software. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure the effectiveness of M&FM algorithms performance in the FSW development and test processes.
The Development of NASA's Fault Management Handbook
NASA is developing a FM Handbook to establish guidelines and to provide recommendations for defining, developing, analyzing, evaluating, testing, and operating FM systems. It establishes a process for developing FM throughout the lifecycle of a mission and provides a basis for moving the field toward a formal and consistent FM methodology to be applied on future programs. This paper describes the motivation for, the development of, and the future plans for the NASA FM Handbook.
The Development of NASA's Fault Management Handbook
Goal: (1) Ameliorate schedule, cost and predictability challenges that often are faced when testing and operating FM systems (2) Improve reliability and safety of NASA s flight and ground systems (3) Coalesce the FM field. Approach: (1) Identify qualified team of FM practitioners and systems engineers (2) Evaluate findings and recommendations from 2008 FM Workshop (3) Initial emphasis on foundational issues; e.g. establish common terminology (1) Capitalize on existing material
Automatic Relative Debugging of OpenMP Programs
In this work we show how automatic relative debugging can be used to find differences in computation between a serial program and an OpenMP parallel version of that program. Backtracking and re-execution are used to determine the first OpenMP parallel region that produces a difference in computation that may lead to an incorrect value the user has indicated. Tool-parallelized programs are addressed by utilizing static analysis and directive information from the parallelization tool. Manually-parallelized programs are addressed as well by performing data dependence and directive analysis.
Backtracking and Re-execution in the Automatic Debugging of Parallelized Programs
In this work we describe a new approach using relative debugging to find differences in computation between a serial program and a parallel version of th it program. We use a combination of re-execution and backtracking in order to find the first difference in computation that may ultimately lead to an incorrect value that the user has indicated. In our prototype implementation we use static analysis information from a parallelization tool in order to perform the backtracking as well as the mapping required between serial and parallel computations.
Advanced Solar-propelled Cargo Spacecraft for Mars Missions
Three concepts for an unmanned, solar powered, cargo spacecraft for Mars support missions were investigated. These spacecraft are designed to carry a 50,000 kg payload from a low Earth orbit to a low Mars orbit. Each design uses a distinctly different propulsion system: A Solar Radiation Absorption (SRA) system, a Solar-Pumped Laser (SPL) system and a solar powered magnetoplasmadynamic (MPD) arc system. The SRA directly converts solar energy to thermal energy in the propellant through a novel process. In the SPL system, a pair of solar-pumped, multi-megawatt, CO2 lasers in sunsynchronous Earth orbit converts solar energy to laser energy. The MPD system used indium phosphide solar cells to convert sunlight to electricity, which powers the propulsion system. Various orbital transfer options are examined for these concepts. In the SRA system, the mother ship transfers the payload into a very high Earth orbit and a small auxiliary propulsion system boosts the payload into a Hohmann transfer to Mars. The SPL spacecraft and the SPL powered spacecraft return to Earth for subsequent missions. The MPD propelled spacecraft, however, remains at Mars as an orbiting space station. A patched conic approximation was used to determine a heliocentric interplanetary transfer orbit for the MPD propelled spacecraft. All three solar-powered spacecraft use an aerobrake procedure to place the payload into a low Mars parking orbit. The payload delivery times range from 160 days to 873 days (2.39 years).