Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “data engineering”

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
All sourcesNASA NTRSDOE OSTI
NASA NTRS1938

Engine Performance and Knock Rating of Fuels for High-output Aircraft Engines

Data are presented to show the effects of inlet-air pressure, inlet-air temperature, and compression ratio on the maximum permissible performance obtained on a single-cylinder test engine with aircraft-engine fuels varying from a fuel of 87 octane number to one 100 octane number plus 1 ml of tetraethyl lead per gallon. The data were obtained on a 5-inch by 5.75-inch liquid-cooled engine operating at 2,500 r.p.m. The compression ratio was varied from 6.50 to 8.75. The inlet-air temperature was varied from 120 to 280 F. and the inlet-air pressure from 30 inches of mercury absolute to the highest permissible. The limiting factors for the increase in compression ratio and in inlet-air pressure was the occurrence of either audible or incipient knock. The data are correlated to show that, for any one fuel,there is a definite relationship between the limiting conditions of inlet-air temperature and density at any compression ratio. This relationship is dependent on the combustion-gas temperature and density relationship that causes knock. The report presents a suggested method of rating aircraft-engine fuels based on this relationship. It is concluded that aircraft-engine fuels cannot be satisfactorily rated by any single factor, such as octane number, highest useful compression ratio, or allowable boost pressure. The fuels should be rated by a curve that expresses the limitations of the fuel over a variety of engine conditions.

Rothbrock, A M↗
NASA NTRS1987

Space shuttle main engine vibration data base

In order to evaluate Space Shuttle Main Engine (SSME) vibration data without having to constantly replay analog tapes, the SSME Vibration Data Base was developed. This data base contains data that have been digitized at a high sample rate for the entire test duration. It provides quick and efficient recall capabilities for numerious computation and display routines. The data base components are described as well as some of the compution and display features.

Lewallen, Pat↗
NASA NTRS2011

Assessment of Radiated Fan Noise Prediction Capabilities Using Static Engine Test Data

This paper describes further assessment of the CDUCT-LaRC code via comparison with static engine test data. In an effort to improve confidence in the use of CDUCT-LaRC for liner optimization studies addressing realistic three-dimensional geometries, inlet radiated fan noise predictions were performed at 54% and 87% engine speed settings. Predictions were then compared with far-field measurements to assess the approach and implementation. The particular configurations were chosen to exercise the three-dimensional capability of CDUCT-LaRC and it s applicability to realistic configurations and conditions. At the 54% engine speed setting, the predictions capture the general directivity and acoustic treatment effects quite well. Comparisons of the predicted and measured directivity at the 87% power setting were more problematic. This was likely due in part to the difficulties in source specification and possibly the nonlinear nature of buzz-saw tones at this engine operating condition. Overall, the approach captured the basic trends and provided a conservative estimate of liner effects from which relative performance metrics could be inferred.

Nark, Douglas M.↗
NASA NTRS2006

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challange

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

systems engineering↗
NASA NTRS1982

An automated data management/analysis system for space shuttle orbiter tiles

An engineering data management system was combined with a nonlinear stress analysis program to provide a capability for analyzing a large number of tiles on the space shuttle orbiter. Tile geometry data and all data necessary of define the tile loads environment accessed automatically as needed for the analysis of a particular tile or a set of tiles. User documentation provided includes: (1) description of computer programs and data files contained in the system; (2) definitions of all engineering data stored in the data base; (3) characteristics of the tile anaytical model; (4) instructions for preparation of user input; and (5) a sample problem to illustrate use of the system. Description of data, computer programs, and analytical models of the tile are sufficiently detailed to guide extension of the system to include additional zones of tiles and/or additional types of analyses

Giles, G. L.↗
NASA NTRS1975

Space shuttle orbit maneuvering engine

Data on the performance, stability, and thermal characteristics of an OME operating with an alternate injector configuration and with alternate propellants was obtained. The design, manufacturing, and operating characteristics of an electroformed, regeneratively cooled thrust chamber were also derived. Subscale and full scale tests provide data relating to off-design and transient operation.

Pauckert, R. P.↗
NASA NTRS2006

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Ground Data System (GDS)↗
NASA NTRS1990

Machine learning of fault characteristics from rocket engine simulation data

Transformation of data into knowledge through conceptual induction has been the focus of our research described in this paper. We have developed a Machine Learning System (MLS) to analyze the rocket engine simulation data. MLS can provide to its users fault analysis, characteristics, and conceptual descriptions of faults, and the relationships of attributes and sensors. All the results are critically important in identifying faults.

Ke, Min↗
NASA NTRS2003

Interactive, Secure Web-enabled Aircraft Engine Simulation Using XML Databinding Integration

