Search NASA⌕ Search

SEARCH · Search NASA

Results for “software concepts”

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 91 records · Page 5
All sourcesNASA NTRSDOE OSTI
NASA NTRS1978

The Seasat algorithm development facility at JPL

The Seasat-A spacecraft, scheduled for launch in May 1978, will produce a global ocean data set covering a one-year nominal mission. Because this is a proof-of-concept mission, data processing algorithms are expected to evolve as the data base grows. To support the evolution and evaluation of algorithms, and to experiment with various techniques for processing the data, an algorithm development facility (ADF) is being developing. The ADF will provide access to the data base and to highly modularized processing programs. The processing programs will be subject to easy and frequent modification by a remote user community of sensor managers and experiment teams, who will use this capability to evaluate the overall performance of the sensors and the algorithms using surface truth data. The ADF concepts of software standardization and interface control are expected to have general applicability for adaptive data processing systems.

Brown, J. W.↗
NASA NTRS1983

Glossary of Software Engineering Laboratory terms

A glossary of terms used in the Software Engineering Laboratory (SEL) is given. The terms are defined within the context of the software development environment for flight dynamics at the Goddard Space Flight Center. A concise reference for clarifying the language employed in SEL documents and data collection forms is given. Basic software engineering concepts are explained and standard definitions for use by SEL personnel are established.

Source record↗
NASA NTRS1984

Command and telemetry in autonomous spacecraft design

Some major steps are summarized in the evolution of autonomous design features for planetary exploration spacecraft. The control and data architectures for the Viking, Voyager, and Galileo spacecraft are considered. Telemetry and command capabilities are fundamental features of spacecraft design that have been successfully used for autonomous control. Also discussed is the Autonomous Redundancy and Maintenance Management Subsystem (ARMMS) concept. The software approach to autonomous control provides for modifications to the control process or the addition of new operating features during flight operations.

Turner, P. R.↗
NASA NTRS1987

The finite-difference time-domain (FD-TD) method for electromagnetic scattering and interaction problems

The formulation and recent applications of the finite-difference time-domain (FD-TD) method for the numerical modeling of electromagnetic scattering and interaction problems are considered. It is shown that improvements in FD-TD modeling concepts and software implementation often make it a preferable choice for structures which cannot be easily treated by conventional integral equations and asymptotic approaches. Recent FD-TD modeling validations in research areas including coupling to wires and wire bundles in free space and cavities, scattering from surfaces in relativistic motion, inverse scattering, and radiation condition theory, are reviewed. Finally, the advantages and disadvantages of FD-TD, and guidelines concerning when FD-TD should and should not be used in high-frequency electromagnetic modeling problems, are summarized.

Taflove, A.↗
NASA NTRS1987

Development of a graphical display on the DMS test bed

The DMS test bed is a model of a data network aboard space station. Users of the network share data relevant to the functional status of various systems aboard the station. Users may inquire the status of myriad sensors, obtaining reading of station subsystem status in real time via the Data Acquisition and Distribution Service. A graphical display of the status of a simulation of the Environmental Control and Life Support System was developed. Two broad issues were addressed: (1) flexible, extensible software design; and (2) the impact of utilizing standard processors, languages, and graphics packages implementing the software design concept. The experience gained with DEC hardware, the DEC implementation of the GKS graphics standard, and with Ada is summarized.

Donnelly, Robert A.↗
NASA NTRS1987

Expert system verification concerns in an operations environment

The Space Shuttle community is currently developing a number of knowledge-based tools, primarily expert systems, to support Space Shuttle operations. It is proposed that anticipating and responding to the requirements of the operations environment will contribute to a rapid and smooth transition of expert systems from development to operations, and that the requirements for verification are critical to this transition. The paper identifies the requirements of expert systems to be used for flight planning and support and compares them to those of existing procedural software used for flight planning and support. It then explores software engineering concepts and methodology that can be used to satisfy these requirements, to aid the transition from development to operations and to support the operations environment during the lifetime of expert systems. Many of these are similar to those used for procedural hardware.

Goodwin, Mary Ann↗
NASA NTRS1990

Facilitating researcher use of flight simulators

Researchers conducting experiments with flight simulators encounter numerous obstacles in bringing their ideas to the simulator. Research into how these simulators could be used more efficiently is presented. The study involved: (1) analyzing the Advanced Concepts Simulator software architecture, (2) analyzing the interaction between the researchers and simulation programmers, and (3) proposing a documentation tool for the researchers.

Russell, C. Ray↗
NASA NTRS1993

The systems engineering overview and process (from the Systems Engineering Management Guide, 1990)

