SEARCH · Search NASA

Results for “LOGIC 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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 757 records · Page 42

All sources NASA NTRS DOE OSTI

NASA NTRS1980

Computer program documentation D1FLTD to drive SINDA boundary nodes: User's guide

The thermal model correlation process begins when measured thermocouple data is available from the orbital flight tests of the shuttle. For this effort, it is necessary to convert some of the system improved numerical differencing analyzer (SINDA) diffusion or arithmetic nodes to boundary nodes and then drive these boundary nodes to the temperature profile of a flight measurement. An efficient way to provide this capability within the SINDA and OFT software systems is to provide a new SINDA routine, D1FLTD, for use in VARIABLES 1 of SINDA, to access the processed (word-addressable) orbital data reduction center flight data and store the appropriate measurement temperature in the desired SINDA temperature location. The ODRC flight data that is to be used for driving the boundary nodes must be assigned a logical unit number and must reside on a word-addressable file. The user must also provide two SINDA constants for the word positions of the first and last words of the temperature record for each measurement identifier (MID), i.e. each call to D1FLTD, used in the model. D1FLTD is then called from the VARIABLES 1 block to obtain the SINDA boundary node temperature for any MID on the file at any time point.

Damico, S. J.↗

NASA NTRS1980

Performance seeking controls

A performance logic algorithm (PSL) was developed to optimize the performance of propulsion systems for component and sensor degradations by monitoring the performance of the engine system and minimizing thrust specific fuel consumption (TSFC) while retaining a constant engine net thrust. Engine constraints such as surge margin, speed, pressure, and temperature are observed. The PSL algorithm was applied to the quiet, clean, short haul experimental engine. Engine control set points were modified for component degradations in order to restore the nominal net thrust. Results show convergence to the optimum value can be obtained within 60 to 90 seconds, which makes the program acceptable to on line operation with present state of the art minicomputers. Tests indicate that in most cases the PSL algorithm offers some improvement in thrust specific fuel consumption over the manual throttle.

Seldner, K.↗

NASA NTRS2002

Field-Programmable Gate Array Computer in Structural Analysis: An Initial Exploration

This paper reports on an initial assessment of using a Field-Programmable Gate Array (FPGA) computational device as a new tool for solving structural mechanics problems. A FPGA is an assemblage of binary gates arranged in logical blocks that are interconnected via software in a manner dependent on the algorithm being implemented and can be reprogrammed thousands of times per second. In effect, this creates a computer specialized for the problem that automatically exploits all the potential for parallel computing intrinsic in an algorithm. This inherent parallelism is the most important feature of the FPGA computational environment. It is therefore important that if a problem offers a choice of different solution algorithms, an algorithm of a higher degree of inherent parallelism should be selected. It is found that in structural analysis, an 'analog computer' style of programming, which solves problems by direct simulation of the terms in the governing differential equations, yields a more favorable solution algorithm than current solution methods. This style of programming is facilitated by a 'drag-and-drop' graphic programming language that is supplied with the particular type of FPGA computer reported in this paper. Simple examples in structural dynamics and statics illustrate the solution approach used. The FPGA system also allows linear scalability in computing capability. As the problem grows, the number of FPGA chips can be increased with no loss of computing efficiency due to data flow or algorithmic latency that occurs when a single problem is distributed among many conventional processors that operate in parallel. This initial assessment finds the FPGA hardware and software to be in their infancy in regard to the user conveniences; however, they have enormous potential for shrinking the elapsed time of structural analysis solutions if programmed with algorithms that exhibit inherent parallelism and linear scalability. This potential warrants further development of FPGA-tailored algorithms for structural analysis.

Singleterry, Robert C., Jr.↗

NASA NTRS1993

The Preliminary Design of a Universal Martian Lander

As part of the NASA/USRA program, nineteen West Virginia University students conducted a preliminary design of a manned Universal Martian Lander (UML). The WVU design considers descent to Mars from polar orbit, a six month surface stay, and ascent for rendezvous. The design begins with an unmanned UML landing at Elysium Mons followed by the manned UML landing nearby. During the six month surface stay, the eight modules are assembled to form a Martian base where scientific experiments are performed. The mission also incorporates hydroponic plant growth into a Controlled Ecological Life Support System (CELSS) for water recycling, food production, and to counteract psycho-logical effects of living on Mars. In situ fuel production for the Martian Ascent and Rendezvous Vehicle (MARV) is produced From gases in the Martian atmosphere. Following surface operations, the eight member crew uses the MARV to return to the Martian Transfer Vehicle (MTV) for the journey home to Earth.

