Search NASA⌕ Search

SEARCH · Search NASA

Results for “generic programming”

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 109 records · Page 6

A portable MPI-based parallel vector template library

This paper discusses the design and implementation of a polymorphic collection library for distributed address-space parallel computers. The library provides a data-parallel programming model for C++ by providing three main components: a single generic collection class, generic algorithms over collections, and generic algebraic combining functions. Collection elements are the fourth component of a program written using the library and may be either of the built-in types of C or of user-defined types. Many ideas are borrowed from the Standard Template Library (STL) of C++, although a restricted programming model is proposed because of the distributed address-space memory model assumed. Whereas the STL provides standard collections and implementations of algorithms for uniprocessors, this paper advocates standardizing interfaces that may be customized for different parallel computers. Just as the STL attempts to increase programmer productivity through code reuse, a similar standard for parallel computers could provide programmers with a standard set of algorithms portable across many different architectures. The efficacy of this approach is verified by examining performance data collected from an initial implementation of the library running on an IBM SP-2 and an Intel Paragon.

Sheffler, Thomas J.↗

A Portable MPI-Based Parallel Vector Template Library

This paper discusses the design and implementation of a polymorphic collection library for distributed address-space parallel computers. The library provides a data-parallel programming model for C + + by providing three main components: a single generic collection class, generic algorithms over collections, and generic algebraic combining functions. Collection elements are the fourth component of a program written using the library and may be either of the built-in types of c or of user-defined types. Many ideas are borrowed from the Standard Template Library (STL) of C++, although a restricted programming model is proposed because of the distributed address-space memory model assumed. Whereas the STL provides standard collections and implementations of algorithms for uniprocessors, this paper advocates standardizing interfaces that may be customized for different parallel computers. Just as the STL attempts to increase programmer productivity through code reuse, a similar standard for parallel computers could provide programmers with a standard set of algorithms portable across many different architectures. The efficacy of this approach is verified by examining performance data collected from an initial implementation of the library running on an IBM SP-2 and an Intel Paragon.

Sheffler, Thomas J.↗

Second Generation RLV Space Vehicle Concept

NASA has a long history of conducting development programs and projects in a consistent fashion. Systems Engineering within those programs and projects has also followed a given method outlined by such documents as the NASA Systems Engineering Handbook. The relatively new NASA Space Launch Initiative (SLI) is taking a new approach to developing a space vehicle, with innovative management methods as well as new Systems Engineering processes. With the program less than a year into its life cycle, the efficacy of these new processes has yet to be proven or disproven. At $776M for phase 1, SLI represents a major portion of the NASA focus; however, the new processes being incorporated are not reflected in the training provided by NASA to its engineers. The NASA Academy of Program and Project Leadership (APPL) offers core classes in program and project management and systems engineering to NASA employees with the purpose of creating a "knowledge community where ideas, skills, and experiences are exchanged to increase each other's capacity for strong leadership". The SLI program is, in one sense, a combination of a conceptual design program and a technology program. The program as a whole doesn't map into the generic systems engineering project cycle as currently, and for some time, taught. For example, the NASA APPL Systems Engineering training course teaches that the "first step in developing an architecture is to define the external boundaries of the system", which will require definition of the interfaces with other systems and the next step will be to "define all the components that make up the next lower level of the system hierarchy" where fundamental requirements are allocated to each component. Whereas, the SLI technology risk reduction approach develops architecture subsystem technologies prior to developing architectures. The higher level architecture requirements are not allowed to fully develop and undergo decomposition and allocation down to the subsystems before the subsystems must develop allocated requirements based on the highest level of requirements. In the vernacular of the project cycles prior to the mid 1990's, the architecture definition portion of the program appears to be at a generic Phase A stage, while the subsystems are operating at Phase B. Even the management structure of the SLI program is innovative in its approach to Systems Engineering and is not reflected in the APPL training modules. The SLI program has established a Systems Engineering office as an office separate from the architecture development or the subsystem technology development, while that office does have representatives within these other offices. The distributed resources of the Systems Engineering Office are co-located with the respective Project Offices. This template is intended to provide systems engineering as an integrated function at the Program Level. the program management of SLI and the MAT agree that "program/project managers and the systems engineering team must work closely together towards the single objective of delivering quality products that meet the customer needs". This paper will explore the differences between the methods being taught by NASA, which represent decades of ideas, and those currently in practice in SLI. Time will tell if the innovation employed by SLI will prove to be the model of the future. For now, it is suggested that the training of the present exercise the flexibility of recognizing the new processes employed by a major new NASA program.

