Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “engineering software”

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,657 records · Page 92
All sourcesNASA NTRSDOE OSTI
NASA NTRS1976

IPCS implications for future supersonic transport aircraft

The Integrated Propulsion Control System (IPCS) demonstrates control of an entire supersonic propulsion module - inlet, engine afterburner, and nozzle - with an HDC 601 digital computer. The program encompasses the design, build, qualification, and flight testing of control modes, software, and hardware. The flight test vehicle is an F-111E airplane. The L.H. inlet and engine will be operated under control of a digital computer mounted in the weapons bay. A general description and the current status of the IPCS program are given.

Billig, L. O.↗
NASA NTRS1992

Software support for irregular and loosely synchronous problems

A large class of scientific and engineering applications may be classified as irregular and loosely synchronous from the perspective of parallel processing. We present a partial classification of such problems. This classification has motivated us to enhance FORTRAN D to provide language support for irregular, loosely synchronous problems. We present techniques for parallelization of such problems in the context of FORTRAN D.

Choudhary, A.↗
NASA NTRSDate not supplied

TechEd Sat-11 Cognitive Engine-1 Experiments

This presentation discusses the experiment concept of operations, flight and ground software, and current status of Technology Educational Satellite 11 (TechEdSat-11).

Rachel Dudukovich↗
NASA NTRS1996

Knowledge Engineering for Preservation and Future use of Institutional Knowledge

This Project has two main thrusts-preservation of special knowledge and its useful representation via computers. NASA is losing the expertise of its engineers and scientists who put together the great missions of the past. We no longer are landing men on the moon. Some of the equipment still used today (such as the RL-10 rocket) was designed decades ago by people who are now retiring. Furthermore, there has been a lack, in some areas of technology, of new projects that overlap with the old and that would have provided opportunities for monitoring by senior engineers of the young ones. We are studying this problem and trying out a couple of methods of soliciting and recording rare knowledge from experts. One method is that of Concept Maps which produces a graphical interface to knowledge even as it helps solicit that knowledge. We arranged for experienced help in this method from John Coffey of the Institute of Human and Machine Technology at the University of West Florida. A second method which we plan to try out in May, is a video-taped review of selected failed missions (e.g., the craft tumbled and blew up). Five senior engineers (most already retired from NASA) will, as a team, analyze available data, illustrating their thought processes as they try to solve the problem of why a space craft failed to complete its mission. The session will be captured in high quality audio and with at least two video cameras. The video can later be used to plan future concept mapping interviews and, in edited form, be a product in itself. Our computer representations of the amassed knowledge may eventually, via the methods of expert systems, be joined with other software being prepared as a suite of tools to aid future engineers designing rocket engines. In addition to representation by multimedia concept maps, we plan to consider linking vast bodies of text (and other media) by hypertexting methods.

Moreman, Douglas↗
NASA NTRS2004

SCDM in a Distributed Environment

The Software Configuration Management (SCM) of the Space Launch Initiative (SLI) Advanced Engineering Environment (AEE) products is performed in a distributed environment-meaning the activities performed during the project lifecycle are across numerous NASA Centers, facilities, organizations, colleges and industry. SCM is the glue that holds the project and products together-especially in a distributed environment. It identifies, controls, accounts, and verified the details of the products; the schedule of activities; the assigned responsibilities; and the required resources, including staff, tools, and computer facilities. Data/document management (DM) captures and conveys the SCM and project efforts. SCM and DM are integrally linked; hence, Software Configuration and Data Management (SCDM). This paper discusses one team's challenges in implementing SCDM in a distributed environment. The distributed nature of the project introduces new opportunities for moving SCDM to the next level of usefulness in today's high-tech development arena. The lessons learned from the implementation of distributed SCDM in support of the SLI AEE Project provide valuable information for future implementations of SCM and DM.

Crowley, Sandra L.↗
NASA NTRS2015

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 NTRS1995

A Systems Engineering Approach to the Analysis of a Planetary Mission Ground System in Terms of Science Objectives

