Search NASA⌕ Search

SEARCH · Search NASA

Results for “program architectures”

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 721 records · Page 40

Using an architectural approach to integrate heterogeneous, distributed software components

Many computer programs cannot be easily integrated because their components are distributed and heterogeneous, i.e., they are implemented in diverse programming languages, use different data representation formats, or their runtime environments are incompatible. In many cases, programs are integrated by modifying their components or interposing mechanisms that handle communication and conversion tasks. For example, remote procedure call (RPC) helps integrate heterogeneous, distributed programs. When configuring such programs, however, mechanisms like RPC must be used explicitly by software developers in order to integrate collections of diverse components. Each collection may require a unique integration solution. This paper describes improvements to the concepts of software packaging and some of our experiences in constructing complex software systems from a wide variety of components in different execution environments. Software packaging is a process that automatically determines how to integrate a diverse collection of computer programs based on the types of components involved and the capabilities of available translators and adapters in an environment. Software packaging provides a context that relates such mechanisms to software integration processes and reduces the cost of configuring applications whose components are distributed or implemented in different programming languages. Our software packaging tool subsumes traditional integration tools like UNIX make by providing a rule-based approach to software integration that is independent of execution environments.

Callahan, John R.↗

The OpenMP Implementation of NAS Parallel Benchmarks and its Performance

As the new ccNUMA architecture became popular in recent years, parallel programming with compiler directives on these machines has evolved to accommodate new needs. In this study, we examine the effectiveness of OpenMP directives for parallelizing the NAS Parallel Benchmarks. Implementation details will be discussed and performance will be compared with the MPI implementation. We have demonstrated that OpenMP can achieve very good results for parallelization on a shared memory system, but effective use of memory and cache is very important.

Jin, Hao-Qiang↗

Paramedir: A Tool for Programmable Performance Analysis

Performance analysis of parallel scientific applications is time consuming and requires great expertise in areas such as programming paradigms, system software, and computer hardware architectures. In this paper we describe a tool that facilitates the programmability of performance metric calculations thereby allowing the automation of the analysis and reducing the application development time. We demonstrate how the system can be used to capture knowledge and intuition acquired by advanced parallel programmers in order to be transferred to novice users.

Jost, Gabriele↗

Robot Swarms

Engineers and interns at this NASA field center are building the prototype of a robotic rover that could go where no wheeled rover has gone before-into the dark cold craters at the lunar poles and across the Moon s rugged highlands-like a walking tetrahedron. With NASA pushing to meet President Bush's new exploration objectives, the robots taking shape here today could be on the Moon in a decade. In the longer term, the concept could lead to shape-shifting robot swarms designed to explore distant planetary surfaces in advance of humans. "If you look at all of NASA s projections of the future, anyone s projections of the space program, they re all rigid-body architecture," says Steven Curtis, principal investigator on the effort. "This is not rigid-body. The whole key here is flexibility and reconfigurability with a capital R."

Morring, Frank, Jr.↗

Life Support Systems for Lunar Landers

Engineers designing life support systems for NASA s next Lunar Landers face unique challenges. As with any vehicle that enables human spaceflight, the needs of the crew drive most of the lander requirements. The lander is also a key element of the architecture NASA will implement in the Constellation program. Many requirements, constraints, or optimization goals will be driven by interfaces with other projects, like the Crew Exploration Vehicle, the Lunar Surface Systems, and the Extravehicular Activity project. Other challenges in the life support system will be driven by the unique location of the vehicle in the environments encountered throughout the mission. This paper examines several topics that may be major design drivers for the lunar lander life support system. There are several functional requirements for the lander that may be different from previous vehicles or programs and recent experience. Some of the requirements or design drivers will change depending on the overall Lander configuration. While the configuration for a lander design is not fixed, designers can examine how these issues would impact their design and be prepared for the quick design iterations required to optimize a spacecraft.

Anderson, Molly↗

Parametric Analysis of Life Support Systems for Future Space Exploration Missions

