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 523 records · Page 29

Injury Potential Testing of Suited Occupants During Dynamic Spacecraft Flight Phases

In support of the NASA Constellation Program, a space-suit architecture was envisioned for support of Launch, Entry, Abort, Micro-g EVA, Post Landing crew operations, and under emergency conditions, survival. This space suit architecture is unique in comparison to previous launch, entry, and abort (LEA) suit architectures in that it utilized rigid mobility elements in the scye and the upper arm regions. The suit architecture also employed rigid thigh disconnect elements to allow for quick disconnect functionality above the knee which allowed for commonality of the lower portion of the suit across two suit configurations. This suit architecture was designed to interface with the Orion seat subsystem, which includes seat components, lateral supports, and restraints. Due to this unique configuration of spacesuit mobility elements, combined with the need to provide occupant protection during dynamic landing events, risks were identified with potential injury due to the suit characteristics described above. To address the risk concerns, a test series was developed to evaluate the likelihood and consequences of these potential issues. Testing included use of Anthropomorphic Test Devices (ATDs), Post Mortem Human Subjects (PMHS), and representative seat/suit hardware in combination with high linear acceleration events. The ensuing treatment focuses on detailed results of the testing that has been conducted under this test series thus far.

McFarland, Shane M.↗

Extravehicular Activity Framework for Exploration - 2019

The Extravehicular Activity (EVA) Framework for Exploration describes NASA's EVASystem Goals in the broader context of ongoing human spaceflight efforts. The purpose of thisdocument is to drive integration, coordination and communication of the EVA community'sexploration development plans as crafted to meet long-term EVA needs. Inclusive in the EVAcommunity are NASA partners in academia and industry. The 2019 EVA Framework outlinesthe office's current method to answer the following questions: What product does NASA useto compare, contrast and integrate across the elements of the EVA community's perceivedgaps, risks, and unfunded work, particularly for future systems intended for use beyond LowEarth Orbit (LEO)? What product does NASA use to proactively coordinate support acrossthe EVA community's wide spectrum of exploration development work? Where can one go toobtain awareness of ongoing efforts, particularly during consideration of new-start activitiesand proposals? These questions lead to the need for a product that speaks to the distributednature of the EVA System across human spaceflight programs, concept studies and flightvehicle architectural elements. This framework can be used and evaluated by the EVAcommunity to assess the full spectrum of needs and answer the question of "what are wemissing" or "are we doing things that just do not make sense". In the end is the EVAcommunity effectively pursuing the future needs of EVA? If answers to those questions revealthe need for change or re-prioritization then actions can be taken through existing projectcontrol processes as well as revision to this document and supporting project plans.

Alpert, Brian K.↗

An Integrated Development Environment for the Prototype Verification System

The steep learning curve of formal technologies is a well-known barrier to the adoption of formal verification tools in industry. This paper presents VSCode-PVS, a modern integrated development environment for the Prototype Verification System (PVS). This new environment integrates the editing and proof management functionalities of PVS in Visual Studio Code, a popular code editor widely used by software developers. VSCode-PVS provides functionalities that developers expect to find in modern verification tools but are not available in the standard Emacs front-end of PVS, such as auto-completion, point-and-click navigation of definitions, live diagnostics for errors, and literate programming. The main features and architecture of the environment are presented, along with a comparison with other similar tools.

Paolo Masci↗

Performance of a Regenerative Fuel Cell System for the Lunar Surface