The most fundamental objective of all planetary missions is to return data. To accomplish this, a spacecraft is fabricated and built, software is planned and coded, and a ground system is designed and implemented. However, a systems engineering approach to determine how the collection of data drives ground system capabilities has received little attention.This paper defines a technique by which science objectives can be quantitatively evaluated. For illustrative purposes, it will be applied to NASA's Cassini Mission. This mission, to be launched in 1997, is an international endeavor designed to orbit Saturn for four years.The results of this systems engineering approach will show which science objectives drive specific ground system capabilities. In addition, this technique can assist system engineers in the selection of the science payload during pre-project mission planning; ground system designers during ground system development and implementation; and operations personnel during the mission.

systems engineering, ground systems↗
NASA NTRS2008

Applied Space Systems Engineering: Manage Technical Data - Chapter 17

Effective space systems engineering (SSE) is conducted in a fully electronic manner. Competitive hardware, software, and system designs are created in a totally digital environment that enables rapid product design and manufacturing cycles, as well as a multitude of techniques such as modeling, simulation, and lean manufacturing that significantly reduce the lifecycle cost of systems. Because the SSE lifecycle depends on the digital environment, managing the enormous volumes of technical data needed to describe, build, deploy, and operate systems is a critical factor in the success of a project. This chapter presents the key aspects of Technical Data Management (TDM) within the SSE process. It is written from the perspective of the System Engineer tasked with establishing the TDM process and infrastructure for a major project. Additional perspectives are reflected from the point of view of the engineers on the project who work within the digital engineering environment established by the TDM toolset and infrastructure, and from the point of view of the contactors who interface via the TDM infrastructure. Table 17.1 lists the TDM process as it relates to SSE.

Kent, Peter↗
NASA NTRS2016

Space Launch System Vibration Analysis Support

The ultimate goal for my efforts during this internship was to help prepare for the Space Launch System (SLS) integrated modal test (IMT) with Rodney Rocha. In 2018, the Structural Engineering Loads and Dynamics Team will have 10 days to perform the IMT on the SLS Integrated Launch Vehicle. After that 10 day period, we will have about two months to analyze the test data and determine whether the integrated vehicle modes/frequencies are adequate for launching the vehicle. Because of the time constraints, NASA must have newly developed post-test analysis methods proven well and with technical confidence before testing. NASA civil servants along with help from rotational interns are working with novel techniques developed and applied external to Johnson Space Center (JSC) to uncover issues in applying this technique to much larger scales than ever before. We intend to use modal decoupling methods to separate the entangled vibrations coming from the SLS and its support structure during the IMT. This new approach is still under development. The primary goal of my internship was to learn the basics of structural dynamics and physical vibrations. I was able to accomplish this by working on two experimental test set ups, the Simple Beam and TAURUS-T, and by doing some light analytical and post-processing work. Within the Simple Beam project, my role involves changing the data acquisition system, reconfiguration of the test set up, transducer calibration, data collection, data file recovery, and post-processing analysis. Within the TAURUS-T project, my duties included cataloging and removing the 30+ triaxial accelerometers, coordinating the removal of the structure from the current rolling cart to a sturdy billet for further testing, preparing the accelerometers for remounting, accurately calibrating, mounting, and mapping of all accelerometer channels, and some testing. Hammer and shaker tests will be performed to easily visualize mode shapes at low frequencies. Short analytical projects using MATLAB were also assigned to aid in research efforts. These included integration of acceleration data for comparison to measured displacement data. Laplace and Fourier transforms were also investigated to determine viability as a method of modal decoupling. In addition to these projects, I was also able contribute work that would benefit future interns and the division as a whole. I gave a short presentation and answered questions to aid in the recruitment of subsequent interns and co-ops for the division. I also assisted in revisions and additions to Intern/Co-Op Handbook to provide incoming employees with background information on the organization they are about to work for. I further developed tutorial on Pulse software, which was used for data acquisition for both experiments and will be helpful to interns and engineers that may be unfamiliar to the software. I gained a diverse range of experience throughout my internship. I was introduced to advanced dynamics and analytical techniques. This was through new experience with both hands on experimentation and analytical post processing methods. I was exposed to the benefits of interdepartmental collaboration and developed stronger skills in time management by coordinating two different tests at once. This internship provided an excellent opportunity to see how engineering theories applied to real life scenarios, and an introduction to how NASA/JSC solves technical problems.

Johnson, Katie↗
NASA NTRS2015