Having adopted a flexible path approach to space exploration, the National Aeronautics and Space Administration is in a process of evaluating future targets for space exploration. In order to maintain the welfare of a crew during future missions, a suite of life support technology is responsible for oxygen and water generation, carbon dioxide control, the removal of trace concentrations of organic contaminants, processing and recovery of water, and the storage and reclamation of solid waste. For each particular life support subsystem, a variety competing technologies either exist or are under aggressive development efforts. Each individual technology has strengths and weaknesses with regard to launch mass, power and cooling requirements, volume of hardware and consumables, and crew time requirements for operation. However, from a system level perspective, the favorability of each life support architecture is better assessed when the sub-system technologies are analyzed in aggregate. In order to evaluate each specific life support system architecture, the measure of equivalent system mass (ESM) was employed to benchmark system favorability. Moreover, the results discussed herein will be from the context of loop-closure with respect to the air, water, and waste sub-systems. Specifically, closure relates to the amount of consumables mass that crosses the boundary of the vehicle over the lifetime of a mission. As will be demonstrated in this manuscript, the optimal level of loop closure is heavily dependent upon mission requirements such as duration and the level of extra- vehicular activity (EVA) performed. Sub-system level trades were also considered as a function of mission duration to assess when increased loop closure is practical. Although many additional factors will likely merit consideration in designing life support systems for future missions, the ESM results described herein provide a context for future architecture design decisions toward a flexible path program.

Swickrath, Michael J.↗

Parametric Analysis of Life Support Systems for Future Space Exploration Missions

The National Aeronautics and Space Administration is in a process of evaluating future targets for space exploration. In order to maintain the welfare of a crew during future missions, a suite of life support technology is responsible for oxygen and water generation, carbon dioxide control, the removal of trace concentrations of organic contaminants, processing and recovery of water, and the storage and reclamation of solid waste. For each particular life support subsystem, a variety competing technologies either exist or are under aggressive development efforts. Each individual technology has strengths and weaknesses with regard to launch mass, power and cooling requirements, volume of hardware and consumables, and crew time requirements for operation. However, from a system level perspective, the favorability of each life support architecture is better assessed when the sub-system technologies are analyzed in aggregate. In order to evaluate each specific life support system architecture, the measure of equivalent system mass (ESM) was employed to benchmark system favorability. Moreover, the results discussed herein will be from the context of loop-closure with respect to the air, water, and waste sub-systems. Specifically, closure relates to the amount of consumables mass that crosses the boundary of the vehicle over the lifetime of a mission. As will be demonstrated in this manuscript, the optimal level of loop closure is heavily dependent upon mission requirements such as duration and the level of extra-vehicular activity (EVA) performed. Sub-system level trades were also considered as a function of mission duration to assess when increased loop closure is practical. Although many additional factors will likely merit consideration in designing life support systems for future missions, the ESM results described herein provide a context for future architecture design decisions toward a flexible path program.

Swickrath, Michael J.↗

Putting the Power of Configuration in the Hands of the Users

Goal was to reduce the overall cost of human space flight while maintaining the most demanding standards for safety and mission success. In support of this goal, a project team was chartered to replace 18 legacy Space Shuttle nonconformance processes and systems with one fully integrated system Problem Reporting and Corrective Action (PRACA) processes provide a closed-loop system for the identification, disposition, resolution, closure, and reporting of all Space Shuttle hardware/software problems PRACA processes are integrated throughout the Space Shuttle organizational processes and are critical to assuring a safe and successful program Primary Project Objectives Develop a fully integrated system that provides an automated workflow with electronic signatures Support multiple NASA programs and contracts with a single "system" architecture Define standard processes, implement best practices, and minimize process variations

Al-Shihabi, Mary-Jo↗

Galaxy Evolution Spectroscopic Explorer (GESE): Science Rationale, Optical Design, and Telescope Architecture

One of the key goals of NASA’s astrophysics program is to answer the question: How did galaxies evolve into the spiral, elliptical, and irregular galaxies that we see today? We describe a space mission concept called Galaxy Evolution Spectroscopic Explorer (GESE) to help address this question by making a large ultraviolet spectroscopic survey of galaxies at a redshift, z approximately 1 (look-back time of approximately 8 billion years). GESE is a 1.5-m space telescope with an near-ultraviolet (NUV) multi-object slit spectrograph covering the spectral range, 0.2-0.4 micrometers (0.1-0.2 micrometers as emitted by galaxies at a redshift, z approximately 1) at a spectral resolution of delta lambda=6 A.

elliptical↗

Space Launch System Liftoff and Separation Dynamics Analysis Tool Chain