The past several decades have seen the rise of large, highly interactive systems that are on the forward edge of technology. As a result of this growth and the increased usage of digital systems (computers and software), the concept of systems engineering has gained increasing attention. Some of this attention is no doubt due to large program failures which possibly could have been avoided, or at least mitigated, through the use of systems engineering principles. The complexity of modern day weapon systems requires conscious application of systems engineering concepts to ensure producible, operable and supportable systems that satisfy mission requirements. Although many authors have traced the roots of systems engineering to earlier dates, the initial formalization of the systems engineering process for military development began to surface in the mid-1950s on the ballistic missile programs. These early ballistic missile development programs marked the emergence of engineering discipline 'specialists' which has since continued to grow. Each of these specialties not only has a need to take data from the overall development process, but also to supply data, in the form of requirements and analysis results, to the process. A number of technical instructions, military standards and specifications, and manuals were developed as a result of these development programs. In particular, MILSTD-499 was issued in 1969 to assist both government and contractor personnel in defining the systems engineering effort in support of defense acquisition programs. This standard was updated to MIL-STD499A in 1974, and formed the foundation for current application of systems engineering principles to military development programs.

Source record↗
NASA NTRS1992

OASIS-CC presentation

The Operations and Science Instrument Support (OASIS) project is a long-term effort to help produce operations capabilities that can support space science missions of the next century. Portions of the OASIS concept in software have been implemented under the general name OASIS-R/T. OASIS-CC is the OASIS Command and Control, for monitoring and controlling science instruments and spacecraft during test, integration, launch and on-orbit operations. Viewgraphs are presented on the OASIS-CC functionality description, OASIS-CC support, and OASIS-CC as a tool.

Source record↗
NASA NTRS1993

Modeling and analysis of selected space station communications and tracking subsystems

The Communications and Tracking System on board Space Station Freedom (SSF) provides space-to-ground, space-to-space, audio, and video communications, as well as tracking data reception and processing services. Each major category of service is provided by a communications subsystem which is controlled and monitored by software. Among these subsystems, the Assembly/Contingency Subsystem (ACS) and the Space-to-Ground Subsystem (SGS) provide communications with the ground via the Tracking and Data Relay Satellite (TDRS) System. The ACS is effectively SSF's command link, while the SGS is primarily intended as the data link for SSF payloads. The research activities of this project focused on the ACS and SGS antenna management algorithms identified in the Flight System Software Requirements (FSSR) documentation, including: (1) software modeling and evaluation of antenna management (positioning) algorithms; and (2) analysis and investigation of selected variables and parameters of these antenna management algorithms i.e., descriptions and definitions of ranges, scopes, and dimensions. In a related activity, to assist those responsible for monitoring the development of this flight system software, a brief summary of software metrics concepts, terms, measures, and uses was prepared.

Richmond, Elmer Raydean↗
NASA NTRS1993

Synergistic control center development utilizing commercial technology and industry standards

The development of the Control Center Complex (CCC), a synergistic control center supporting both the Space Station Freedom and the Space Shuttle Program, is described. To provide maximum growth and flexibility, the CCC uses commercial off-the-shelf technology and industry standards. The discussion covers the development philosophy, CCC architecture, data distribution, the software platform concept, workstation platform, commercial tools for the CCC, and benefits of synergy.

Anderson, Brian L.↗
NASA NTRS1994

Baseline tests of an autonomous telerobotic system for assembly of space truss structures

Several proposed space missions include precision reflectors that are larger in diameter than any current or proposed launch vehicle. Most of these reflectors will require a truss structure to accurately position the reflector panels and these reflectors will likely require assembly in orbit. A research program has been conducted at the NASA Langley Research Center to develop the technology required for the robotic assembly of truss structures. The focus of this research has been on hardware concepts, computer software control systems, and operator interfaces necessary to perform supervised autonomous assembly. A special facility was developed and four assembly and disassembly tests of a 102-strut tetrahedral truss have been conducted. The test procedures were developed around traditional 'pick-and-place' robotic techniques that rely on positioning repeatability for successful operation. The data from two of the four tests were evaluated and are presented in this report. All operations in the tests were controlled by predefined sequences stored in a command file, and the operator intervened only when the system paused because of the failure of an actuator command. The tests were successful in identifying potential pitfalls in a telerobotic system, many of which would not have been readily anticipated or incurred through simulation studies. Addressing the total integrated task, instead of bench testing the component parts, forced all aspects of the task to be evaluated. Although the test results indicate that additional developments should be pursued, no problems were encountered that would preclude automated assembly in space as a viable construction method.

Rhodes, Marvin D.↗
NASA NTRS1996