Fault Management Architectures and the Challenges of Providing Software Assurance

The satellite systems 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 is system complexity due to a need to establish a multi-dimensional structure across hardware, software and operations. This structure is necessary to identify and respond to system faults, mitigate technical risks and ensure operational continuity. These 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 (VV) is challenging. A breakout session at the 2012 NASA Independent Verification Validation (IVV) Annual Workshop titled VV of Fault Management: Challenges and Successes exposed these issues in terms of VV for a representative set of architectures. NASA's IVV is funded by NASA's Software Assurance Research Program (SARP) in partnership with NASA's Jet Propulsion Laboratory (JPL) to extend the work performed at the Workshop session. NASA IVV will extract FM architectures across the IVV portfolio and evaluate the data set for robustness, assess visibility for validation and test, and define software assurance methods that could be applied to the various architectures and designs. This work focuses efforts on FM architectures from critical and complex projects within NASA. The identification of particular FM architectures, visibility, and associated VVIVV techniques provides a data set that can enable higher assurance that a satellite 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 satellite community. This paper discusses the approach taken to perform the evaluations and preliminary findings from the research including identification of FM architectures, visibility observations, and methods utilized for VVIVV.

Fault Management↗
NASA NTRS2011

The Effects of Propellant Slosh Dynamics on the Solar Dynamics Observatory

The Solar Dynamics Observatory (SDO) mission, which is part of the Living With a Star program, was successfully launched and deployed from its Atlas V launch vehicle on February 11, 2010. SDO is an Explorer-class mission now operating in a geosynchronous orbit (GEO). The basic mission is to observe the Sun for a very high percentage of the 5-year mission (10-year goal) with long stretches of uninterrupted observations and with constant, high-data-rate transmission to a dedicated ground station located in White Sands, New Mexico. A significant portion of SDO's launch mass was propellant, contained in two large tanks. To ensure performance with this level of propellant, a slosh analysis was performed. This paper provides an overview of the SDO slosh analysis, the on-orbit experience, and the lessons learned. SDO is a three-axis controlled, single fault tolerant spacecraft. The attitude sensor complement includes sixteen coarse Sun sensors, a digital Sun sensor, three two-axis inertial reference units, two star trackers, and four guide telescopes. Attitude actuation is performed either using four reaction wheels or eight thrusters, depending on the control mode, along with single main engine which nominally provides velocity-change thrust. The attitude control software has five nominal control modes: three wheel-based modes and two thruster-based modes. A wheel-based Safehold running in the Attitude Control Electronics (ACE) box improves the robustness of the system as a whole. All six modes are designed on the same basic proportional-integral-derivative attitude error structure, with more robust modes setting their integral gains to zero. To achieve and maintain a geosynchronous orbit for a 2974-kilogram spacecraft in a cost effective manner, the SDO team designed a high-efficiency propulsive system. This bi-propellant design includes a 100-pound-force main engine and eight 5-pound-force attitude control thrusters. The main engine provides high specific impulse for the maneuvers to attain GEO, while the smaller Attitude Control System (ACS) thrusters manage the disturbance torques of the larger main engine and provide the capability for much smaller orbit adjustment burns. SDO's large solar profile produces a large solar torque disturbance and momentum buildup. This buildup drives the frequency of momentum unloads via ACS thrusters. SDO requires 1409 kilograms (which is approximately half the launch mass) of propellant to achieve and maintain the GEO orbit while performing the momentum unloads for 10 years.

Mason, Paul↗
NASA NTRS1981

Structure of the knowledge base for an expert labeling system

One of the principal objectives of the NASA AgRISTARS program is the inventory of global crop resources using remotely sensed data gathered by Land Satellites (LANDSAT). A central problem in any such crop inventory procedure is the interpretation of LANDSAT images and identification of parts of each image which are covered by a particular crop of interest. This task of labeling is largely a manual one done by trained human analysts and consequently presents obstacles to the development of totally automated crop inventory systems. However, development in knowledge engineering as well as widespread availability of inexpensive hardware and software for artificial intelligence work offers possibilities for developing expert systems for labeling of crops. Such a knowledge based approach to labeling is presented.

Rajaram, N. S.↗
NASA NTRS1984