A flexible, hierarchical tool chain that is being applied to NASA’s Space Launch System (SLS) for critical dynamics phenomena is described. This tool chain, called CLVTOPS, is used to investigate lateral liftoff movement of the vehicle as it departs and clears the mobile launch tower and separation of the two solid rocket boosters without collision with the core stage and payload. The toolset’s architecture was configured to take advantage of a modern software-engineering approach for maximum flexibility and utilization of open-source simulations and associated tools. As opposed to a “monolithic” approach, scripting languages were used to “bind” together a tool chain to configure and organize input data, execute and produce analysis results, and post-process these results to facilitate a rapid iterative analysis process to quickly address issues and pursue alternatives with emphasis on analysis automation. Key capabilities in the tool chain include processing and mining of very large data sets, a wide range of graphical depictions, and high-fidelity, physics-based simulations. The paper begins with a problem description and the motivation for liftoff and separation dynamics analysis followed by a historical survey of dynamics analyses for previous NASA human-rated launch vehicles. Details of the tool chain and its components are then introduced divided, first, into description of the scripting language architecture used to “bind” the simulation tools, programs, and scripts together and, second, the physics models and simulations. Representative analyses and data products are shown for liftoff and booster separation dynamics that provide in-depth insight to the tool chain’s capabilities. Supporting activities such as simulation tool chain verification, version archiving and data management, and training are addressed. The paper concludes with case examples on how the tool chain can be tailored to related aerospace dynamics analyses, both large and small. These patterns and techniques for SLS dynamics tool construction can be applied for other aerospace simulations.

6DOF↗

Space Launch System Liftoff and Separation Dynamics Analysis Tool Chain

A flexible, hierarchical tool chain that is being applied to NASA’s Space Launch System (SLS) for critical dynamics phenomena is described. This tool chain, called CLVTOPS, is used to investigate lateral liftoff movement of the vehicle as it departs and clears the mobile launch tower and separation of the two solid rocket boosters without collision with the core stage and payload. The toolset’s architecture was configured to take advantage of a modern software engineering approach for maximum flexibility and utilization of open-source simulations and associated tools. As opposed to a “monolithic” approach, scripting languages were used to “bind” together a tool chain to configure and organize input data, execute and produce analysis results, and post-process these results to facilitate a rapid, iterative analysis process to quickly address issues and pursue alternatives with emphasis on analysis automation. Key capabilities in the tool chain include processing and mining of very large data sets, a wide range of graphical depictions, and high-fidelity, physics-based simulations. The paper begins with a problem description and the motivation for liftoff and separation dynamics analysis followed by a historical survey of dynamics analyses for previous NASA human-rated launch vehicles. Details of the tool chain and its components are then introduced and divided, first, into description of the scripting language architecture used to “bind” the simulation tools, programs, and scripts together and, second, the physics models and simulations. Representative analyses and data products for liftoff and booster separation dynamics are shown in order to provide in-depth insight into the tool chain’s capabilities. Supporting activities such as simulation tool chain verification, version archiving and data management, and training are addressed. The paper concludes with case examples on how the tool chain can be tailored to related aerospace dynamics analyses, both large and small. The flexibility and versatility of this tool chain in supporting analyses of such a diverse range of aerospace applications demonstrates the feasibility of applying these patterns and techniques for tool construction to other aerospace simulations.

6DOF↗

NASA Class A Certification of Core Flight Software (cFS)

