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 361 records · Page 20

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↗

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↗

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.↗

Towards Autonomous Operation of Robonaut 2

The Robonaut 2 (R2) platform, as shown in Figure 1, was designed through a collaboration between NASA and General Motors to be a capable robotic assistant with the dexterity similar to a suited astronaut [1]. An R2 robot was sent to the International Space Station (ISS) in February 2011 and, in doing so, became the first humanoid robot in space. Its capabilities are presently being tested and expanded to increase its usefulness to the crew. Current work on R2 includes the addition of a mobility platform to allow the robot to complete tasks (such as cleaning, maintenance, or simple construction activities) both inside and outside of the ISS. To support these new activities, R2's software architecture is being developed to provide efficient ways of programming robust and autonomous behavior. In particular, a multi-tiered software architecture is proposed that combines principles of low-level feedback control with higher-level planners that accomplish behavioral goals at the task level given the run-time context, user constraints, the health of the system, and so on. The proposed architecture is shown in Figure 2. At the lowest-level, the resource level, there exists the various sensory and motor signals available to the system. The sensory signals for a robot such as R2 include multiple channels of force/torque data, joint or Cartesian positions calculated through the robot's proprioception, and signals derived from objects observable by its cameras.

Badger, Julia M.↗

Mission objectives and comparison of strategies for Mars exploration

Over the past several years, a number of candidate scenarios for the human exploration of Mars have been advanced. These have had a range of mission objectives, scope, scale, complexity and probable cost. The Exploration Programs Office (ExPO) has developed a reference Mars exploration program and a means of comparing it to other proposed Mars programs. The reference program was initiated in a workshop of Mars exploration advocates which defined two objectives of equal importance for early Mars exploration - understanding Mars and understanding the potential of Mars to support humans. These goals were used to define a set of transportation and surface elements that could carry out a robust exploration program. The approach to comparing alternate architectures has three principal parts: (1) Bringing the architectures into rough commonality in terms of surface mission objectives and hardware capabilities; (2) Providing a common level of human support for flights to and from Mars; and (3) Comparing the complexity of the elements needed to carry out the program and using partial redundancy to approximate the same statistical probability of mission success. This top-level approach has been applied to the ExPO reference program, the 'Mars Directs strategy (Zubrin, 1991) and the Stanford International Mars Mission (Lusignan, 1992).

Duke, Michael B.↗

ATLAS, an integrated structural analysis and design system. Volume 2: System design document

ATLAS is a structural analysis and design system, operational on the Control Data Corporation 6600/CYBER computers. The overall system design, the design of the individual program modules, and the routines in the ATLAS system library are described. The overall design is discussed in terms of system architecture, executive function, data base structure, user program interfaces and operational procedures. The program module sections include detailed code description, common block usage and random access file usage. The description of the ATLAS program library includes all information needed to use these general purpose routines.

Erickson, W. J.↗

Evaluating science return in space exploration initiative architectures

