SEARCH · Search NASA
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.
Task provide two deliverables: 1. Technological solutions demonstrated by design, fabrication, and test of single element of small scale rocket injector hardware. 2. Improvement in capability and validity to analyze large, multi-element injectors.
PVM Wrapper is a software library that makes it possible for code that utilizes the Parallel Virtual Machine (PVM) software library to run using the message-passing interface (MPI) software library, without needing to rewrite the entire code. PVM and MPI are the two most common software libraries used for applications that involve passing of messages among parallel computers. Since about 1996, MPI has been the de facto standard. Codes written when PVM was popular often feature patterns of {"initsend," "pack," "send"} and {"receive," "unpack"} calls. In many cases, these calls are not contiguous and one set of calls may even exist over multiple subroutines. These characteristics make it difficult to obtain equivalent functionality via a single MPI "send" call. Because PVM Wrapper is written to run with MPI- 1.2, some PVM functions are not permitted and must be replaced - a task that requires some programming expertise. The "pvm_spawn" and "pvm_parent" function calls are not replaced, but a programmer can use "mpirun" and knowledge of the ranks of parent and child tasks with supplied macroinstructions to enable execution of codes that use "pvm_spawn" and "pvm_parent."
A long-term program is in progress at JPL to reduce cost and risk of mission operations through defect prevention and error management. A major element of this program, Mission Operations and Command Assurance (MO&QA), provides a system level function on flight projects to instill quality in mission operations. MO&CA embodies the Total Quality Management (TQM) principle of Continuous Process Inprovement (CPI) and uses CPI in applying automation to mission operations to reduce risk and costs. MO&CA has led efforts to apply and has implemented automation in areas that impact the daily flight project environment including Incident Surprise Anomoly tracking and reporting; command data verification, tracking, and reporting; and command support data usage. MO&CA's future work in automation will take into account that future missions systems must be designed to avoid increasing error through the introduction of automation, while adapting to the demands of smaller flight teams.
Survey of the present technological development status of machine intelligence for autonomous manipulation in the U.S., Japan, USSR, and England. The extent of task-performance autonomy is examined that machine intelligence gives the manipulator by eliminating the need for a human operator to close continuously the control loop, or to rewrite control programs for each different task. Surveyed research projects show that the development of some advanced automation systems for manipulator control are within the state of the art. Yet, many more realistic breadboard systems and experimental work are needed before further progress can be made in the design of advanced automation systems for manipulator control suitable for new major practical applications. Specific research areas of promise are pointed out.
Large scale space programs analyze thousands of requirements while mitigating safety, performance, schedule, and cost risks. These efforts involve a variety of roles with interdependent use cases and goals. For example, study managers and facilitators identify ground-rules and assumptions for a collection of studies required for a program or project milestone. Task leaders derive product requirements from the ground rules and assumptions and describe activities to produce needed analytical products. Disciplined specialists produce the specified products and load results into a file management system. Organizational and project managers provide the personnel and funds to conduct the tasks. Each role has responsibilities to establish information linkages and provide status reports to management. Projects conduct design and analysis cycles to refine designs to meet the requirements and implement risk mitigation plans. At the program level, integrated design and analysis cycles studies are conducted to eliminate every 'to-be-determined' and develop plans to mitigate every risk. At the agency level, strategic studies analyze different approaches to exploration architectures and campaigns. This paper describes a web-accessible database developed by NASA to coordinate and manage tasks at three organizational levels. Other topics in this paper cover integration technologies and techniques for process modeling and enterprise architectures.
The objective of this contract was to provide definition of alternate propulsion systems for both earth-to-orbit (ETO) and in-space vehicles (upper stages and space transfer vehicles). For such propulsion systems, technical data to describe performance, weight, dimensions, etc. was provided along with programmatic information such as cost, schedule, needed facilities, etc. Advanced technology and advanced development needs were determined and provided. This volume separately presents the various program cost estimates that were generated under three tasks: the F-1A Restart Task, the J-2S Restart Task, and the SSME Upper Stage Use Task. The conclusions, technical results, and the program cost estimates are described in more detail in Volume 1 - Executive Summary and in individual Final Task Reports.
The objective of this contract was to provide definition of alternate propulsion systems for both earth-to-orbit (ETO) and in-space vehicles (upper stages and space transfer vehicles). For such propulsion systems, technical data to describe performance, weight, dimensions, etc. was provided along with programmatic information such as cost, schedule, needed facilities, etc. Advanced technology and advanced development needs were determined and provided. This volume separately presents the various program cost estimates that were generated under three tasks: the F- IA Restart Task, the J-2S Restart Task, and the SSME Upper Stage Use Task. The conclusions, technical results , and the program cost estimates are described in more detail in Volume I - Executive Summary and in individual Final Task Reports.
The existing radiative transfer and inversion programs will be modified for application to the atmospheres of Uranus, Neptune, and Jupiter. The programs will be employed for analysis of KAO planetary observations in order to develop far infrared photometric calibration standards. This work will be carried out on MSFC computers. The expected end product of this task is a working program for analysis of the observations, and numerical data representing the planets as far-infrared calibration sources.
The U.S. Army Crew Station Research and Development Branch (CSRDB) of the Aircraft Simulation Division (AVSCOM) was tasked by the Light Helicopter Program Manager (LH-PM) to provide training to Army personnel in advanced aircraft simulation technology. The purpose of this training was to prepare different groups of pilots to support and evaluate two contractor simulation efforts during the Demonstration/Validation (DEM/VAL) phase of the LH program. The personnel in the CSRDB developed mission oriented training programs to accomplish the objectives, conduct the programs, and provide guidance to army personnel and support personnel throughout the DEM/VAL phase.
Schedule Tracker provides effective method for tracking tasks "past due" and/or "near term". Generates reports for each responsible staff member having one or more assigned tasks falling within two listed categories. Schedule Organizer (SO) (COSMIC program MSC-21525), Schedule Tracker (ST), and Schedule Report Generator (SRG) (COSMIC program MSC-21527) computer programs manipulating data-base files in ways advantageous in scheduling. Written in PL/1 and DEC Command Language (DCL).
The Interdisciplinary Technology Office (ITO) has been tasked with the responsibility of coordinating interdisciplinary research and technology programs; establish and maintain interface with the various disciplines at LeRC, industry, government, and academic organizations; and facilitating the exploitation of advances in the individual disciplinary efforts that have multidisciplinary implications.
During the NASA/FAA (Federal Aviation Administration) Tailplane Icing Program, pilot evaluations of aircraft flying qualities were conducted with various ice shapes attached to the horizontal tailplane of the NASA Twin Otter Icing Research Aircraft. Initially, only NASA pilots conducted these evaluations, assessing the differences in longitudinal flight characteristics between the baseline or clean aircraft, and the aircraft configured with an Ice Contaminated Tailplane (ICT). Longitudinal tests included Constant Airspeed Flap Transitions, Constant Airspeed Thrust Transitions, zero-G Pushovers, Repeat Elevator Doublets, and Simulated Approach and Go-Around tasks. Later in the program, guest pilots from government and industry were invited to fly the NASA Twin Otter configured with a single full-span artificial ice shape attached to the leading edge of the horizontal tailplane. This shape represented ice formed due to a 'Failed Boot' condition, and was generated from tests in the Glenn Icing Research Tunnel on a full-scale tailplane model. Guest pilots performed longitudinal handling tests, similar to those conducted by the NASA pilots, to evaluate the ICT condition. In general, all pilots agreed that longitudinal flying qualities were degraded as flaps were lowered, and further degraded at high thrust settings. Repeat elevator doublets demonstrated reduced pitch damping effects due to ICT, which is a characteristic that results in degraded flying qualities. Pilots identified elevator control force reversals (CFR) in zero-G pushovers at a 20 deg flap setting, a characteristic that fails the FAR 25 no CFR certification requirement. However, when the same pilots used the Cooper-Harper rating scale to perform a simulated approach and go-around task at the 20 deg flap setting, they rated the airplane as having Level I and Level II flying qualities respectively. By comparison, the same task conducted at the 30 deg flap setting, resulted in Level II flying qualities for the approach portion, and Level III for the go-around portion.The results of this program indicate that safe and acceptable flying qualities with an ICT condition, can be effectively assessed by task-oriented pilot maneuvers. In addition, other maneuvers such as repeat elevator doublets provide good qualitative and quantitative assessments of pitch damping and elevator effectiveness, which are characteristics that correlate well with pilot task ratings. The results of this testing indicate that the FAR 25 zero-G pushover maneuver, which requires no CFR during its execution, may be an overly conservative pass/fail criteria for aircraft certification.
Management tasks associated with preparation and implementation of spacecraft system design, development, launch, and mission support for Voyager project
Computer techniques for data problems encountered by task analysts
The purpose of this paper is to present the history of Extravehicular Activity (EVA) through the Skylab Program and to outline the expected tasks and equipment capabilities projected for the Space Shuttle Program. Advantages offered by EVA as a tool to extend payload capabilities and effectiveness and economic advantages of using EVA will be explored. The presentation will conclude with some guidelines and recommendations for consideration by payload investigators in establishing concepts and designs utilizing EVA support.
Six years ago, the Defense Science Board (DSB) initiated a review of the concept, technical basis, program content, and missions of the National Aerospace Plane (NASP) program. The report was completed in Sep. 1988, and the recommendations contributed to strengthening the technical efforts in the NASP program. Since then, substantial technological progress has been made in the technology development phase (Phase 2) of the program. Phase 2 of the program is currently scheduled to end in late Fiscal Year 1993, with a decision whether to proceed to the experimental flight vehicle phase (Phase 3) to be made at that time. This decision will be a very significant one for the Department of Defense (DoD) and the National Aeronautics and Space Administration (NASA). In February of this year, the DSB was chartered to revisit the NASP program to assess the degree to which the many technical challenges of the program have been resolved, or are likely to be resolved by the end of Phase 2.
The paper discusses the management structure and organization that was developed in early 1986 to focus the national technology resource pool on the enabling technologies for the NASP. The NASP program is developing technologies in parallel with total system studies that are aimed at single stage to orbit (SSTO) capability. In order to manage the technology development seven teams were established by discipline and charged with the task of recommending specific programs to be funded by the NASP Joint Program Office (JPO). The teams were staffed by representatives from NASA Research Centers, Johns Hopkins University, and the Air Force Laboratories at Wright-Patterson AFB. In addition several special teams were established to recommend development programs for specific areas of technical concern that became apparent when the total system studies identified the technology to be critical and sensitive in the analysis that would enable a single stage to orbit vehicle.
The Navier-Stokes computer is a high-performance, reconfigurable, pipelined machine designed to solve large computational fluid dynamics problems. Due to the complexity of the architecture, development of effective, high-level language compilers for the system appears to be a very difficult task. Consequently, a visual programming methodology has been developed which allows users to program the system at an architectural level by constructing diagrams of the pipeline configuration. These schematic program representations can then be checked for validity and automatically translated into machine code. The visual environment is illustrated by using a prototype graphical editor to program an example problem.