Search NASA⌕ Search

SEARCH · Search NASA

Results for “programming systems”

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 631 records · Page 35

Off-line programming motion and process commands for robotic welding of Space Shuttle main engines

The off-line-programming software and hardware being developed for robotic welding of the Space Shuttle main engine are described and illustrated with diagrams, drawings, graphs, and photographs. The menu-driven workstation-based interactive programming system is designed to permit generation of both motion and process commands for the robotic workcell by weld engineers (with only limited knowledge of programming or CAD systems) on the production floor. Consideration is given to the user interface, geometric-sources interfaces, overall menu structure, weld-parameter data base, and displays of run time and archived data. Ongoing efforts to address limitations related to automatic-downhand-configuration coordinated motion, a lack of source codes for the motion-control software, CAD data incompatibility, interfacing with the robotic workcell, and definition of the welding data base are discussed.

Ruokangas, C. C.↗

Semantic Metrics for Object Oriented Design

The purpose of this proposal is to research a new suite of object-oriented (OO) software metrics, called semantic metrics, that have the potential to help software engineers identify fragile, low quality code sections much earlier in the development cycle than is possible with traditional OO metrics. With earlier and better Fault detection, software maintenance will be less time consuming and expensive, and software reusability will be improved. Because it is less costly to correct faults found earlier than to correct faults found later in the software lifecycle, the overall cost of software development will be reduced. Semantic metrics can be derived from the knowledge base of a program understanding system. A program understanding system is designed to understand a software module. Once understanding is complete, the knowledge-base contains digested information about the software module. Various semantic metrics can be collected on the knowledge base. This new kind of metric measures domain complexity, or the relationship of the software to its application domain, rather than implementation complexity, which is what traditional software metrics measure. A semantic metric will thus map much more closely to qualities humans are interested in, such as cohesion and maintainability, than is possible using traditional metrics, that are calculated using only syntactic aspects of software.

Etzkorn, Lethe↗

UAS-NAS Stakeholder Feedback Report

The need to fly UAS in the NAS to perform missions of vital importance to national security and defense, emergency management, science, and to enable commercial applications has been continually increasing over the past few years. To address this need, the NASA Aeronautics Research Mission Directorate (ARMD) Integrated Aviation Systems Program (IASP) formulated and funded the Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project (hereafter referred to as UAS‐NAS Project) from 2011 to 2016. The UAS‐NAS Project identified the following need statement: The UAS community needs routine access to the global airspace for all classes of UAS. The Project identified the following goal: To provide research findings to reduce technical barriers associated with integrating UAS into the NAS utilizing integrated system level tests in a relevant environment. This report provides a summary of the collaborations between the UAS-NAS Project and its primary stakeholders and how the Project applied and incorporated the feedback.

pilotless aircraft↗

Automatic system for computer program documentation

Work done on a project to design an automatic system for computer program documentation aids was made to determine what existing programs could be used effectively to document computer programs. Results of the study are included in the form of an extensive bibliography and working papers on appropriate operating systems, text editors, program editors, data structures, standards, decision tables, flowchart systems, and proprietary documentation aids. The preliminary design for an automated documentation system is also included. An actual program has been documented in detail to demonstrate the types of output that can be produced by the proposed system.

Simmons, D. B.↗

NASA university program management information system, FY 1986

The University Program Report provides current information and related statistics for approximately 4300 grants/contracts/cooperative agreements active during the report period. NASA Field centers and certain Headquarters Program Offices provide funds for those R&D activities in universities which contribute to the mission needs of that particular NASA element. This annual report is one means of documenting the NASA-university relationship, frequently denoted, collectively, as NASA's University Program.

Source record↗

NASA university program management information system, FY 1985

The University Program Report provides current information and related statistics for approximately 4200 grants/contracts/cooperative agreements active during the reporting period. NASA Field Centers and certain Headquarters Program Offices provide funds for those research and development activities in universities which contribute to the mission needs of that particular NASA element. This annual report is one means of documenting the NASA-University relationship, frequently denoted, collectively, as NASA's University Program.

Source record↗

NASA University program management information system, FY 1993