Bailey, Michelle↗

Manned geosynchronous mission requirements and systems analysis study extension. Volume 1: Executive summary

A study was performed to determine the types of manned missions that will likely be performed in the late 1980's or early 1990's timeframe, to define MOTV configurations which satisfy these missions requirements, and to develop a program plan for its development. Twenty generic missions were originally defined for MOTV but, to simplify the selection process, five of these missions were selected as typical and used as Design Reference Missions. Systems and subsystems requirements were re-examined and sensitivity analyses performed to determine optimum point designs. Turnaround modes were considered to determine the most effective combination of ground based and spaced based activities. A preferred concept for the crew capsule and for the mission mode was developed.

Source record↗

Structures performance, benefit, cost-study

New technology concepts and structural analysis development needs which could lead to improved life cycle cost for future high-bypass turbofans were studied. The NASA-GE energy efficient engine technology is used as a base to assess the concept benefits. Recommended programs are identified for attaining these generic structural and other beneficial technologies.

Woike, O. G.↗

United Airlines LOFT training

Line oriented training is used in a broader, more generic sense that as a specific program under FAR 12.1409 and AC 120-35. A company policy was adopted more than twenty years ago requiring that all pilot checks and recurrent training be conducted with a full crew occupying the seats they occupy on the line. Permission was obtained to reschedule the hours for recurrent proficiency training to include one and one-half hours of LOFT flight. The number of emergencies and abnormal procedures which could be undertaken were considered and the introduction of an a occasional incapacitation revealed which person is the most difficult to replace on the widebodies. By using the LOFT concept, every training period can be structured like a typical line flight. The use of LOFT in simulator syllabus development and problems that need to be refined are discussed.

Cavanagh, D.↗

Cooperative analysis expert situation assessment research

For the past few decades, Rome Air Development Center (RADC) has been conducting research in Artificial Intelligence (AI). When the recent advances in hardware technology made many AI techniques practical, the Intelligence and Reconnaissance Directorate of RADC initiated an applications program entitled Knowledge Based Intelligence Systems (KBIS). The goal of the program is the development of a generic Intelligent Analyst System, an open machine with the framework for intelligence analysis, natural language processing, and man-machine interface techniques, needing only the specific problem domain knowledge to be operationally useful. The development of KBIS is described.

Mccown, Michael G.↗

STV engine requirements

The Space Exploration Initiative program and the Space Transfer Vehicle studies provide the opportunity to evaluate the engine requirements for the next generation space engine within the context of a credible but technologically demanding program. Some of these requirements are generic, basically independent of the architecture, and others are mission and configuration dependent. Generic requirements include high reliability, space-basing, man-rataing, long life and reusability, and extended health monitoring, including automatic pre-mission checkout. Mission and configuration dependent requirements include vehicle/engine interfaces, engine throttling, performance specifications, engine system architecture, and operational requirements. It is argued that engine technology requirements must be extended from the usual performance-related issues to encompass reliability, space-basing, life, and extended health monitoring.

Redus, J. R.↗

Test Cases for the Benchmark Active Controls: Spoiler and Control Surface Oscillations and Flutter