Preliminary flight test results of the F100 EMD engine in an F-15 airplane

A flight evaluation of the F100 Engine Model Derivative (EMD) is conducted. The F100 EMD is an advanced version of the F100 engine that powers the F15 and F16 airplanes. The F100 EMD features a bigger fan, higher temperature turbine, a Digital Electronic Engine Control system (DEEC), and a newly designed 16 segment afterburner, all of which results in a 15 to 20 percent increase in sea level thrust. The flight evaluations consist of investigation of performance (thrust, fuel flow, and airflow) and operability (transient response and airstart) in the F-15 airplane. The performance of the F100 EMD is excellent. Aircraft acceleration time to Mach 2.0 is reduced by 23 percent with two F100 EMD engines. Several anomalies are discovered in the operability evaluations. A software change to the DEEC improved the throttle, and subsequent Cooper Harper ratings of 3 to 4 are obtained. In the extreme upper left hand corner of the flight enveloped, compressor stalls occurr when the throttle is retarded to idle power. These stalls are not predicted by altitude facility tests or stability for the compressor.

Myers, L. P.↗
NASA NTRS1985

Research in computer science

Synopses are given for NASA supported work in computer science at the University of Virginia. Some areas of research include: error seeding as a testing method; knowledge representation for engineering design; analysis of faults in a multi-version software experiment; implementation of a parallel programming environment; two computer graphics systems for visualization of pressure distribution and convective density particles; task decomposition for multiple robot arms; vectorized incomplete conjugate gradient; and iterative methods for solving linear equations on the Flex/32.

Ortega, J. M.↗
NASA NTRS1985

Instrument Systems Analysis and Verification Facility (ISAVF) users guide

The ISAVF facility is primarily an interconnected system of computers, special purpose real time hardware, and associated generalized software systems, which will permit the Instrument System Analysts, Design Engineers and Instrument Scientists, to perform trade off studies, specification development, instrument modeling, and verification of the instrument, hardware performance. It is not the intent of the ISAVF to duplicate or replace existing special purpose facilities such as the Code 710 Optical Laboratories or the Code 750 Test and Evaluation facilities. The ISAVF will provide data acquisition and control services for these facilities, as needed, using remote computer stations attached to the main ISAVF computers via dedicated communication lines.

Davis, J. F.↗
NASA NTRS1985

Component-specific modeling

Accomplishments are described for the second year effort of a 3-year program to develop methodology for component specific modeling of aircraft engine hot section components (turbine blades, turbine vanes, and burner liners). These accomplishments include: (1) engine thermodynamic and mission models; (2) geometry model generators; (3) remeshing; (4) specialty 3-D inelastic stuctural analysis; (5) computationally efficient solvers, (6) adaptive solution strategies; (7) engine performance parameters/component response variables decomposition and synthesis; (8) integrated software architecture and development, and (9) validation cases for software developed.

Mcknight, R. L.↗
NASA NTRS1985

Modular digital holographic fringe data processing system

A software architecture suitable for reducing holographic fringe data into useful engineering data is developed and tested. The results, along with a detailed description of the proposed architecture for a Modular Digital Fringe Analysis System, are presented.

Downward, J. G.↗
NASA NTRS1988

Successful completion of a cyclic ground test of a mercury ion auxiliary propulsion system

An engineering model Ion Auxiliary Propulsion System (IAPS) 8-cm thruster (S/N 905) has completed a life test at NASA Lewis Research Center. The mercury ion thruster successfully completed and exceeded the test goals of 2557 on/off cycles and 7057 hr of operation at full thrust. The final 1200 cycles and 3600 hr of the life test were conducted using an engineering model of the IAPS power electronics unit (PEU) and breadboard digital controller and interface unit (DCIU). This portion of the test is described in this paper with a charted history of thruster operating parameters and off-normal events. Performance and operating characteristics were constant throughout the test with only minor variations. The engineering model power electronics unit operated without malfunction; the flight software in the digital controller and interface unit was exercised and verified. Post-test inspection of the thruster revealed facility enhanced accelerator grid erosion but overall the thruster was in good condition. It was concluded that the thruster performance was not drastically degraded by time or cycles. Additional cyclic testing is currently under consideration.

Francisco, David R.↗