Regenerative fuel cells (RFCs) are an attractive energy storage solution for lunar missions as a technology capable of providing a higher specific energy (i.e., W∙h/kg) than state-of-the-art packaged Li-ion battery systems. An RFC consists of the (1 & 2) electrochemical stacks (chemical to electrical energy conversion to supply electricity to an external load, i.e. the fuel cell reaction, and electrical to chemical energy conversion of supplied electrical power to dissociate water into hydrogen and oxygen gases, i.e. water electrolysis), (3) fluidic conditioning, (4) reactant storage, (5) avionics, (6) power management and distribution (PMAD), and (7) thermal management. NASA’s Glenn Research Center has designed, assembled, and tested a breadboard RFC sys-tem capable of operating autonomously for multiple simulated lunar day/night cycles in a laboratory environment. The system is comprised of a non-flow through proton exchange membrane (PEM) fuel cell stack and a liquid-anode feed PEM electrolyzer (EZ) stack designed to electrochemically compress the reactants at balanced pressures up to 12.4 MPa (1800 psia). The fluidic conditioning, avionics, PMAD, and thermal management sub-systems are largely comprised of commercial-off-the-shelf components for this system-level development effort. The hardware is controlled by a CubeSat space processor running an operational program based on core flight architecture that can control the RFC hardware autonomously through a state machine with fault monitoring. The testing results highlighted here were completed with the system in an open-loop configuration such that reactants generated through water electrolysis were vented while gas cylinders supplied fuel cell operation. The breadboard operated autonomously, but there were five unplanned transitions to a safe state that required a manual restart after reviewing the data, determining a root cause, and implementing a solution. Four of the transitions were caused by the thermal management subsystem and the fifth was caused by a water management control issue in the EZ sub-system. The RFC system operated for over 550 hours with the final cycle being slightly abbreviated due to reasons unrelated to system performance.

Kerrigan Cain↗

Performance of a Regenerative Fuel Cell System for the Lunar Surface

Regenerative fuel cells (RFCs) are an attractive energy storage solution for lunar missions as a technology capable of providing a higher specific energy (i.e., W∙h/kg) than state-of-the-art packaged Li-ion battery systems. An RFC consists of the (1 & 2) electrochemical stacks (chemical to electrical energy conversion to supply electricity to an external load, i.e. the fuel cell reaction, and electrical to chemical energy conversion of supplied electrical power to dissociate water into hydrogen and oxygen gases, i.e. water electrolysis), (3) fluidic conditioning, (4) reactant storage, (5) avionics, (6) power management and distribution (PMAD), and (7) thermal management. NASA’s Glenn Research Center has designed, assembled, and tested a breadboard RFC sys-tem capable of operating autonomously for multiple simulated lunar day/night cycles in a laboratory environment. The system is comprised of a non-flow through proton exchange membrane (PEM) fuel cell stack and a liquid-anode feed PEM electrolyzer (EZ) stack designed to electrochemically compress the reactants at balanced pressures up to 12.4 MPa (1800 psia). The fluidic conditioning, avionics, PMAD, and thermal management sub-systems are largely comprised of commercial-off-the-shelf components for this system-level development effort. The hardware is controlled by a CubeSat space processor running an operational program based on core flight architecture that can control the RFC hardware autonomously through a state machine with fault monitoring. The testing results highlighted here were completed with the system in an open-loop configuration such that reactants generated through water electrolysis were vented while gas cylinders supplied fuel cell operation. The breadboard operated autonomously, but there were five unplanned transitions to a safe state that required a manual restart after reviewing the data, determining a root cause, and implementing a solution. Four of the transitions were caused by the thermal management subsystem and the fifth was caused by a water management control issue in the EZ sub-system. The RFC system operated for over 550 hours with the final cycle being slightly abbreviated due to reasons unrelated to system performance.

Kerrigan Cain↗

Domain-Specific Languages For Developing and Deploying Signature Discovery Workflows

Domain-agnostic Signature Discovery entails scientific investigation across multiple domains through the re-use of existing algorithms into workflows. The existing algorithms may be written in any programming language for various hardware architectures (e.g., desktops, commodity clusters, and specialized parallel hardware platforms). This raises an engineering issue in generating Web services for heterogeneous algorithms so that they can be composed into a scientific workflow environment (e.g., Taverna). In this paper, we present our software tool that defines two simple Domain-Specific Languages (DSLs) to automate these processes: SDL and WDL. Our Service Description Language (SDL) describes key elements of a signature discovery algorithm and generates the service code. The Workflow Description Language (WDL) describes the pipeline of services and generates deployable artifacts for the Taverna workflow management system. We demonstrate our tool with a landscape classification example that is represented by BLAST workflows composed of services that wrap original scripts.

Jacob, Ferosh↗

Exploring Asynchronous Many-Task Runtime Systems toward Extreme Scales