This paper discusses the detailed design of an XML databinding framework for aircraft engine simulation. The framework provides an object interface to access and use engine data. while at the same time preserving the meaning of the original data. The Language independent representation of engine component data enables users to move around XML data using HTTP through disparate networks. The application of this framework is demonstrated via a web-based turbofan propulsion system simulation using the World Wide Web (WWW). A Java Servlet based web component architecture is used for rendering XML engine data into HTML format and dealing with input events from the user, which allows users to interact with simulation data from a web browser. The simulation data can also be saved to a local disk for archiving or to restart the simulation at a later time.

Lin, Risheng↗
NASA NTRS1991

The development of a post-test diagnostic system for rocket engines

An effort was undertaken by NASA to develop an automated post-test, post-flight diagnostic system for rocket engines. The automated system is designed to be generic and to automate the rocket engine data review process. A modular, distributed architecture with a generic software core was chosen to meet the design requirements. The diagnostic system is initially being applied to the Space Shuttle Main Engine data review process. The system modules currently under development are the session/message manager, and portions of the applications section, the component analysis section, and the intelligent knowledge server. An overview is presented of a rocket engine data review process, the design requirements and guidelines, the architecture and modules, and the projected benefits of the automated diagnostic system.

Zakrajsek, June F.↗
NASA NTRS1991

The development of a post-test diagnostic system for rocket engines

An effort was undertaken by NASA to develop an automated post-test, post-flight diagnostic system for rocket engines. The automated system is designed to be generic and to automate the rocket engine data review process. A modular, distributed architecture with a generic software core was chosen to meet the design requirements. The diagnostic system is initially being applied to the Space Shuttle Main Engine data review process. The system modules currently under development are the session/message manager, and portions of the applications section, the component analysis section, and the intelligent knowledge server. An overview is presented of a rocket engine data review process, the design requirements and guidelines, the architecture and modules, and the projected benefits of the automated diagnostic system.

Zakrajsek, June F.↗
NASA NTRS1982

QCSEE Over-the-Wing Engine Acoustic Data

The over the wing (OTW) Quiet, Clean, Short Haul Experimental Engine (QCSEE) was tested at the NASA Lewis Engine Noise Test Facility. A boilerplate (nonflight weight), high throat Mach number, acoustically treated inlet and a D shaped OTW exhaust nozzle with variable position side doors were used in the tests along with wing and flap segments to simulate an installation on a short haul transport aircraft. All of the acoustic test data from 10 configurations are documented in tabular form. Some selected narrowband and 1/3 octave band plots of sound pressure level are presented.

Bloomer, H. E.↗
NASA NTRS1976

The ABC's required for establishing a practical computerized plant engineering management data base system

A system's approach is outlined in the paper to assist facility and Plant Engineers improve their organization's data management system. The six basic steps identified may appear somewhat simple; however, adequate planning, proper resources, and the involvement of management will determine the success of a computerized facility management data base. Helpful suggestions are noted throughout the paper to insure the development of a practical computerized data management system.

Maiocco, F. R.↗
NASA NTRSDate not supplied

Medical Database Accomplishments and Lessons Learned - 2021

The Medical Database (MD) is a virtual repository consisting of two software components: the Medical Item Database (MedID) and the Evidence Library (EL). MedID consists of engineering data and associated information for specific medical resource items (e.g., pharmaceutical, medical devices, and supporting components), while the EL is a tool which provides all of the medical evidence necessary. The Medical Database will serve as the single “source of truth” for the Informing Mission Planning via Analysis of Complex Tradespaces (IMPACT) tool suite for both medical evidence and medical resource engineering data. It will be used in conjunction with the IMPACT tool suite to inform research prioritizations and perform systematic trade study evaluations using probabilistic risk assessment and simulated human spaceflight missions to aid stakeholders in making informed decisions during Pre-Phase-A planning of human spaceflight missions. The IMPACT project is conducted under the Exploration Medical Capability (ExMC) element of the Human Research Program (HRP), within NASA’s Human Exploration and Operations Mission Directorate. Over the past year, the MedID software has been successfully merged with the Evidence Library into one cohesive Medical Database with two independent user interface experiences for modifying either clinical evidence or resource engineering data. As MD has evolved substantially over the past year, a number of challenges have been encountered and overcome along the way. A number of ‘lessons learned’ and practical/logistical realizations have emerged which will be detailed in the forthcoming Medical Database presentation.

Exploration Medical Capability↗
NASA NTRS1971

Handbook of human engineering design data for reduced gravity conditions

A Handbook is presented for the use of engineers, designers, and human factors specialists during the developmental and detailed design phases of manned spacecraft programs. Detailed and diverse quantified data on man's capabilities and tolerances for survival and productive effort in the extraterrestrial environment are provided. Quantified data and information on the space environment as well as the characteristics of the vehicular or residential environment required to support man in outer space are also given.

Marton, T.↗