Norman, Timothy L.↗

NASA NTRS1978

Photovoltaic design optimization for terrestrial applications

As part of the Jet Propulsion Laboratory's Low-Cost Solar Array Project, a comprehensive program of module cost-optimization has been carried out. The objective of these studies has been to define means of reducing the cost and improving the utility and reliability of photovoltaic modules for the broad spectrum of terrestrial applications. This paper describes one of the methods being used for module optimization, including the derivation of specific equations which allow the optimization of various module design features. The method is based on minimizing the life-cycle cost of energy for the complete system. Comparison of the life-cycle energy cost with the marginal cost of energy each year allows the logical plant lifetime to be determined. The equations derived allow the explicit inclusion of design parameters such as tracking, site variability, and module degradation with time. An example problem involving the selection of an optimum module glass substrate is presented.

Ross, R. G., Jr.↗

NASA NTRS1999

Roll-Out and Turn-Off Display Software for Integrated Display System

This report describes the software products, system architectures and operational procedures developed by Lockheed-Martin in support of the Roll-Out and Turn-Off (ROTO) sub-element of the Low Visibility Landing and Surface Operations (LVLASO) program at the NASA Langley Research Center. The ROTO portion of this program focuses on developing technologies that aid pilots in the task of managing the deceleration of an aircraft to a pre-selected exit taxiway. This report focuses on software that produces a system of redundant deceleration cues for a pilot during the landing roll-out, and presents these cues on a head up display (HUD). The software also produces symbology for aircraft operational phases involving cruise flight, approach, takeoff, and go-around. The algorithms and data sources used to compute the deceleration guidance and generate the displays are discussed. Examples of the display formats and symbology options are presented. Logic diagrams describing the design of the ROTO software module are also given.

Johnson, Edward J., Jr.↗

NASA NTRS1983

Transformations of software design and code may lead to reduced errors

The capability of programmers and non-programmers to specify problem solutions by developing example-solutions and also for the programmers by writing computer programs was investigated; each method of specification was accomplished at various levels of problem complexity. The level of difficulty of each problem was reflected by the number of steps needed by the user to develop a solution. Machine processing of the user inputs permitted inferences to be developed about the algorithms required to solve a particular problem. The interactive feedback of processing results led users to a more precise definition of the desired solution. Two participant groups (programmers and bookkeepers/accountants) working with three levels of problem complexity and three levels of processor complexity were used. The experimental task employed required specification of a logic for solution of a Navy task force problem.

Connelly, E. M.↗

NASA NTRS1987

Parallel software support for computational structural mechanics

The application of the parallel programming methodology known as the Force was conducted. Two application issues were addressed. The first involves the efficiency of the implementation and its completeness in terms of satisfying the needs of other researchers implementing parallel algorithms. Support for, and interaction with, other Computational Structural Mechanics (CSM) researchers using the Force was the main issue, but some independent investigation of the Barrier construct, which is extremely important to overall performance, was also undertaken. Another efficiency issue which was addressed was that of relaxing the strong synchronization condition imposed on the self-scheduled parallel DO loop. The Force was extended by the addition of logical conditions to the cases of a parallel case construct and by the inclusion of a self-scheduled version of this construct. The second issue involved applying the Force to the parallelization of finite element codes such as those found in the NICE/SPAR testbed system. One of the more difficult problems encountered is the determination of what information in COMMON blocks is actually used outside of a subroutine and when a subroutine uses a COMMON block merely as scratch storage for internal temporary results.

Jordan, Harry F.↗

NASA NTRS2013

Exploration Space Suit Architecture and Destination Environmental-Based Technology Development

