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 1,261 records · Page 70

Space Transportation Engine Program (STEP), phase B

The Space Transportation Engine Program (STEP) Phase 2 effort includes preliminary design and activities plan preparation that will allow smooth and time transition into a Prototype Phase and then into Phases 3, 4, and 5. A Concurrent Engineering approach using Total Quality Management (TQM) techniques, is being applied to define an oxygen-hydrogen engine. The baseline from Phase 1/1' studies was used as a point of departure for trade studies and analyses. Existing STME system models are being enhanced as more detailed module/component characteristics are determined. Preliminary designs for the open expander, closed expander, and gas generator cycles were prepared, and recommendations for cycle selection made at the Design Concept Review (DCR). As a result of July '90 DCR, and information subsequently supplied to the Technical Review Team, a gas generator cycle was selected. Results of the various Advanced Development Programs (ADP's) for the Advanced Launch Systems (ALS) were contributive to this effort. An active vehicle integration effort is supplying the NASA, Air Force, and vehicle contractors with engine parameters and data, and flowing down appropriate vehicle requirements. Engine design and analysis trade studies are being documented in a data base that was developed and is being used to organize information. To date, seventy four trade studies were input to the data base.

Source record↗

Summary of Free-flight Performance of a Series of Ram-jet Engines at Mach Numbers from 0.80 to 2.20

Data obtained from the NACA air-launched ram-jet program are summarized with emphasis placed upon the transonic propulsive thrust potential of the engines. Data are presented for boosted and non-boosted engine configurations which incorporate a single-oblique-shock or double-oblique-shock diffuser designed for critical inlet operation at flight Mach numbers of 1.8 and 2.4, respectively. The engines are evaluated in terms of flight Mach number, mass-flow ratio, diffuser pressure recovery, combustion-chamber heat release, propulsive thrust, external drag, and specific impulse. From specific impulse considerations, it appears that for some air-launched missile applications the self-accelerating supersonic ram jet may have a lower gross weight than a rocket-boosted ram jet.

RESEARCH EQUIPMENT, FREE-FLIGHT↗

Application of Systems Engineering Principles and Techniques in Biological Big Data Analytics: A Review

In the past few decades, we have witnessed tremendous advancements in biology, life sciences and healthcare. These advancements are due in no small part to the big data made available by various high-throughput technologies, the ever-advancing computing power, and the algorithmic advancements in machine learning. Specifically, big data analytics such as statistical and machine learning has become an essential tool in these rapidly developing fields. As a result, the subject has drawn increased attention and many review papers have been published in just the past few years on the subject. Different from all existing reviews, this work focuses on the application of systems, engineering principles and techniques in addressing some of the common challenges in big data analytics for biological, biomedical and healthcare applications. Specifically, this review focuses on the following three key areas in biological big data analytics where systems engineering principles and techniques have been playing important roles: the principle of parsimony in addressing overfitting, the dynamic analysis of biological data, and the role of domain knowledge in biological data analytics.

dynamic analysis↗

GPGPU Enabled Adaptive Volume Visualization Using Commodity Game Engines

The amount of data produced by researchers in fields like nuclear engineering, materials science, and medicine has dramatically increased in recent years. There is a growing need to analyze and visualize this data in order to derive new insights. However, creating a visualization of data that is many gigabytes in size in real time is a difficult task since most graphics processing units (GPUs) are unable to hold this much data at one time. In order to alleviate this issue, an adaptive volume visualizer has been developed that is capable of rendering large scale datasets with high levels of detail at interactive framerates.

97 MATHEMATICS AND COMPUTING↗

Engineering the CernVM-Filesystem as a High Bandwidth Distributed Filesystem for Auxiliary Physics Data

A common use pattern in the computing models of particle physics experiments is running many distributed applications that read from a shared set of data files. We refer to this data is auxiliary data, to distinguish it from (a) event data from the detector (which tends to be different for every job), and (b) conditions data about the detector (which tends to be the same for each job in a batch of jobs). Relatively speaking, conditions data also tends to be relatively small per job where both event data and auxiliary data are larger per job. Unlike event data, auxiliary data comes from a limited working set of shared files. Since there is spatial locality of the auxiliary data access, the use case appears to be identical to that of the CernVM- Filesystem (CVMFS). However, we show that distributing auxiliary data through CVMFS causes the existing CVMFS infrastructure to perform poorly. We utilize a CVMFS client feature called 'alien cache' to cache data on existing local high-bandwidth data servers that were engineered for storing event data. This cache is shared between the worker nodes at a site and replaces caching CVMFS files on both the worker node local disks and on the site's local squids. We have tested this alien cache with the dCache NFSv4.1 interface, Lustre, and the Hadoop Distributed File System (HDFS) FUSE interface, and measured performance. In addition, we use high-bandwidth data servers at central sites to perform the CVMFS Stratum 1 function instead of the low-bandwidth web servers deployed for the CVMFS software distribution function. We have tested this using the dCache HTTP interface. As a result, we have a design for an end-to-end high-bandwidth distributed caching read-only filesystem, using existing client software already widely deployed to grid worker nodes and existing file servers already widely installed at grid sites. Files are published in a central place and are soon available on demand throughout the grid and cached locally on the site with a convenient POSIX interface. This paper discusses the details of the architecture and reports performance measurements.

Dykstra, D.↗

General purpose simulation system of the data management system for Space Shuttle mission 18

A simulation program for the flow of data through the Data Management System of Spacelab and Space Shuttle was presented. The science, engineering, command and guidance, navigation and control data were included. The programming language used was General Purpose Simulation System V (OS). The science and engineering data flow was modeled from its origin at the experiments and subsystems to transmission from Space Shuttle. Command data flow was modeled from the point of reception onboard and from the CDMS Control Panel to the experiments and subsystems. The GN&C data flow model handled data between the General Purpose Computer and the experiments and subsystems. Mission 18 was the particular flight chosen for simulation. The general structure of the program is presented, followed by a user's manual. Input data required to make runs are discussed followed by identification of the output statistics. The appendices contain a detailed model configuration, program listing and results.

Bengtson, N. M.↗

Enabling and Enhancing Space Mission Success and Reduction of Risk through the Application of an Integrated Data Architecture

The engineering phases of design, development, test, and evaluation (DDT and E) and subsequent planning, preparation, and operation (Ops) of space vehicles in a complex and distributed environment requires massive and continuous flows of information across the enterprise and across temporal stages of the vehicle lifecycle. The resulting capabilities at each subsequent stage depend in part on the capture, preparation, storage, and subsequent provision of information from prior stages. The United States National Aeronautics and Space Administration (NASA) is currently designing a fleet of new vehicles that will replace the Space Shuttle and expand space operations and exploration capabilities. This includes the 2 stage human rated lift vehicle Ares 1 and its associated crew vehicle the Orion, and a service module; the heavy lift cargo vehicle, Ares 5, and an associated cargo stage known as the Earth Departure Stage; and a Lunar Lander vehicle that contains a descent stage, and ascent stage, and a habitation module. A variety of concurrent assorted ground operations infrastructure including software and facilities are also being developed, assorted technology and assembly designs and development for equipment such as EVA suits, life support systems, command and control technologies are also in the pipeline. The development is occurring in a distributed manner, with project deliverables being contributed by a large and diverse assortment of vendors and most space faring nations. Critical information about all of the components, software, and procedures must be shared during the DDT and E phases and then made readily available to the mission operations staff for access during the planning, preparation, and operations phases, and also need to be readily available for system to system interactions. The Constellation Data Systems Project (CxDS) is identifying the needs, and designing and deploying systems and processes to support these needs. This paper details the steps and processes that NASA is applying within the Constellation Program to manage this data and information, and to insure that the correct information is available, correctly annotated, and can be provisioned digitally to enhance response times, and support engineering analysis and anomaly resolution.

Brummett, Robert C.↗

The stirling engine for vehicle propulsion

The performance data of experimental Stirling engines are considered along with questions of exhaust-gas composition, engine noise, engine volume and weight, engine control, and the engine-starting process. The Stirling engine can use practically any liquid or gaseous fuel for its operation. It is found that technically a use of the Stirling engine in motor vehicles is feasible. Economic questions related to an introduction of the Stirling engine are discussed along with possible new developments which could improve the economic situation in favor of a use of Stirling engine.

Kuhlman, P.↗

Correlation of Cooling Data from an Air-Cooled Cylinder and Several Multicylinder Engines

The theory of engine-cylinder cooling developed in a previous report was further substantiated by data obtained on a cylinder from a Wright r-1820-g engine. Equations are presented for the average head and barrel temperatures of this cylinder as functions of the engine and the cooling conditions. These equations are utilized to calculate the variation in cylinder temperature with altitude for level flight and climb. A method is presented for correlating average head and barrel temperatures and temperatures at individual points on the head and the barrel obtained on the test stand and in flight. The method is applied to the correlation and the comparison of data obtained on a number of service engines. Data are presented showing the variation of cylinder temperature with time when the power and the cooling pressure drop are suddenly changed.

Pinkel, Benjamin↗

Engine systems analysis results of the Space Shuttle Main Engine redesigned powerhead initial engine level testing

Engineers regularly analyze SSME ground test and flight data with respect to engine systems performance. Recently, a redesigned SSME powerhead was introduced to engine-level testing in part to increase engine operational margins through optimization of the engine internal environment. This paper presents an overview of the MSFC personnel engine systems analysis results and conclusions reached from initial engine level testing of the redesigned powerhead, and further redesigns incorporated to eliminate accelerated main injector baffle and main combustion chamber hot gas wall degradation. The conclusions are drawn from instrumented engine ground test data and hardware integrity analysis reports and address initial engine test results with respect to the apparent design change effects on engine system and component operation.

Sander, Erik J.↗

Graph convolutional networks applied to unstructured flow field data

Abstract Many scientific and engineering processes produce spatially unstructured data. However, most data-driven models require a feature matrix that enforces both a set number and order of features for each sample. They thus cannot be easily constructed for an unstructured dataset. Therefore, a graph based data-driven model to perform inference on fields defined on an unstructured mesh, using a graph convolutional neural network (GCNN) is presented. The ability of the method to predict global properties from spatially irregular measurements with high accuracy is demonstrated by predicting the drag force associated with laminar flow around airfoils from scattered velocity measurements. The network can infer from field samples at different resolutions, and is invariant to the order in which the measurements within each sample are presented. The GCNN method, using inductive convolutional layers and adaptive pooling, is able to predict this quantity with a validation R 2 above 0.98, and a Normalized Mean Squared Error below 0.01, without relying on spatial structure.

Ogoke, Francis (ORCID:0000000224327783)↗

Development of Analysis Methods that Integrate Numeric and Textual Equipment Reliability Data

Within the Light Water Reactor Sustainability (LWRS) program, the Risk-Informed Systems Analysis (RISA) Pathway is performing collaborative research on the development and deployment of technologies designed to assist operating nuclear power plants (NPPs) to reduce operating costs improve plant reliability and availability. One of the RISA research areas is focusing on the development of methods and tools designed to optimize plant operations (e.g., maintenance/replacement schedules, optimal maintenance postures for plant structures, systems, and components [SSCs]) in a manner that is more cost effective than current approaches and makes better use of available SSC health data. The Risk-Informed Asset Management (RIAM) project targets this research area by creating a direct bridge between component equipment reliability (ER) data and system engineer decision making regarding maintenance activity scheduling and component aging management. In this respect, one challenge that NPP system engineers are facing is that the amount of ER data being continuously generated is not only extremely large in size, but it comes in different forms: textual (e.g., condition or maintenance reports) and numeric (e.g., generated by monitoring systems). All these data elements provide them with valuable insights and information regarding: 1) the discovery of anomalous behaviors or degradation trends, 2) the identification of the possible causes behind such behaviors/trends, and 3) the prediction of their direct consequences. However, several challenges have proved to be roadblocks to this process. While some of these challenges are technical in nature (i.e., data are often distributed over several physical servers/databases), others are conceptual in nature: data elements come in different formats (e.g., numeric or textual), and measured values have different scales (e.g., vibration spectra and oil temperature). The activities performed by the RIAM project during FY23 directly tackles the need to simultaneously integrate the analysis of ER data in all its forms, numeric and textual. Note that such task has never been performed before due to the complexity of the systems under consideration but, most importantly, because of the technical challenges behind the harmonization of ER data formats and the lack of adequate computational methods to analyze them. Our approach borrows ideas and concepts from the medical field where integration of several data sources is vital to assist medical practitioners to perform correct diagnosis and indicate optimal treatments. In our view a NPP asset is equivalent to a patient in a medical context. The main difference is the complexity of a human body is a magnitude more complex when compared to typical assets commonly present in NPPs (e.g., centrifugal pumps, or motor operated valves). This simplifies our first requirement when analyzing heterogenous ER data formats: to put data into “context”. Context is here intended as the additional piece of information that is needed by ER data analysis tools to understand what these data elements are referring to, i.e., which king of knowledge they are generating. In our context, this knowledge can be translated into models that capture the form and functional architecture of assets/systems, their dependencies, and how they interact. These models actually emulate the knowledge that that NPP system engineers possess about assets and systems; this is their key of success when analyzing ER data, their challenge is ability to handle large amount of data. Here, we employ model-based system engineering (MBSE) models of systems and assets to represent and capture their architecture and functional, i.e. cause-effect, relations. Then, ER data elements are processed by identifying first of all which elements of the developed MBSE elements they are referring to. For numeric ER data this task is fairly easy since it is possible to precisely pinpoint what MBSE elements the corresponding sensor are observing (e.g., bearing temperature of a centrifugal pump). Task is much harder for textual data since the information contained in issue or maintenance reports needs to “be understood” by a computational tool. Here we called this process as “knowledge extraction”. Once again, we borrow the experience in the medical field where methods to extract knowledge from textual data have been developed in the past decade. The missing element for us is the availability of a complete dictionary of NPP related concepts (in addition to the MBSE models presented earlier) that can put “text into context”. In FY23, such dictionary has been developed along with all the computational elements required for knowledge extraction. Lastly, once numeric and textual ER data elements have been processed and “understood”, then the last step is the discovery of possible cause-effect relations among them. This is performed by observing if a logical connection through the MBSE models exists, and if the