As a portion of the Benchmark Models Program at NASA Langley, a simple generic model was developed for active controls research and was called BACT for Benchmark Active Controls Technology model. This model was based on the previously-tested Benchmark Models rectangular wing with the NACA 0012 airfoil section that was mounted on the Pitch and Plunge Apparatus (PAPA) for flutter testing. The BACT model had an upper surface spoiler, a lower surface spoiler, and a trailing edge control surface for use in flutter suppression and dynamic response excitation. Previous experience with flutter suppression indicated a need for measured control surface aerodynamics for accurate control law design. Three different types of flutter instability boundaries had also been determined for the NACA 0012/PAPA model, a classical flutter boundary, a transonic stall flutter boundary at angle of attack, and a plunge instability near M = 0.9. Therefore an extensive set of steady and control surface oscillation data was generated spanning the range of the three types of instabilities. This information was subsequently used to design control laws to suppress each flutter instability. There have been three tests of the BACT model. The objective of the first test, TDT Test 485, was to generate a data set of steady and unsteady control surface effectiveness data, and to determine the open loop dynamic characteristics of the control systems including the actuators. Unsteady pressures, loads, and transfer functions were measured. The other two tests, TDT Test 502 and TDT Test 5 18, were primarily oriented towards active controls research, but some data supplementary to the first test were obtained. Dynamic response of the flexible system to control surface excitation and open loop flutter characteristics were determined during Test 502. Loads were not measured during the last two tests. During these tests, a database of over 3000 data sets was obtained. A reasonably extensive subset of the data sets from the first two tests have been chosen for Test Cases for computational comparisons concentrating on static conditions and cases with harmonically oscillating control surfaces. Several flutter Test Cases from both tests have also been included. Some aerodynamic comparisons with the BACT data have been made using computational fluid dynamics codes at the Navier-Stokes level (and in the accompanying chapter SC). Some mechanical and active control studies have been presented. In this report several Test Cases are selected to illustrate trends for a variety of different conditions with emphasis on transonic flow effects. Cases for static angles of attack, static trailing-edge and upper-surface spoiler deflections are included for a range of conditions near those for the oscillation cases. Cases for trailing-edge control and upper-surface spoiler oscillations for a range of Mach numbers, angle of attack, and static control deflections are included. Cases for all three types of flutter instability are selected. In addition some cases are included for dynamic response measurements during forced oscillations of the controls on the flexible mount. An overview of the model and tests is given, and the standard formulary for these data is listed. Some sample data and sample results of calculations are presented. Only the static pressures and the first harmonic real and imaginary parts of the pressures are included in the data for the Test Cases, but digitized time histories have been archived. The data for the Test Cases are also available as separate electronic files.

Bennett, Robert M.↗

Propulsion System Modeling and Simulation

The Aerospace Systems Design Laboratory at the School of Aerospace Engineering in Georgia Institute of Technology has developed a core competency that enables propulsion technology managers to make technology investment decisions substantiated by propulsion and airframe technology system studies. This method assists the designer/manager in selecting appropriate technology concepts while accounting for the presence of risk and uncertainty as well as interactions between disciplines. This capability is incorporated into a single design simulation system that is described in this paper. This propulsion system design environment is created with a commercially available software called iSIGHT, which is a generic computational framework, and with analysis programs for engine cycle, engine flowpath, mission, and economic analyses. iSIGHT is used to integrate these analysis tools within a single computer platform and facilitate information transfer amongst the various codes. The resulting modeling and simulation (M&S) environment in conjunction with the response surface method provides the designer/decision-maker an analytical means to examine the entire design space from either a subsystem and/or system perspective. The results of this paper will enable managers to analytically play what-if games to gain insight in to the benefits (and/or degradation) of changing engine cycle design parameters. Furthermore, the propulsion design space will be explored probabilistically to show the feasibility and viability of the propulsion system integrated with a vehicle.

Tai, Jimmy C. M.↗

Implementation of Programmatic Quality and the Impact on Safety