NASA Gateway program has named cFS as the software architecture for the vehicle. The core CFS team (GSFC+JSC) is tasked to develop a certifiable release of the cFS bundle, by components, as class A, safety-critical flight software. It is to be available to all Gateway software developers, including our element vendors and international partners. Its availability & usage will be as stated by the Gateway User Agreement license. In this presentation, we will describe our general certification process, and more importantly, our certification artifacts that can be re-run to certify cFS on different platforms. Our goal is to also make available these certifiable packages to the open source community, specifically for cFE, OSAL and certain cFS applications and libraries that are currently hosted on NASA github (https://github.com/nasa).

Tam M Ngo↗

NASA Class A Certification of Core Flight Software (cFS)

NASA Gateway program has named cFS as the software architecture for the vehicle. The core CFS team (GSFC+JSC) is tasked to develop a certifiable release of the cFS bundle, by components, as class A, safety-critical flight software. It is to be available to all Gateway software developers, including our element vendors and international partners. Its availability & usage will be as stated by the Gateway User Agreement license. In this presentation, we will describe our general certification process, and more importantly, our certification artifacts that can be re-run to certify cFS on different platforms. Our goal is to also make available these certifiable packages to the open source community, specifically for cFE, OSAL and certain cFS applications and libraries that are currently hosted on NASA github (https://github.com/nasa).

Tam M Ngo↗

Demonstration of a Modular, Scalable, Laser Communication Terminal for Manned Spaceflight Missions

Free-space laser communication systems are increasingly implemented on state of the art satellites for their high-speed connectivity. This work outlines the design, analysis and test of the Modular, Agile, Scalable Optical Terminal (MAScOT) we have developed to support Low-Earth Orbit (LEO) to deep-space communication links. In LEO, the MAScOT will be implemented on the International Space Station to support the Integrated Laser Communications Relay Demonstration (LCRD) LEO User Modem and Amplifier Terminal (ILLUMA-T) program. ILLUMA-T’s overarching objective is to demonstrate high bandwidth data transfer between LEO and a ground station via a geosynchronous (GEO) relay satellite. Outside of GEO, MAScOT will also be implemented on the Artemis-II mission to demonstrate high data rate optical communications to and from the moon as part of the Orion EM-2 Optical Communications (O2O) program. Both missions leverage the same modular architecture despite varying structural, thermal, and optical requirements. To achieve sufficient performance, the optical terminal relies on a coarse/fine nested tracking loop to realize sub-arcsecond pointing across +/- 120 deg elevation and +/- 175 deg azimuth field of regard. An integrated analysis of the MAScOT in support of both missions will be outlined in addition to scalable versions of this terminal for future missions.

Steven R. Gillmer↗

Demonstration of a Modular, Scalable, Laser Communication Terminal for Manned Spaceflight Missions

Free-space laser communication systems are increasingly implemented on state of the art satellites for their high-speed connectivity. This work outlines a demonstration of the Modular, Agile, Scalable Optical Terminal(MAScOT) we have developed to support Low-Earth Orbit (LEO) to deep-space communication links. In LEO, the MAScOT will be implemented on the International Space Station to support the Integrated Laser Communications Relay Demonstration (LCRD) LEO User Modem and Amplifier Terminal (ILLUMA-T) program. ILLUMA-Ts overarching objective is to demonstrate high bandwidth data transfer between LEO and a ground station via a geosynchronous (GEO) relay satellite. Outside of GEO, MAScOT will also be implemented on the Artemis-II mission to demonstrate high data rate optical communications to and from the moon as part of theOrion EM-2 Optical Communications (O2O) program. Both missions leverage the same modular architecture despite varying structural, thermal, and optical requirements. To achieve sufficient performance, the optical terminal relies on a nested tracking loop to realize sub-arcsecond pointing across±120◦elevation and±175◦azimuth field of regard.

optical communications↗

Evaluating Liftoff Debris for NASA’s Space Launch System (SLS) Prior to the Artemis I Launch

The SLS Artemis I launch vehicle is the first of several planned Artemis launch vehicles, with a number of design differences from earlier NASA missions that incur liftoff debris risk to the mission. As a test vehicle, the Artemis I hardware also endured environments and tests not planned for future missions, which led to several additional factors contributing to an evolving liftoff debris risk to the SLS vehicle. This paper will summarize these risk factors and address the processes used to evaluate and communicate the risks to support a successful Artemis I launch. It will discuss how the evolving risks that were quantified and evaluated by a Cross-Program team of debris Subject Matter Experts to mitigate liftoff debris hazards and communicate updated risk to the SLS vehicle. This process was performed through the inaugural use of an SLS debris day-of-launch (DOL) standard operating procedure that will be used for subsequent Artemis missions. This paper addresses the risk of liftoff debris, debris released by the vehicle or from the launch pad during liftoff through vehicle tower clear. Expected liftoff debris is well understood from previous NASA programs’ experience and from tests of materials, processes and functions that are known to release liftoff debris. These expected sources were assessed and cleared well ahead of launch day. However, given the ever-changing schedules and environments, processes were in place to evaluate any additional potential liftoff debris risks identified during launch countdown. Although many of the Artemis vehicle hardware components are similar to those on the NASA Shuttle Program, there are important differences in the architecture of the Artemis I vehicle which require new assessments of liftoff debris risk for the Artemis missions. The more favorable Artemis crew module location and surfaces are far less vulnerable to debris impacts; however, the longer vehicle can result in higher liftoff debris impact energies to those components on the aft end of the vehicle. Additionally, the positional change of the RS-25 liquid engines to nearer the Booster nozzle exit plane along with the change in Booster throat plug design is a disadvantage to the overall liftoff debris risk which resulted in additional test and analysis efforts for evaluating the integrated vehicle debris risk. In spite of the comprehensive tests and analyses of Artemis I expected liftoff debris, a number of additional tests/processes were completed prior to the Artemis I mission that were required to support a complete understanding of a new launch vehicle, but increased the risk of releasing liftoff debris. The hardware endured several additional cryogenic loading cycles, including the Green Run tests at Stennis Space Center, Wet Dress Rehearsals at Kennedy Space Center, and multiple launch attempts. Each of these cycles induced stresses in the thermal protection system (TPS) materials, increasing the risk of damage to and release of the TPS. Additionally, induced and weather environmental factors that could increase the likelihood of debris release were significant. Vibrations and stresses in the TPS were induced by a required roll-back to the Vehicle Assembly Building before Hurricane Ian to protect the vehicle from damage by high winds. Wind damage and potential internal stresses to several outer mold line materials on the integrated SLS vehicle and mobile launcher were caused by weathering Hurricane Nicole at Pad 39B the week before launch. A thorough imagery scan of the vehicle was performed after each event and the damage observed was repaired, removed, or assessed and the risk to the mission evaluated. Mitigation of debris risk can occur by tests and analyses to show debris impacted components as damage tolerant, by new/improved processes for prevention of debris availability, or redesign. Risk mitigation processes for Artemis I-specific liftoff debris events and the development and use of the SLS debris day of launch (DOL) procedures that will be used for subsequent Artemis missions will be described.

Space Launch System↗

Evaluating Liftoff Debris for NASA’s Space Launch System (SLS) Prior to the Artemis I Launch

The SLS Artemis I launch vehicle is the first of several planned Artemis launch vehicles, with a number of design differences from earlier NASA missions that incur liftoff debris risk to the mission. As a test vehicle, the Artemis I hardware also endured environments and tests not planned for future missions, which led to several additional factors contributing to an evolving liftoff debris risk to the SLS vehicle. This paper will summarize these risk factors and address the processes used to evaluate and communicate the risks to support a successful Artemis I launch. It will discuss how the evolving risks that were quantified and evaluated by a Cross-Program team of debris Subject Matter Experts to mitigate liftoff debris hazards and communicate updated risk to the SLS vehicle. This process was performed through the inaugural use of an SLS debris day-of-launch (DOL) standard operating procedure that will be used for subsequent Artemis missions. This paper addresses the risk of liftoff debris, debris released by the vehicle or from the launch pad during liftoff through vehicle tower clear. Expected liftoff debris is well understood from previous NASA programs’ experience and from tests of materials, processes and functions that are known to release liftoff debris. These expected sources were assessed and cleared well ahead of launch day. However, given the ever-changing schedules and environments, processes were in place to evaluate any additional potential liftoff debris risks identified during launch countdown. Although many of the Artemis vehicle hardware components are similar to those on the NASA Shuttle Program, there are important differences in the architecture of the Artemis I vehicle which require new assessments of liftoff debris risk for the Artemis missions. The more favorable Artemis crew module location and surfaces are far less vulnerable to debris impacts; however, the longer vehicle can result in higher liftoff debris impact energies to those components on the aft end of the vehicle. Additionally, the positional change of the RS-25 liquid engines to nearer the Booster nozzle exit plane along with the change in Booster throat plug design is a disadvantage to the overall liftoff debris risk which resulted in additional test and analysis efforts for evaluating the integrated vehicle debris risk. In spite of the comprehensive tests and analyses of Artemis I expected liftoff debris, a number of additional tests/processes were completed prior to the Artemis I mission that were required to support a complete understanding of a new launch vehicle, but increased the risk of releasing liftoff debris. The hardware endured several additional cryogenic loading cycles, including the Green Run tests at Stennis Space Center, Wet Dress Rehearsals at Kennedy Space Center, and multiple launch attempts. Each of these cycles induced stresses in the thermal protection system (TPS) materials, increasing the risk of damage to and release of the TPS. Additionally, induced and weather environmental factors that could increase the likelihood of debris release were significant. Vibrations and stresses in the TPS were induced by a required roll-back to the Vehicle Assembly Building before Hurricane Ian to protect the vehicle from damage by high winds. Wind damage and potential internal stresses to several outer mold line materials on the integrated SLS vehicle and mobile launcher were caused by weathering Hurricane Nicole at Pad 39B the week before launch. A thorough imagery scan of the vehicle was performed after each event and the damage observed was repaired, removed, or assessed and the risk to the mission evaluated. Mitigation of debris risk can occur by tests and analyses to show debris impacted components as damage tolerant, by new/improved processes for prevention of debris availability, or redesign. Risk mitigation processes for Artemis I-specific liftoff debris events and the development and use of the SLS debris day of launch (DOL) procedures that will be used for subsequent Artemis missions will be described.

Space Launch System↗

Software Systems for High-performance Quantum Computing

Quantum computing promises new opportunities for solving hard computational problems, but harnessing this novelty requires breakthrough concepts in the design, operation, and application of computing systems. We define some of the challenges facing the development of quantum computing systems as well as software-based approaches that can be used to overcome these challenges. Following a brief overview of the state of the art, we present models for the quantum programming and execution models, the development of architectures for hybrid high-performance computing systems, and the realization of software stacks for quantum networking. This leads to a discussion of the role that conventional computing plays in the quantum paradigm and how some of the current challenges for exascale computing overlap with those facing quantum computing.

high-performance computing↗