97 MATHEMATICS AND COMPUTING↗

Application of the Systematic Sensor Selection Strategy for Turbofan Engine Diagnostics

The data acquired from available system sensors forms the foundation upon which any health management system is based, and the available sensor suite directly impacts the overall diagnostic performance that can be achieved. While additional sensors may provide improved fault diagnostic performance there are other factors that also need to be considered such as instrumentation cost, weight, and reliability. A systematic sensor selection approach is desired to perform sensor selection from a holistic system-level perspective as opposed to performing decisions in an ad hoc or heuristic fashion. The Systematic Sensor Selection Strategy is a methodology that optimally selects a sensor suite from a pool of sensors based on the system fault diagnostic approach, with the ability of taking cost, weight and reliability into consideration. This procedure was applied to a large commercial turbofan engine simulation. In this initial study, sensor suites tailored for improved diagnostic performance are constructed from a prescribed collection of candidate sensors. The diagnostic performance of the best performing sensor suites in terms of fault detection and identification are demonstrated, with a discussion of the results and implications for future research.

Sowers, T. Shane↗

Application of the Systematic Sensor Selection Strategy for Turbofan Engine Diagnostics

The data acquired from available system sensors forms the foundation upon which any health management system is based, and the available sensor suite directly impacts the overall diagnostic performance that can be achieved. While additional sensors may provide improved fault diagnostic performance, there are other factors that also need to be considered such as instrumentation cost, weight, and reliability. A systematic sensor selection approach is desired to perform sensor selection from a holistic system-level perspective as opposed to performing decisions in an ad hoc or heuristic fashion. The Systematic Sensor Selection Strategy is a methodology that optimally selects a sensor suite from a pool of sensors based on the system fault diagnostic approach, with the ability of taking cost, weight, and reliability into consideration. This procedure was applied to a large commercial turbofan engine simulation. In this initial study, sensor suites tailored for improved diagnostic performance are constructed from a prescribed collection of candidate sensors. The diagnostic performance of the best performing sensor suites in terms of fault detection and identification are demonstrated, with a discussion of the results and implications for future research.