Lunar Base Heat Pump

The objective of this project was to investigate the feasibility of constructing a heat pump suitable for use as a heat rejection device in applications such as a lunar base. In this situation, direct heat rejection through the use of radiators is not possible at a temperature suitable for lde support systems. Initial analysis of a heat pump of this type called for a temperature lift of approximately 378 deg. K, which is considerably higher than is commonly called for in HVAC and refrigeration applications where heat pumps are most often employed. Also because of the variation of the rejection temperature (from 100 to 381 deg. K), extreme flexibility in the configuration and operation of the heat pump is required. A three-stage compression cycle using a refrigerant such as CFC-11 or HCFC-123 was formulated with operation possible with one, two or three stages of compression. Also, to meet the redundancy requirements, compression was divided up over multiple compressors in each stage. A control scheme was devised that allowed these multiple compressors to be operated as required so that the heat pump could perform with variable heat loads and rejection conditions. A prototype heat pump was designed and constructed to investigate the key elements of the high-lift heat pump concept. Control software was written and implemented in the prototype to allow fully automatic operation. The heat pump was capable of operation over a wide range of rejection temperatures and cooling loads, while maintaining cooling water temperature well within the required specification of 40 deg. C +/- 1.7 deg. C. This performance was verified through testing.

Walker, D.↗
NASA NTRS1999

Recent Developments in Chemically Reactive Sensors for Propellants

Propellant system leaks can pose a significant hazard in aerospace operations. For example, a leak in the hydrazine supply system of the shuttle auxiliary power unit (APU) has resulted in hydrazine ignition and fire in the aft compartment of the shuttle. Sensors indicating the location of a leak could provide valuable information required for operational decisions. WSTF has developed a small, single-use sensor for detection of propellant leaks. The sensor is composed of a thermistor bead coated with a substance which is chemically reactive with the propellant. The reactive thermistor is one of a pair of closely located thermistors, the other being a reference. On exposure to the propellant, the reactive coating responds exothermically to it and increases the temperature of the coated-thermistor by several degrees. The temperature rise is sensed by a resistive bridge circuit, and an alarm is registered by data acquisition software. The concept is general and has been applied to sensors for hydrazine, monomethylhydrazine, unsym-dimethylhydrazine, ammonia, hydrogen peroxide, ethanol, and dinitrogen tetroxide. Responses of these sensors to humidity, propellant concentration, distance from the liquid leak, and ambient pressure levels arc presented. A multi-use sensor has also been developed for hydrazine based on its catalytic reactivity with noble metals.

Davis, Dennis D.↗
NASA NTRS2001

A Component-based Programming Model for Composite, Distributed Applications

The nature of scientific programming is evolving to larger, composite applications that are composed of smaller element applications. These composite applications are more frequently being targeted for distributed, heterogeneous networks of computers. They are most likely programmed by a group of developers. Software component technology and computational frameworks are being proposed and developed to meet the programming requirements of these new applications. Historically, programming systems have had a hard time being accepted by the scientific programming community. In this paper, a programming model is outlined that attempts to organize the software component concepts and fundamental programming entities into programming abstractions that will be better understood by the application developers. The programming model is designed to support computational frameworks that manage many of the tedious programming details, but also that allow sufficient programmer control to design an accurate, high-performance application.

Eidson, Thomas M.↗
NASA NTRS2010

NDARC-NASA Design and Analysis of Rotorcraft Theoretical Basis and Architecture

The theoretical basis and architecture of the conceptual design tool NDARC (NASA Design and Analysis of Rotorcraft) are described. The principal tasks of NDARC are to design (or size) a rotorcraft to satisfy specified design conditions and missions, and then analyze the performance of the aircraft for a set of off-design missions and point operating conditions. The aircraft consists of a set of components, including fuselage, rotors, wings, tails, and propulsion. For each component, attributes such as performance, drag, and weight can be calculated. The aircraft attributes are obtained from the sum of the component attributes. NDARC provides a capability to model general rotorcraft configurations, and estimate the performance and attributes of advanced rotor concepts. The software has been implemented with low-fidelity models, typical of the conceptual design environment. Incorporation of higher-fidelity models will be possible, as the architecture of the code accommodates configuration flexibility, a hierarchy of models, and ultimately multidisciplinary design, analysis and optimization.

Johnson, Wayne↗
NASA NTRS2015

Advanced Concept Modeling

Advanced Concepts Modeling software validation, analysis, and design. This was a National Institute of Aerospace contract with a lot of pieces. Efforts ranged from software development and validation for structures and aerodynamics, through flight control development, and aeropropulsive analysis, to UAV piloting services.

Chaput, Armand↗