This paper continues forward where EVA Space Suit Architecture: Low Earth Orbit Vs. Moon Vs. Mars1 left off in the development of a space suit architecture that is modular in design and could be reconfigured prior to launch or during any given mission depending on the tasks or destination. This paper addresses the space suit system architecture and technologies required based on human exploration (EVA) destinations, and describes how these systems should evolve to meet the future exploration EVA needs of the US human space flight program. A series of exercises and analyses provided a strong indication that the Constellation Program space suit architecture, with its maximum reuse of technology and functionality across a range of mission profiles and destinations, is postured to provide a viable solution for future space exploration missions. The destination environmental analysis demonstrates that the modular architecture approach could provide the lowest mass and mission cost for the protection of the crew, given any human mission outside of low-Earth orbit. Additionally, some of the high-level trades presented here provide a review of the environmental and non-environmental design drivers that will become increasingly important as humans venture farther from Earth. This paper demonstrates a logical clustering of destination design environments that allows a focused approach to technology prioritization, development, and design that will maximize the return on investment, largely independent of any particular design reference mission.

Hill, Terry R.↗

NASA NTRS1991

Utilization of common pressurized modules on the Space Station Freedom

During the preliminary design review of Space Station Freedom elements and subsystems, it was shown that reductions of cost, weight, and on-orbit integration and verification would be necessary in order to meet program constraints, particularly nominal Orbiter payload launch capability. At that time, the Baseline station consisted of four resource nodes and two 44 ft modules. In this study, the viability of a common module which maintains crew and payload accommodation is assessed. The size, transportation, and orientation of modules and the accommodation of system racks and user experiments are considered and compared to baseline. Based on available weight estimates, a module pattern consisting of six 28 ft. common elements with three radial and two end ports is shown to be nearly optimal. Advantageous characteristics include a reduction in assembly flights, dual egress from all elements, logical functional allocation, no adverse impacts to international partners, favorable airlock, cupola, ACRV (Assured Crew Return Vehicle), and logistics module accommodation, and desirable flight attitude and control characteristics.

Gould, Marston J.↗

NASA NTRS1991

Utilization of common pressurized modules on the Space Station Freedom

During the preliminary design review of Space Station Freedom elements and subsystems, it was shown that reductions of cost, weight, and on-orbit integration and verification would be necessary in order to meet program constraints, particularly nominal Orbiter payload launch capability. At that time, the Baseline station consisted of four resource nodes and two 44 ft modules. In this study, the viability of a common module which maintains crew and payload accommodation is assessed. The size, transportation, and orientation of modules and the accommodation of system racks and user experiments are considered and compared to baseline. Based on available weight estimates, a module pattern consisting of six 28 ft common elements with three radial and two end ports is shown to be nearly optimal. Advantageous characteristics include a reduction in assembly flights, dual egress from all elements, logical functional allocation, no adverse impacts to international partners, favorable airlock, cupola, ACRV (Assured Crew Return Vehicle), and logistics module accommodation, and desirable flight attitude and control characteristics.

Mazanek, Daniel D.↗

NASA NTRS2005

Data Fusion for Enhanced Aircraft Engine Prognostics and Health Management

Aircraft gas-turbine engine data is available from a variety of sources, including on-board sensor measurements, maintenance histories, and component models. An ultimate goal of Propulsion Health Management (PHM) is to maximize the amount of meaningful information that can be extracted from disparate data sources to obtain comprehensive diagnostic and prognostic knowledge regarding the health of the engine. Data fusion is the integration of data or information from multiple sources for the achievement of improved accuracy and more specific inferences than can be obtained from the use of a single sensor alone. The basic tenet underlying the data/ information fusion concept is to leverage all available information to enhance diagnostic visibility, increase diagnostic reliability and reduce the number of diagnostic false alarms. This report describes a basic PHM data fusion architecture being developed in alignment with the NASA C-17 PHM Flight Test program. The challenge of how to maximize the meaningful information extracted from disparate data sources to obtain enhanced diagnostic and prognostic information regarding the health and condition of the engine is the primary goal of this endeavor. To address this challenge, NASA Glenn Research Center, NASA Dryden Flight Research Center, and Pratt & Whitney have formed a team with several small innovative technology companies to plan and conduct a research project in the area of data fusion, as it applies to PHM. Methodologies being developed and evaluated have been drawn from a wide range of areas including artificial intelligence, pattern recognition, statistical estimation, and fuzzy logic. This report will provide a chronology and summary of the work accomplished under this research contract.

Volponi, Al↗

NASA NTRS2006

Systems Integration Processes for NASA's Crew Launch Vehicle