The University Program Report, Fiscal Year 1993, provides current information and related statistics for 7682 grants/contracts/cooperative agreements active during the report period. NASA field centers and certain Headquarters program offices provide funds for those R&D activities in universities which contribute to the mission needs of that particular NASA element. This annual report is one means of documenting the NASA-university relationship, frequently denoted, collectively, as NASA's University Program.

Source record↗

NASA university program management information system, FY 1994

The University Program report, Fiscal Year 1994, provides current information and related statistics for 7841 grants/contracts/cooperative agreements active during the reporting period. NASA field centers and certain Headquarters program offices provide funds for those activities in universities which contribute to the mission needs of that particular NASA element. This annual report is one means of documenting the NASA-university relationship, frequently denoted, collectively, as NASA's University Program.

Source record↗

NASA University Program Management Information System: FY 1995

The University Program Report, Fiscal Year 1995, provides current information and related statistics for grants/contracts/cooperative agreements active during the report period. NASA field centers and certain Headquarters program offices provide funds for those R&D activities in universities which contribute to the mission needs of that particular NASA element. This annual report is one means of documenting the NASA-university relationship, frequently denoted, collectively, as NASA's University Program.

Source record↗

Programming your way out of the past: ISIS and the META Project

The ISIS distributed programming system and the META Project are described. The ISIS programming toolkit is an aid to low-level programming that makes it easy to build fault-tolerant distributed applications that exploit replication and concurrent execution. The META Project is reexamining high-level mechanisms such as the filesystem, shell language, and administration tools in distributed systems.

Birman, Kenneth P.↗

An implementation of the distributed programming structural synthesis system (PROSSS)

A method is described for implementing a flexible software system that combines large, complex programs with small, user-supplied, problem-dependent programs and that distributes their execution between a mainframe and a minicomputer. The Programming Structural Synthesis System (PROSSS) was the specific software system considered. The results of such distributed implementation are flexibility of the optimization procedure organization and versatility of the formulation of constraints and design variables.

Rogers, J. L., Jr.↗

Applying the Transactive Systems Business Value Model to IRP

As part of the Transactive Systems Program at Pacific Northwest National Laboratory, a value modeling system was developed to support the evaluation of transactive systems. The technique is general enough to be applied outside transactive systems and to demonstrate this capability, a project was undertaken to use this value modeling technique as a means for modeling the valuation process undertaken by vertically integrated utilities when undergoing integrated resource planning (IRP). IRP is the process by which vertically integrated utilities (those that both serve customers directly as well as manage and run generation assets to do so) regularly go through to demonstrate to their regulators that they have a plan to meet the expected future load of their customers in a least cost and compliant manner. Traditionally this has been primarily an issue of how many and of which types of power plants to build but increasingly has included alternative measures such as demand response programs. Increasingly, environmental regulations play a significant role in both determine what types of power plants can be built under current regulations as well as what retrofits or upgrades need to be made to existing plants to allow them to continue to operate. Two use-case diagrams were constructed, one showing the showing the process by which IRP is carried out and another showing how a vertically integrated utility procures the resources it requires to meet load now and in the future. These diagrams help clarify the difference and provide a high-level outline of the two processes. A class diagram was constructed to clearly define the types of actors that would be considered in this model and the relationships between them. This diagram tacitly indicates which types of actors are and are not included in the model which provides significant guidance in defining the scope of the model. The relationship between the classes/actors provides further indication of what areas of the model have higher levels of detail and by implication bear more significance in modeling the system. Using the classes/actors defined in the class diagram, a business value diagram was constructed that defines the key value streams exchanged between the actors. This diagram provides a clear expression of the business case of the vertically integrated utility and who its counterparties are during the process of meeting load. These value streams have not only to do with meeting the load but doing so in a manner that meets environmental regulations. Increasingly, IRPs have three key metrics to evaluate a given plant to meet load: net present value of revenue required, emissions, and renewable energy credits. From this business value diagram, more detailed activity diagrams were formed that focus on a few of the key value stream exchanges, showing the process by which each party accrues value. These diagrams provide insight into the timing and sequence of the interactions in a way that the business value diagrams did not. The transactive value model was found to be highly compatible with IRP and provided a clear, simple model of the analysis done during IRP and key metrics driving IRP decisions. In particular it highlighted a few key items that may or may not have been as clear prior to the development of the model. Specifically, the role of the environmental regulations has become increasingly important and two of the three key metrics by which IRPs are typically evaluated are environmentally focused. Additionally, though generally not acknowledged, the role of the investor was included in this model as they are an essential source of capital in building new power plants and cannot be ignored when defining the business case of the vertically integrated utility.