Major exascale computing reports indicate a number of software challenges to meet the dramatic change of system architectures in near future. While several-orders-of-magnitude increase in parallelism is the most commonly cited of those, hurdles also include performance heterogeneity of compute nodes across the system, increased imbalance between computational capacity and I/O capabilities, frequent system interrupts, and complex hardware architectures. Asynchronous task-parallel programming models show a great promise in addressing these issues, but are not yet fully understood nor developed su ciently for computational science and engineering application codes. We address these knowledge gaps through quantitative and qualitative exploration of leading candidate solutions in the context of engineering applications at Sandia. In this poster, we evaluate MiniAero code ported to three leading candidate programming models (Charm++, Legion and UINTAH) to examine the feasibility of these models that permits insertion of new programming model elements into an existing code base.

97 MATHEMATICS AND COMPUTING↗

Space Architecture: The Role, Work and Aptitude

Space architecture has been an emerging discipline for at least 40 years. Has it arrived? Is space architecture a legitimate vocation or an avocation? If it leads to a job, what do employers want? In 2002, NASA Headquarters created a management position for a space architect whose job was to "lead the development of strategic architectures and identify high level requirements for systems that will accomplish the Nation's space exploration vision." This is a good job description with responsibility at the right level in NASA, but unfortunately, the office was discontinued two years later. Even though there is no accredited academic program or professional licensing for space architecture, there is a community of practitioners. They are civil servants, contractors and academicians supporting International Space Station and space exploration programs. In various ways, space architects currently contribute to human spaceflight, but there is a way for the discipline to be more effective in developing solutions to large scale complex problems. This paper organizes contributions from engineers, architects and psychologists into recommendations on the role of space architects in the organization, the process of creating and selecting options, and intrinsic personality traits including why they must have a high tolerance for ambiguity.

Griffin, Brand↗

Automation of Data Traffic Control on DSM Architecture

The design of distributed shared memory (DSM) computers liberates users from the duty to distribute data across processors and allows for the incremental development of parallel programs using, for example, OpenMP or Java threads. DSM architecture greatly simplifies the development of parallel programs having good performance on a few processors. However, to achieve a good program scalability on DSM computers requires that the user understand data flow in the application and use various techniques to avoid data traffic congestions. In this paper we discuss a number of such techniques, including data blocking, data placement, data transposition and page size control and evaluate their efficiency on the NAS (NASA Advanced Supercomputing) Parallel Benchmarks. We also present a tool which automates the detection of constructs causing data congestions in Fortran array oriented codes and advises the user on code transformations for improving data traffic in the application.

Frumkin, Michael↗

BIRD: A general interface for sparse distributed memory simulators

Kanerva's sparse distributed memory (SDM) has now been implemented for at least six different computers, including SUN3 workstations, the Apple Macintosh, and the Connection Machine. A common interface for input of commands would both aid testing of programs on a broad range of computer architectures and assist users in transferring results from research environments to applications. A common interface also allows secondary programs to generate command sequences for a sparse distributed memory, which may then be executed on the appropriate hardware. The BIRD program is an attempt to create such an interface. Simplifying access to different simulators should assist developers in finding appropriate uses for SDM.

Rogers, David↗

Bim-to-fea Conversion Program

The purpose of this program is to enable interoperability between BIM-based architectural design software (i.e., Revit, ArchiCAD, AVEVA E3D) to structural analysis software (i.e., SAP2000). The program takes in BIM building model data via the IFC file format, automatically transforms the architectural coordination entities (structural beams, columns, slabs, walls) to structural analysis entities (i.e., finite element space frames and shells), automatically adjusts the connectivity of the structural analysis entities, and finally exports the structural analysis entities as a structural analysis model contained within a new IFC file. For example, a 3D building in Revit can be exported to an IFC file, run through this BIM-to-FEA program, then the exported IFC can be inputted into SAP2000.