NASA's Exploration Initiative will require development of many new elements to constitute a robust system of systems. New launch vehicles are needed to place cargo and crew in stable low earth orbit. This paper examines the systems integration processes NASA is utilizing to ensure integration and control of propulsion and non-propulsion elements within NASA's Crew Launch Vehicle (CLV). The objective of the CLV is to provide the transportation capabilities to meet the Constellation Program requirements for delivering a Crew Exploration Vehicle (CEV) or other payload to Low Earth Orbit (LEO) in support of the lunar and Mars missions. The CLV must successfully provide the capability within cost and schedule with an acceptable risk approach. This paper will describe in detail the systems engineering management processes that will be applied to assure CLV Project success through complete and efficient technical integration. Discussion of specific processes for requirements development and verification, integrated design and analysis, integrated simulation and testing and the integration of reliability, maintainability and supportability (RMS) into the design will also be included. The CLV Project is broken logically into elements by the major hardware groupings, and associated management, system engineering, and integration functions. The processes to be described herein are designed to integrate within these CLV elements and among the other Constellation projects. Launch vehicle stack integration (CLV to CEV, and Ground and Flight Operations integration) throughout the life cycle, including integrated vehicle performance through orbital insertion, recovery of the first stage, and reentry of the upper stage will also be discussed. The processes for decomposing requirements to the Elements and ensuring that requirements have been correctly validated, decomposed, allocated, and that the verification requirements are properly defined to ensure that the system design meets requirements will be discussed.

Reuter, James L.↗

NASA NTRS2012

Security Data Warehouse Application

The Security Data Warehouse (SDW) is used to aggregate and correlate all JSC IT security data. This includes IT asset inventory such as operating systems and patch levels, users, user logins, remote access dial-in and VPN, and vulnerability tracking and reporting. The correlation of this data allows for an integrated understanding of current security issues and systems by providing this data in a format that associates it to an individual host. The cornerstone of the SDW is its unique host-mapping algorithm that has undergone extensive field tests, and provides a high degree of accuracy. The algorithm comprises two parts. The first part employs fuzzy logic to derive a best-guess host assignment using incomplete sensor data. The second part is logic to identify and correct errors in the database, based on subsequent, more complete data. Host records are automatically split or merged, as appropriate. The process had to be refined and thoroughly tested before the SDW deployment was feasible. Complexity was increased by adding the dimension of time. The SDW correlates all data with its relationship to time. This lends support to forensic investigations, audits, and overall situational awareness. Another important feature of the SDW architecture is that all of the underlying complexities of the data model and host-mapping algorithm are encapsulated in an easy-to-use and understandable Perl language Application Programming Interface (API). This allows the SDW to be quickly augmented with additional sensors using minimal coding and testing. It also supports rapid generation of ad hoc reports and integration with other information systems.

Vernon, Lynn R.↗

NASA NTRS2013

Exploration Space Suit Architecture and Destination Environmental-Based Technology Development

This paper continues forward where EVA Space Suit Architecture: Low Earth Orbit Vs. Moon Vs. Mars left off in the development of a space suit architecture that is modular in design and could be reconfigured prior to launch or during any given mission depending on the tasks or destination. This space suit system architecture and technologies required based on human exploration (EVA) destinations will be discussed, and how these systems should evolve to meet the future exploration EVA needs of the US human space flight program. A series of exercises and analyses provided a strong indication that the Constellation Program space suit architecture, with its maximum reuse of technology and functionality across a range of mission profiles and destinations, is postured to provide a viable solution for future space exploration missions. The destination environmental analysis demonstrates that the modular architecture approach could provide the lowest mass and mission cost for the protection of the crew, given any human mission outside of low-Earth orbit. Additionally, some of the high-level trades presented here provide a review of the environmental and nonenvironmental design drivers that will become increasingly important as humans venture farther from Earth. The presentation of destination environmental data demonstrates a logical clustering of destination design environments that allows a focused approach to technology prioritization, development, and design that will maximize the return on investment, largely independent of any particular design reference mission.

Hill, Terry R.↗

NASA NTRS2006

Systems Integration Processes for NASA Ares I Crew Launch Vehicle