The purpose of this paper is to discuss the implementation of a programmatic quality assurance discipline within the International Space Station Program and the resulting impact on safety. NASA culture has continued to stress safety at the expense of quality when both are extremely important and both can equally influence the success or failure of a Program or Mission. Although safety was heavily criticized in the media after Col~imbiaa, strong case can be made that it was the failure of quality processes and quality assurance in all processes that eventually led to the Columbia accident. Consequently, it is possible to have good quality processes without safety, but it is impossible to have good safety processes without quality. The ISS Program quality assurance function was analyzed as representative of the long-term manned missions that are consistent with the President s Vision for Space Exploration. Background topics are as follows: The quality assurance organizational structure within the ISS Program and the interrelationships between various internal and external organizations. ISS Program quality roles and responsibilities with respect to internal Program Offices and other external organizations such as the Shuttle Program, JSC Directorates, NASA Headquarters, NASA Contractors, other NASA Centers, and International Partner/participants will be addressed. A detailed analysis of implemented quality assurance responsibilities and functions with respect to NASA Headquarters, the JSC S&MA Directorate, and the ISS Program will be presented. Discussions topics are as follows: A comparison of quality and safety resources in terms of staffing, training, experience, and certifications. A benchmark assessment of the lessons learned from the Columbia Accident Investigation (CAB) Report (and follow-up reports and assessments), NASA Benchmarking, and traditional quality assurance activities against ISS quality procedures and practices. The lack of a coherent operational and sustaining quality assurance strategy for long-term manned space flight. An analysis of the ISS waiver processes and the Problem Reporting and Corrective Action (PRACA) process implemented as quality functions. Impact of current ISS Program procedures and practices with regards to operational safety and risk A discussion regarding a "defense-in-depth" approach to quality functions will be provided to address the issue of "integration vs independence" with respect to the roles of Programs, NASA Centers, and NASA Headquarters. Generic recommendations are offered to address the inadequacies identified in the implementation of ISS quality assurance. A reassessment by the NASA community regarding the importance of a "quality culture" as a component within a larger "safety culture" will generate a more effective and value-added functionality that will ultimately enhance safety.

Huls, Dale Thomas↗

Constellation's Command, Control, Communications and Information (C3I) Architecture

Operations concepts are highly effective for: 1) Developing consensus; 2) Discovering stakeholder needs, goals, objectives; 3) Defining behavior of system components (especially emergent behaviors). An interoperability standard can provide an excellent lever to define the capabilities needed for system evolution. Two categories of architectures are needed in a program of this size are: 1) Generic - Needed for planning, design and construction standards; 2) Specific - Needed for detailed requirement allocations, interface specs. A wide variety of architectural views are needed to address stakeholder concerns, including: 1) Physical; 2) Information (structure, flow, evolution); 3) Processes (design, manufacturing, operations); 4) Performance; 5) Risk.

constellation↗

System Safety Hazards Assessment in Conceptual Program Trade Studies

Providing a program in the concept development phase with a method of determining system safety benefits of potential concepts has always been a challenge. Lockheed Martin Space and Strategic Missiles has developed a methodology for developing a relative system safety ranking using the potential hazards of each concept. The resulting output supports program decisions with system safety as an evaluation criterion with supporting data for evaluation. This approach begins with a generic hazards list that has been tailored for the program being studied and augmented with an initial hazard analysis. Each proposed concept is assessed against the list of program hazards and ranked in three derived areas. The hazards can be weighted to show those that are of more concern to the program. Sensitivities can be also be determined to test the robustness of the conclusions

Eben, Dennis M.↗

An overview of NASA intermittent combustion engine research