Science is an important aspect of the Space Exploration Initiative, a program to explore the Moon and Mars with people and machines. Different SEI mission architectures are evaluated on the basis of three variables: access (to the planet's surface), capability (including number of crew, equipment, and supporting infrastructure), and time (being the total number of man-hours available for scientific activities). This technique allows us to estimate the scientific return to be expected from different architectures and from different implementations of the same architecture. Our methodology allows us to maximize the scientific return from the initiative by illuminating the different emphases and returns that result from the alternative architectural decisions.

Budden, Nancy Ann↗

Lunar Precursor Robotic Program: A Robotic Focus To The Vision

In April 2006, NASA, with help from the commercial and international communities, began developing a global Lunar Exploration Strategy. These activities resulted in themes that expanded on why we should return to the Moon and objectives that identify what we should do when we get there. NASA used these results to develop a Lunar Architecture designed to achieve the subset of the global Lunar Exploration Strategy objectives that fit within NASA's scope. A component of this architecture is the Lunar Precursor Robotic Program. This Program, anticipated to consist of both lunar orbiters and landers, is intended to meet many of NASA's lunar exploration objectives.

French, Raymond A.↗

Advanced Information Processing System (AIPS)-based fault tolerant avionics architecture for launch vehicles

An avionics architecture for the advanced launch system (ALS) that uses validated hardware and software building blocks developed under the advanced information processing system program is presented. The AIPS for ALS architecture defined is preliminary, and reliability requirements can be met by the AIPS hardware and software building blocks that are built using the state-of-the-art technology available in the 1992-93 time frame. The level of detail in the architecture definition reflects the level of detail available in the ALS requirements. As the avionics requirements are refined, the architecture can also be refined and defined in greater detail with the help of analysis and simulation tools. A useful methodology is demonstrated for investigating the impact of the avionics suite to the recurring cost of the ALS. It is shown that allowing the vehicle to launch with selected detected failures can potentially reduce the recurring launch costs. A comparative analysis shows that validated fault-tolerant avionics built out of Class B parts can result in lower life-cycle-cost in comparison to simplex avionics built out of Class S parts or other redundant architectures.

Lala, Jaynarayan H.↗

Rocket Engine Numerical Simulator (RENS)

Work is being done at three universities to help today's NASA engineers use the knowledge and experience of their Apolloera predecessors in designing liquid rocket engines. Ground-breaking work is being done in important subject areas to create a prototype of the most important functions for the Rocket Engine Numerical Simulator (RENS). The goal of RENS is to develop an interactive, realtime application that engineers can utilize for comprehensive preliminary propulsion system design functions. RENS will employ computer science and artificial intelligence research in knowledge acquisition, computer code parallelization and objectification, expert system architecture design, and object-oriented programming. In 1995, a 3year grant from the NASA Lewis Research Center was awarded to Dr. Douglas Moreman and Dr. John Dyer of Southern University at Baton Rouge, Louisiana, to begin acquiring knowledge in liquid rocket propulsion systems. Resources of the University of West Florida in Pensacola were enlisted to begin the process of enlisting knowledge from senior NASA engineers who are recognized experts in liquid rocket engine propulsion systems. Dr. John Coffey of the University of West Florida is utilizing his expertise in interviewing and concept mapping techniques to encode, classify, and integrate information obtained through personal interviews. The expertise extracted from the NASA engineers has been put into concept maps with supporting textual, audio, graphic, and video material. A fundamental concept map was delivered by the end of the first year of work and the development of maps containing increasing amounts of information is continuing. Find out more information about this work at the Southern University/University of West Florida. In 1996, the Southern University/University of West Florida team conducted a 4day group interview with a panel of five experts to discuss failures of the RL10 rocket engine in conjunction with the Centaur launch vehicle. The discussion was recorded on video and audio tape. Transcriptions of the entire proceedings and an abbreviated video presentation of the discussion highlights are under development. Also in 1996, two additional 3year grants were awarded to conduct parallel efforts that would complement the work being done by Southern University and the University of West Florida. Dr. Prem Bhalla of Jackson State University in Jackson, Mississippi, is developing the architectural framework for RENS. By employing the Rose Rational language and Booch Object Oriented Programming (OOP) technology, Dr. Bhalla is developing the basic structure of RENS by identifying and encoding propulsion system components, their individual characteristics, and cross-functionality and dependencies. Dr. Ruknet Cezzar of Hampton University, located in Hampton, Virginia, began working on the parallelization and objectification of rocket engine analysis and design codes. Dr. Cezzar will use the Turbo C++ OOP language to translate important liquid rocket engine computer codes from FORTRAN and permit their inclusion into the RENS framework being developed at Jackson State University. The Southern University/University of West Florida grant was extended by 1 year to coordinate the conclusion of all three efforts in 1999.

Davidian, Kenneth O.↗

Performance of BLAS 3, FFTs and NAS Parallel Benchmarks on Cray T3D

Recently, a Cray T3D Emulator has been made available on the Cray Y-MP and C90 computers. The Pittsburgh Supercomputer Center has acquired a CRAY T3D system and many other centers like Jet Propulsion Laboratory (JPL) will have it by the end of 1994. The Cray T3D system is the firstphase 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. The Cray T3D Emulator will give prospective users a valuable experience in developing high performance applications on the MPP system. This emulator runs programs written in CRI's MPP Fortran programming model (data sharing and work sharing) or Parallel Virtual Machine (PVM) programming model. It will help the users to study data layout, data locality, and data reference patterns thereby providing feedback which will enable one to write more efficient parallel codes. An overview of the Cray T3D hardware, software, and three of its available programming models is presented.The Cray Fortran Programming Model comprising (a) Data Sharing, (b) Worksharing and (c) Message Passing, will be discussed with examples. We have also implemented distributed BLAS 3 (matrix-matrix multiplication) in data parallel model (using only CSHIFT); worksharing model using block distribution and collapsed distribution; and message passing model using PVM. We have also implemented 2D and 3D FFTs for radix-2 using PVM. The performance of NAS Parallel 'Benchmarks (NPB) on CRAY T3D will be compared with other highly parallel systems such as CM-5, Paragon, C90 etc.

Saini, Subhash↗

NASA’s Strategic Analysis Cycle 2021 (SAC21) Human Mars Architecture

The National Aeronautics and Space Administration’s (NASA) Mars Architecture Team (MAT) was challenged to develop a mission architecture capable of transporting humans to the surface of Mars and back as fast—and as soon—as practical. This challenge represented a significant departure from previous approaches that minimized Earth-launched mass and maximized in-space transportation efficiency, often resulting in roundtrip missions of three years or more in duration. In the interest of crew health, MAT’s cross-Agency team of subject matter experts was challenged to develop an architecture capable of shortening crew time away from Earth to about two years. MAT was given specific mission constraints, such as number of crew, as well as mandates to minimize surface infrastructure as much as possible and to incorporate nuclear transportation options. The resulting MAT-developed concept, referred to here as the Strategic Analysis Cycle 2021 (SAC21) architecture, leverages Artemis elements and emerging commercial capabilities for cargo and logistics launches, and features a hybrid Nuclear Electric Propulsion (NEP)/Chemical transportation system able to complete the 1.8 billion kilometer round-trip journey to Mars and back in 760 to 850 days transit time for the 2039 Earth departure opportunity. Three Mars Descent Systems (MDS), each capable of landing about 25 metric tons of useful cargo on the surface of Mars, would be pre-deployed in advance of crew departure from Earth; two of these MDS’s would deliver a partially fueled Mars Ascent Vehicle (MAV), a fission power system, surface mobility, and additional MAV propellant. To minimize surface infrastructure, only two of the four Mars crew would descend and live in an MDS-landed pressurized rover, exploring the martian surface for 30 martian days, or sols, before returning to Mars orbit aboard their MAV and rejoining the other two crew on the Deep Space Transport for the Earth return voyage. Specifics of many of these architecture elements are detailed in separate technical publications; this paper outlines the end-to-end integrated architecture performance and concept of operations, including synergies with Artemis lunar architecture elements. It is important to note that NASA does not have a formal human Mars program and no decisions have been made; the architecture described here is intended to fill in an often-overlooked corner of the trade space, helping to complete the menu of options available to decision-makers as they chart the course for humans to Mars.

exploration↗

NASA’s Strategic Analysis Cycle 2021 (SAC21) Human Mars Architecture

[Note: this is the presentation for a companion paper with the following abstract] The National Aeronautics and Space Administration’s (NASA) Mars Architecture Team (MAT) was challenged to develop a mission architecture capable of transporting humans to the surface of Mars and back as fast—and as soon—as practical. This challenge represented a significant departure from previous approaches that minimized Earth-launched mass and maximized in-space transportation efficiency, often resulting in roundtrip missions of three years or more in duration. In the interest of crew health, MAT’s cross-Agency team of subject matter experts was challenged to develop an architecture capable of shortening crew time away from Earth to about two years. MAT was given specific mission constraints, such as number of crew, as well as mandates to minimize surface infrastructure as much as possible and to incorporate nuclear transportation options. The resulting MAT-developed concept, referred to here as the Strategic Analysis Cycle 2021 (SAC21) architecture, leverages Artemis elements and emerging commercial capabilities for cargo and logistics launches, and features a hybrid Nuclear Electric Propulsion (NEP)/Chemical transportation system able to complete the 1.8 billion kilometer round-trip journey to Mars and back in 760 to 850 days transit time for the 2039 Earth departure opportunity. Three Mars Descent Systems (MDS), each capable of landing about 25 metric tons of useful cargo on the surface of Mars, would be pre-deployed in advance of crew departure from Earth; two of these MDS’s would deliver a partially fueled Mars Ascent Vehicle (MAV), a fission power system, surface mobility, and additional MAV propellant. To minimize surface infrastructure, only two of the four Mars crew would descend and live in an MDS-landed pressurized rover, exploring the martian surface for 30 martian days, or sols, before returning to Mars orbit aboard their MAV and rejoining the other two crew on the Deep Space Transport for the Earth return voyage. Specifics of many of these architecture elements are detailed in separate technical publications; this paper outlines the end-to-end integrated architecture performance and concept of operations, including synergies with Artemis lunar architecture elements. It is important to note that NASA does not have a formal human Mars program and no decisions have been made; the architecture described here is intended to fill in an often-overlooked corner of the trade space, helping to complete the menu of options available to decision-makers as they chart the course for humans to Mars. Note: Slide 9 contains a ~2 min video, best viewed when downloaded. Once downloaded to begin video you may be requested to hit options and Trust this document.

Long-duration spaceflight↗