Sowers, T. Shane↗

The Mariner Venus Mercury flight data subsystem.

The flight data subsystem (FDS) discussed handles both the engineering and scientific measurements performed on the MVM'73. It formats the data into serial data streams, and sends it to the modulation/demodulation subsystem for transmission to earth or to the data storage subsystem for storage on a digital tape recorder. The FDS is controlled by serial digital words, called coded commands, received from the central computer sequencer of from the ground via the modulation/demodulation subsystem. The eight major blocks of the FDS are: power converter, timing and control, engineering data, memory, memory input/output and control, nonimaging data, imaging data, and data output. The FDS incorporates some 4000 components, weighs 17 kg, and uses 35 W of power. General data on the mission and spacecraft are given.

Whitehead, P. B.↗

Impeller flow field characterization with a laser two-focus velocimeter

Use of Computational Fluid Dynamics (CFD) codes, prevalent in the rocket engine turbomachinery industry, necessitates data of sufficient quality and quantity to benchmark computational codes. Existing data bases for typical rocket engine configurations, in particular impellers, are limited. In addition, traditional data acquisition methods have several limitations: typically transducer uncertainties are 0.5% of transducer full scale and traditional pressure probes are unable to provide flow characteristics in the circumferential (blade-to-blade) direction. Laser velocimetry circumvents these limitations by providing +0.5% uncertainty in flow velocity and +0.5% uncertainty in flow angle. The percent of uncertainty in flow velocity is based on the measured value, not full range capability. The laser electronics multiple partitioning capability allows data acquired between blades as the impeller rotates, to be analyzed separately, thus providing blade-to-blade flow characterization. Unlike some probes, the non-intrusive measurements made with the laser velocimeter does not disturb the flow. To this end,, and under Contract (NAS8-38864) to the National Aeronautics and Space Administration (NASA) at Marshall Space Flight Center (MSFC), an extensive test program was undertaken at Rocketdyne. Impellers from two different generic rocket engine pump configurations were examined. The impellers represent different spectrums of pump design: the Space Shuttle Main Engine (SSME) high pressure fuel turbopump (HPFTP) impeller was designed in the 1 1970's the Consortium for CFD application in Propulsion Technology Pump Stage Technology Team (Pump Consortium) optimized impeller was designed with the aid of modern computing techniques. The tester configuration for each of the impellers consisted of an axial inlet, an inducer, a diffuser, and a crossover discharge. While the tested configurations were carefully chosen to be representative of generic rocket engine pumps, several features of both testers were intentionally atypical. A crossover discharge, downstream of the impeller, rather than a volute discharge was used to minimize asymmetric flow conditions that might be reflected in the impeller discharge flow data. Impeller shroud wear ring radial clearances were purposely close to minimize leakage flow, thus increasing confidence in using the inlet data as an input to CFD programs. The empirical study extensively examined the flow fields of the two impellers via performance of laser two-focus velocimeter surveys in an axial plane upstream of the impellers and in multiple radial planes downstream of the impellers. Both studies were performed at the impeller design flow coefficients. Inlet laser surveys that provide CFD code inlet boundary conditions were performed in one axial plane, with ten radial locations surveyed. Three wall static pressures, positioned circumferentially around the impeller inlet, were used to identify asymmetrical pressure distributions in the inlet survey plane. The impeller discharge flow characterization consisted of three radial planes for the SSME HPFTP impeller and two radial planes for the Pump Consortium optimized impeller. Housing wall static pressures were placed to correspond to the radial locations surveyed with the laser velocimeter. Between five and thirteen axial stations across the discharge channel width were examined in each radial plane during the extensive flow mapping. The largely successful empirical flow characterization of two different impellers resulted in a substantial contribution to the limited existing data base, and yielded accurate data for CFD code benchmarking.

Brozowski, L. A.↗

Command and Control System Automated Testing

The Kennedy Space Center (KSC) has developed its own Command and Control System for the launch of the Space Launch System (SLS) and Orion capsule. The Command and Control System (CCS) is used by console engineers for the launch and system checkout of aerospace vehicles. The CCS allows console engineers to read data from the flight hardware on the launch pad and from the ground control systems and allows console engineers to issue commands, like opening a valve, to the flight hardware and ground control systems. The CCS needs to interact with thousands of devices and hardware controllers for the spacecraft and ground systems, receive data from these devices, distribute the data to console engineers in real-time, and allow console engineers to issue commands to manipulate hardware on the launch pad. The system needs to be robust, fault tolerant, responsive, and fast. In order to keep up with the pace of development of the CCS, a Test Automation System (TAS) is needed to validate the integrity of the system as a whole along with its individual components. Automated tests allow for faster development time, since tests can be ran through a Continuous Integration system and allow developers to check their code faster. Currently, the different modules, classes, and functions that make up the CCS are tested at the unit level, and the system level, with all the modules working together. My project was to implement a system for the data protocol layer of the Command Control System to be tested as a complete functional unit, with all of its classes and functions working together, but independent of the other modules of the CCS.

Automated TestingTest Automation↗