This paper overviews the current program, whose objective is to establish the generic technology base for advanced aircraft I.C. engines of the early 1990's and beyond. The major emphasis of this paper is on development of the past two years. Past studies and ongoing confirmatory experimental efforts are reviewed, which show unexpectly high potential when modern aerospace technologies are applied to inherently compact and balanced I.C. engine configurations. Currently, the program is focussed on two engine concepts the stratified-charge, multi-fuel rotary, and the lightweight two-stroke diesel. A review is given of contracted and planned high performance one-rotor and one-cylinder test engine work addressing several levels of technology. Also reviewed are basic supporting efforts, e.g., the development and experimental validation of computerized airflow and combustion process models, being performed in-house at Lewis Research Center and by university grants.

Willis, E. A.↗

An overview of NASA intermittent combustion engine research

This paper overviews the current program, whose objective is to establish the generic technology base for advanced aircraft I.C. engines of the early 1990's and beyond. The major emphasis of this paper is on development of the past two years. Past studies and ongoing confirmatory experimental efforts are reviewed, which show unexpectedly high potential when modern aerospace technologies are applied to inherently compact and balanced I.C. engine configurations. Currently, the program is focussed on two engine concepts, the stratified-charge, multi-fuel rotary and the lightweight two-stroke diesel. A review is given of contracted and planned high performance one-rotor and one-cylinder test engine work addressing several levels of technology. Also reviewed are basic supporting efforts, e.g., the development and experimental validation of computerized airflow and combustion process models, being performed in-house at Lewis Research Center and by university grants. Previously announced in STAR as N84-24583

Willis, E. A.↗

Generic propellant transfer unit: A project update

Currently, most satellite programs use dedicated hypergolic propellant ground servicing equipment. These 'carts' are typically program specific (non-interchangeable), costly, and non-Department of Transportation (DOT) compliant. They require safety waivers when used on government property and must be emptied before off-site transport. The emptying process usually generates large amounts of Hazardous Wastes. Fuel carts are usually loaded from multiple 208-liter (55 gallon) drums and oxidizer carts from 909-kg (2000 lb) cylinders. This further increases operating costs due to additional container samples and cart-filling transfers. NASA, Kennedy Space Center has developed reusable, generic, DOT compliant propellant delivery containers as possible replacements for the propellant-tank portion of servicing carts. Our ultimate goal is to reduce operating expenses by minimizing propellant transfers, samples, and waste generation through use of bulk propellant operations, minimizing drum or cylinder operations. This has the added benefit of increasing operating safety by decreasing overall propellant operations.

Davis, C. L.↗

Flow studies in close-coupled ventral nozzles for STOVL aircraft

Flow in a generic ventral nozzle system was studied experimentally and analytically with the PARC3D computational fluid dynamics program in order to evaluate the program's ability to predict system performance and internal flow patterns. A generic model of a tailpipe with a rectangular ventral nozzle, about 1/3 of full size, was tested with unheated air at steady state pressure ratios up to 4.0. The end of the tailpipe was closed to simulate a blocked exhaust nozzle. Flow behavior into and through the ventral duct is discussed and illustrated with paint streak flow visualization photographs. PARC3D graphic images are shown for comparison with the experimental photographs. The program successfully predicted internal flow patterns; it also computed thrust and discharge coefficients within 1 pct. of measured values.

Mcardle, Jack G.↗

Flow studies in close-coupled ventral nozzles for STOVL aircraft

Flow in a generic ventral nozzle system was studied experimentally and analytically with the PARC3D computational fluid dynamics program (a full Navier-Stokes equations solver) in order to evaluate the program's ability to predict system performance and internal flow patterns. A generic model of a tailpipe with a rectangular ventral nozzle, about one-third of full size, was tested with unheated air at steady-state pressure ratios up to 4.0. Measurements showed about 5.5 percent flow-turning loss and reasonable nozzle performance coefficients. The flow turned more than the designed 90 deg, causing an aftward axial component in the total thrust. Flow behavior into and through the ventral duct is discussed and illustrated with paint streak flow visualization photographs. PARC3D graphic images are shown for comparison with the experiment photographs. The program successfully predicted internal flow patterns; it also computed thrust and discharge coefficients within 1 percent of measured values.

Mcardle, Jack G.↗