Crowder, Nicholas [Idaho National Laboratory (INL)↗

Multi-Terrain Earth Landing Systems Applicable for Manned Space Capsules

A key element of the President's Vision for Space Exploration is the development of a new space transportation system to replace the Shuttle that will enable manned exploration of the moon, Mars, and beyond. NASA has tasked the Constellation Program with the development of this architecture, which includes the Ares launch vehicle and Orion manned spacecraft. The Orion spacecraft must carry six astronauts and its primary structure should be reusable, if practical. These requirements led the Constellation Program to consider a baseline land landing on return to earth. To assess the landing system options for Orion, a review of current operational parachute landing systems such as those used for the F-111 escape module and the Soyuz is performed. In particular, landing systems with airbags and retrorockets that would enable reusability of the Orion capsule are investigated. In addition, Apollo tests and analyses conducted in the 1960's for both water and land landings are reviewed. Finally, tests and dynamic finite element simulations to understand land landings for the Orion spacecraft are also presented.

Fasanella, Edwin L.↗

Multi-Terrain Earth Landing Systems Applicable for Manned Space Capsules

A key element of the President's Vision for Space Exploration is the development of a new space transportation system to replace Shuttle that will enable manned exploration of the moon, Mars, and beyond. NASA has tasked the Constellation Program with the development of this architecture, which includes the Ares launch vehicle and Orion manned spacecraft. The Orion spacecraft must carry six astronauts and its primary structure should be reusable, if practical. These requirements led the Constellation Program to consider a baseline land landing on return to earth. To assess the landing system options for Orion, a review of current operational parachute landing systems such as those used for the F-111 escape module and the Soyuz is performed. In particular, landing systems with airbags and retrorockets that would enable reusability of the Orion capsule are investigated. In addition, Apollo tests and analyses conducted in the 1960's for both water and land landings are reviewed. Finally, tests and dynamic finite element simulations to understand land landings for the Orion spacecraft are also presented.

Fasanella, Edwin L.↗

High Performance Programming Using Explicit Shared Memory Model on Cray T3D1

The Cray T3D system is the first-phase system in Cray Research, Inc.'s (CRI) three-phase massively parallel processing (MPP) program. This system features a heterogeneous architecture that closely couples DEC's Alpha microprocessors and CRI's parallel-vector technology, i.e., the Cray Y-MP and Cray C90. An overview of the Cray T3D hardware and available programming models is presented. Under Cray Research adaptive Fortran (CRAFT) model four programming methods (data parallel, work sharing, message-passing using PVM, and explicit shared memory model) are available to the users. However, at this time data parallel and work sharing programming models are not available to the user community. The differences between standard PVM and CRI's PVM are highlighted with performance measurements such as latencies and communication bandwidths. We have found that the performance of neither standard PVM nor CRI s PVM exploits the hardware capabilities of the T3D. The reasons for the bad performance of PVM as a native message-passing library are presented. This is illustrated by the performance of NAS Parallel Benchmarks (NPB) programmed in explicit shared memory model on Cray T3D. In general, the performance of standard PVM is about 4 to 5 times less than obtained by using explicit shared memory model. This degradation in performance is also seen on CM-5 where the performance of applications using native message-passing library CMMD on CM-5 is also about 4 to 5 times less than using data parallel methods. The issues involved (such as barriers, synchronization, invalidating data cache, aligning data cache etc.) while programming in explicit shared memory model are discussed. Comparative performance of NPB using explicit shared memory programming model on the Cray T3D and other highly parallel systems such as the TMC CM-5, Intel Paragon, Cray C90, IBM-SP1, etc. is presented.

Simon, Horst D.↗

Fault Management Architectures and the Challenges of Providing Software Assurance

Fault Management (FM) is focused on safety, the preservation of assets, and maintaining the desired functionality of the system. How FM is implemented varies among missions. Common to most missions is system complexity due to a need to establish a multi-dimensional structure across hardware, software and spacecraft operations. FM is necessary to identify and respond to system faults, mitigate technical risks and ensure operational continuity. Generally, FM architecture, implementation, and software assurance efforts increase with mission complexity. Because FM is a systems engineering discipline with a distributed implementation, providing efficient and effective verification and validation (V&V) is challenging. A breakout session at the 2012 NASA Independent Verification & Validation (IV&V) Annual Workshop titled "V&V of Fault Management: Challenges and Successes" exposed this issue in terms of V&V for a representative set of architectures. NASA's Software Assurance Research Program (SARP) has provided funds to NASA IV&V to extend the work performed at the Workshop session in partnership with NASA's Jet Propulsion Laboratory (JPL). NASA IV&V will extract FM architectures across the IV&V portfolio and evaluate the data set, assess visibility for validation and test, and define software assurance methods that could be applied to the various architectures and designs. This SARP initiative focuses efforts on FM architectures from critical and complex projects within NASA. The identification of particular FM architectures and associated V&V/IV&V techniques provides a data set that can enable improved assurance that a system will adequately detect and respond to adverse conditions. Ultimately, results from this activity will be incorporated into the NASA Fault Management Handbook providing dissemination across NASA, other agencies and the space community. This paper discusses the approach taken to perform the evaluations and preliminary findings from the research.

Fault Management↗

GASNet-EX RMA Communication Performance on Recent Supercomputing Systems

Partitioned Global Address Space (PGAS) programming models, typified by systems such as Unified Parallel C (UPC) and Fortran coarrays, expose one-sided Remote Memory Access (RMA) communication as a key building block for High Performance Computing (HPC) applications. Architectural trends in supercomputing make such programming models increasingly attractive, and newer, more sophisticated models such as UPC++, Legion and Chapel that rely upon similar communication paradigms are gaining popularity. GASNet-EX is a portable, open-source, high-performance communication library designed to efficiently support the networking requirements of PGAS runtime systems and other alternative models in emerging exascale machines. The library is an evolution of the popular GASNet communication system, building upon 20 years of lessons learned. We present microbenchmark results which demonstrate the RMA performance of GASNet-EX is competitive with MPI implementations on four recent, high-impact, production HPC systems. These results are an update relative to previously published results on older systems. The networks measured here are representative of hardware currently used in six of the top ten fastest supercomputers in the world, and all of the exascale systems on the U.S. DOE road map.

Hargrove, Paul H↗

NASA Centers and Universities Collaborate Through Smallsat Technology Partnerships

The Small Spacecraft Technology (SST) Program within the NASA Space Technology Mission Directorate is chartered develop and demonstrate the capabilities that enable small spacecraft to achieve science and exploration missions in "unique" and "more affordable" ways. Specifically, the SST program seeks to enable new mission architectures through the use of small spacecraft, to expand the reach of small spacecraft to new destinations, and to make possible the augmentation existing assets and future missions with supporting small spacecraft. The SST program sponsors smallsat technology development partnerships between universities and NASA Centers in order to engage the unique talents and fresh perspectives of the university community and to share NASA experience and expertise in relevant university projects to develop new technologies and capabilities for small spacecraft. These partnerships also engage NASA personnel in the rapid, agile and cost-conscious small spacecraft approaches that have evolved in the university community, as well as increase support to university efforts and foster a new generation of innovators for NASA and the nation.

Partnerships↗

Architecture Adaptive Computing Environment

Architecture Adaptive Computing Environment (aCe) is a software system that includes a language, compiler, and run-time library for parallel computing. aCe was developed to enable programmers to write programs, more easily than was previously possible, for a variety of parallel computing architectures. Heretofore, it has been perceived to be difficult to write parallel programs for parallel computers and more difficult to port the programs to different parallel computing architectures. In contrast, aCe is supportable on all high-performance computing architectures. Currently, it is supported on LINUX clusters. aCe uses parallel programming constructs that facilitate writing of parallel programs. Such constructs were used in single-instruction/multiple-data (SIMD) programming languages of the 1980s, including Parallel Pascal, Parallel Forth, C*, *LISP, and MasPar MPL. In aCe, these constructs are extended and implemented for both SIMD and multiple- instruction/multiple-data (MIMD) architectures. Two new constructs incorporated in aCe are those of (1) scalar and virtual variables and (2) pre-computed paths. The scalar-and-virtual-variables construct increases flexibility in optimizing memory utilization in various architectures. The pre-computed-paths construct enables the compiler to pre-compute part of a communication operation once, rather than computing it every time the communication operation is performed.

Dorband, John E.↗