NASA's Exploration Initiative will require development of many new elements to constitute a robust system of systems. New launch vehicles are needed to place cargo and crew in stable Low Earth Orbit (LEO). This paper examines the systems integration processes NASA is utilizing to ensure integration and control of propulsion and nonpropulsion elements within NASA's Crew Launch Vehicle (CLV), now known as the Ares I. The objective of the Ares I is to provide the transportation capabilities to meet the Constellation Program requirements for delivering a Crew Exploration Vehicle (CEV) or other payload to LEO in support of the lunar and Mars missions. The Ares I must successfully provide this capability within cost and schedule, and with an acceptable risk approach. This paper will describe the systems engineering management processes that will be applied to assure Ares I Project success through complete and efficient technical integration. Discussion of technical review and management processes for requirements development and verification, integrated design and analysis, integrated simulation and testing, and the integration of reliability, maintainability and supportability (RMS) into the design will also be included. The Ares I Project is logically divided into elements by the major hardware groupings, and associated management, system engineering, and integration functions. The processes to be described herein are designed to integrate within these Ares I elements and among the other Constellation projects. Also discussed is launch vehicle stack integration (Ares I to CEV, and Ground and Flight Operations integration) throughout the life cycle, including integrated vehicle performance through orbital insertion, recovery of the first stage, and reentry of the upper stage. The processes for decomposing requirements to the elements and ensuring that requirements have been correctly validated, decomposed, and allocated, and that the verification requirements are properly defined to ensure that the system design meets requirements, will be discussed.

Taylor, James L.↗

NASA NTRS2004

Development of an Information Fusion System for Engine Diagnostics and Health Management

Aircraft gas-turbine engine data are available from a variety of sources including on-board sensor measurements, maintenance histories, and component models. An ultimate goal of Propulsion Health Management (PHM) is to maximize the amount of meaningful information that can be extracted from disparate data sources to obtain comprehensive diagnostic and prognostic knowledge regarding the health of the engine. Data Fusion is the integration of data or information from multiple sources, to achieve improved accuracy and more specific inferences than can be obtained from the use of a single sensor alone. The basic tenet underlying the data/information fusion concept is to leverage all available information to enhance diagnostic visibility, increase diagnostic reliability and reduce the number of diagnostic false alarms. This paper describes a basic PHM Data Fusion architecture being developed in alignment with the NASA C17 Propulsion Health Management (PHM) Flight Test program. The challenge of how to maximize the meaningful information extracted from disparate data sources to obtain enhanced diagnostic and prognostic information regarding the health and condition of the engine is the primary goal of this endeavor. To address this challenge, NASA Glenn Research Center (GRC), NASA Dryden Flight Research Center (DFRC) and Pratt & Whitney (P&W) have formed a team with several small innovative technology companies to plan and conduct a research project in the area of data fusion as applied to PHM. Methodologies being developed and evaluated have been drawn from a wide range of areas including artificial intelligence, pattern recognition, statistical estimation, and fuzzy logic. This paper will provide a broad overview of this work, discuss some of the methodologies employed and give some illustrative examples.

Volponi, Allan J.↗

NASA NTRS1992

Support activities to maintain SUMS flight readiness

The Shuttle Upper Atmosphere Mass Spectrometer (SUMS), a component experiment of the NASA Orbital Experiments Program (OEX), was flown aboard the shuttle Columbia (OV102) mounted at the forward end of the nose landing gear well with an atmospheric gas inlet system fitted to the lower fuselage (chin panel) surface. The SUMS was designed to provide atmospheric data in flow regimes inaccessible prior to the development of the Space Transportation System (STS). The experiment mission operation began about one hour prior to shuttle de-orbit entry maneuver and continued until reaching 1.6 torr (about 86 km altitude). The SUMS mass spectrometer consists of the spare unit from the Viking mission to Mars. Bendix Aerospace under contract to NASA LaRC incorporated the Viking mass spectrometer, a microprocessor based logic card, a pressurized instrument case, and the University of Texas at Dallas provided a gas inlet system into a configuration suited to interface with the shuttle Columbia. The SUMS experiment underwent static and dynamic calibration as well as vacuum maintenance before and after STS 40 shuttle flight. The SUMS flew a total of 3 times on the space shuttle Columbia. Between flights the SUMS was maintained in flight ready status. The flight data has been analyzed by the NASA LaRC Aerothermodynamics Branch. Flight data spectrum plots and reports are presented in the Appendices to the Final Technical Report for NAS1-17399.

Wright, Willie↗