24 POWER TRANSMISSION AND DISTRIBUTION↗

PLSS 2.5 Fan Design and Development

NASA is building a high fidelity prototype of an advanced portable life support system (PLSS) as part of the Advanced Exploration Systems Program. This new PLSS, designated as PLSS 2.5, will advance component technologies and systems knowledge in order to inform a future flight program. The oxygen ventilation loop of its predecessor, PLSS 2.0, is driven by a centrifugal fan developed using specifications from over five years ago. PLSS technology and system parameters have matured to the point where the existing fan will not perform adequately for the new prototype. In addition, areas of potential improvement have been identified with the existing fan that could be addressed in a new design. As a result, a new fan was designed and tested for the PLSS 2.5. The PLSS 2.5 fan is a derivative of the one used in PLSS 2.0. It uses the same basic non-metallic can around the motor, but with a larger volute and impeller to meet the higher pressure drop requirements of the PLSS 2.5 loop. This allows it to operate at rotational speeds that are matched to rolling element bearings, and which create reasonably low impeller tip speeds. Development of the fan also considered a shrouded impeller design that allows larger clearances for greater oxygen safety and better performance.

Converse, David↗

A Management Information System Model for Program Management

The development of a model to simulate the information system of a program management type of organization is reported. The model statistically determines the following parameters: type of messages, destinations, delivery durations, type processing, processing durations, communication channels, outgoing messages, and priorites. The total management information system of the program management organization is considered, including formal and informal information flows and both facilities and equipment. The model is written in General Purpose System Simulation 2 computer programming language for use on the Univac 1108, Executive 8 computer. The model is simulated on a daily basis and collects queue and resource utilization statistics for each decision point. The statistics are then used by management to evaluate proposed resource allocations, to evaluate proposed changes to the system, and to identify potential problem areas. The model employs both empirical and theoretical distributions which are adjusted to simulate the information flow being studied.

Shipman, D. L.↗

Design and development of a passive propellant management system

This paper describes the passive propellant management system program being conducted for the NASA-Marshall Space Flight Center. The objectives of this program are to design and develop a hydrazine propellant acquisition system which will acquire propellant in low- or zero-g environments and also retain this propellant under high axially directed accelerations that may be experienced during launch and orbit-to-orbit transfer. The system design requirements were established to satisfy requirements for a large number of potential NASA and military applications, such as orbit-to-orbit shuttles and satellite vehicles. The resulting concept is a multicompartmented tank with independent surface-tension acquisition channels in each compartment. The tank is designed to provide greater than 98% expulsion efficiency when subjected to the simultaneous requirements of acceleration, vibration, and outflow usage. The system design has the unique capability to demonstrate low-g performance in a one-g test environment, and the test program has been structured around this capability.

Regnier, W. W.↗

Extreme Heterogeneity 2018 - Productive Computational Science in the Era of Extreme Heterogeneity: Report for DOE ASCR Workshop on Extreme Heterogeneity

The 2018 Basic Research Needs Workshop on Extreme Heterogeneity identified five Priority Research Directions for realizing the capabilities needed to address the challenges posed in this era of rapid technological change. This report captures the outcomes of that workshop. In the context of extreme heterogeneity, it defines basic research needs and opportunities in computer science research to develop smart and trainable operating and runtime systems, programming environments, and predictive tools that will make future systems easier to adapt to scientists’ computing needs and easier for facilities to deploy securely.

97 MATHEMATICS AND COMPUTING↗

Systems analysis - Key to NASA's data system planning

Critical steps in the systems analysis process for NASA's data system planning are: (1) compilation of future user/mission requirements, (2) development of alternative overall data system concepts which satisfy requirements, (3) assessment of future development and availability of data system technology, and (4) cost/performance tradeoff studies of the alternative concepts for systems optimization. Tasks within the NEEDS (NASA End-to-End Data System) Program, which correspond to the critical steps in this systems analysis process are examined.

Nelson, R. W.↗