Search NASA⌕ Search

SEARCH · Search NASA

Results for “program implementation”

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 613 records · Page 34
All sourcesNASA NTRSDOE OSTI
NASA NTRS2020

History and Logic Model NASA Goddard Space Flight Center Instrument and Payload Systems Engineering Technical Performance Study

Historically, some NASA missions have exceeded schedule and cost commitments. Studies suggest technical performance is a contributor. The 1980 NASA Project Management Study concluded, "one of the most significant contributors to cost and schedule growth is inadequate definition of technical and management aspects of a program..." (as cited in GAO/NSIAD-93-97, p. 11). The 1991 NASA Roles and Missions Report identified a "need for increased emphasis on technological readiness and requirements on the front end of a program" (as cited in GAO/NSIAD-93-97, p. 11). The 1992 NASA Program Costs Report stated that NASA officials identified, among other things, "insufficient definition studies... [and] program redesigns and technical complexities" as reasons for cost and schedule overruns (GAO/NSAID-93-97, p. 11). The 2002 Task Force on Acquisition of National Security Space Programs found "requirements definition and control issues, unhealthy cost bias in proposal evaluation, widespread lack of budget reserves required to implement high risk programs on schedule, and an overall underappreciation of the importance of appropriately staffed and trained system engineering staff to manage the technologically demanding and unique aspects of space programs" (DoD, 2003, p.i.) In 2007, The NASA Office of the Chief Engineer chartered the NASA Instrument Capability Study (NICS) “to determine whether NASA instrument developers are facing challenges that impact the capability to design and build quality instruments or whether there are flaws in the acquisition strategy evidenced by schedule delays, cost overruns, and increased technical risk via design deficiencies. The... team was also chartered to determine if occurrences [are]... isolated cases or if there are generic issues... If the issues [are] found to be generic, the team [is] to offer solutions to recover such capability" (NICS Report, 2008, p. vi). The 2008 NICS Report, led by Goddard Space Flight Center (GSFC), identified challenges to instrument technical performance consistent with findings from previous reports. In 2017, the Instrument Project Division (IPD) Implementation Study was initiated to determine if there was a change in meeting schedule and cost commitments after implementing certain NICS recommendations. In 2018, the Instrument Technical Performance Study was initiated to determine the current state of Instrument Technical Performance in the GSFC Payload & Instrument Systems Engineering Branch. The purpose of the combined studies is to answer the question, "Is there a relationship between meeting NASA scientific instrument technical success and meeting schedule and cost commitments? If yes, what is the relationship?" References Department of Defense Office of the Under Secretary of Defense for Acquisition, Technology, and Logistics. (2003). The report of the defense science board/ air force scientific advisory board joint task force on acquisition of national security space programs. Washington DC. Government Accounting Office. (1992). NASA program costs: Space missions require substantially more funding than initially estimated. GAO/NSIAD-93-97. Washington DC. National Aeronautics and Space Administration, National Oceanic and Atmospheric Agency, Department of Defense. (2008). The NASA instrument capability study final report. NP-2008-11-058-GSFC. Washington DC.

Robbins, Geraldine↗
NASA NTRS2014

The Impact of Apollo-Era Microbiology on Human Space Flight

The microbiota of crewmembers and the spacecraft environment contributes significant risk to crew health during space flight missions. NASA reduces microbial risk with various mitigation methods that originated during the Apollo Program and continued to evolve through subsequent programs: Skylab, Shuttle, and International Space Station (ISS). A quarantine of the crew and lunar surface samples, within the Lunar Receiving Laboratory following return from the Moon, was used to prevent contamination with unknown extraterrestrial organisms. The quarantine durations for the crew and lunar samples were 21 days and 50 days, respectively. A series of infections among Apollo crewmembers resulted in a quarantine before launch to limit exposure to infectious organisms. This Health Stabilization Program isolated the crew for 21 days before flight and was effective in reducing crew illness. After the program developed water recovery hardware for Apollo spacecraft, the 1967 National Academy of Science Space Science Board recommended the monitoring of potable water. NASA implemented acceptability limits of 10 colony forming units (CFU) per mL and the absence of viable E. coli, anaerobes, yeasts, and molds in three separate 150 mL aliquots. Microbiological investigations of the crew and spacecraft environment were conducted during the Apollo program, including the Apollo-Soyuz Test Project and Skylab. Subsequent space programs implemented microbial screening of the crew for pathogens and acceptability limits on spacecraft surfaces and air. Microbiology risk mitigation methods have evolved since the Apollo program. NASA cancelled the quarantine of the crew after return from the lunar surface, reduced the duration of the Health Stabilization Program; and implemented acceptability limits for spacecraft surfaces and air. While microbial risks were not a main focus of the early Mercury and Gemini programs, the extended duration of Apollo flights resulted in the increased scrutiny of impact of the space flight environment on crew health. The lessons learned during that era of space flight continue to impact microbiology risk mitigation in space programs today.

Elliott, T. F↗
NASA NTRS1971

Instruct coders' manual

A manual designed both as an instructional manual for beginning coders and as a reference manual for the coding language INSTRUCT, is presented. The manual includes the major programs necessary to implement the teaching system and lists the limitation of current implementation. A detailed description is given of how to code a lesson, what buttons to push, and what utility programs to use. Suggestions for debugging coded lessons and the error messages that may be received during assembly or while running the lesson are given.

Friend, J.↗
NASA NTRS2007

State-Chart Autocoder

A computer program translates Unified Modeling Language (UML) representations of state charts into source code in the C, C++, and Python computing languages. ( State charts signifies graphical descriptions of states and state transitions of a spacecraft or other complex system.) The UML representations constituting the input to this program are generated by using a UML-compliant graphical design program to draw the state charts. The generated source code is consistent with the "quantum programming" approach, which is so named because it involves discrete states and state transitions that have features in common with states and state transitions in quantum mechanics. Quantum programming enables efficient implementation of state charts, suitable for real-time embedded flight software. In addition to source code, the autocoder program generates a graphical-user-interface (GUI) program that, in turn, generates a display of state transitions in response to events triggered by the user. The GUI program is wrapped around, and can be used to exercise the state-chart behavior of, the generated source code. Once the expected state-chart behavior is confirmed, the generated source code can be augmented with a software interface to the rest of the software with which the source code is required to interact.

Clark, Kenneth↗
NASA NTRSDate not supplied

Type-Safe Generic Programming in Fortran

When the Fortran language committee first collected requests for new language features for what has now become the Fortran 2023 standard, support for generic programming emerged as a top priority. However, due to the anticipated complexity, a dedicated committee subgroup was formed, and implementation of generic programming was purposely spread across two language release cycles -- aiming for what is internally referred to as F202Y. In this talk, I will begin with a brief overview of existing Fortran features that support generic programming and then proceed to a detailed examination of the plans for F202Y. This discussion will include motivating use cases, type-safe design goals, (probable) syntax, and a few simple examples. I conclude with a discussion on the likely limitations of generic programming in F202Y and my expectations for extended capabilities in the subsequent release, F203X.

Tom Clune↗
NASA NTRS1984

Software Implemented Fault-Tolerant (SIFT) user's guide

Program development for a Software Implemented Fault Tolerant (SIFT) computer system is accomplished in the NASA LaRC AIRLAB facility using a DEC VAX-11 to interface with eight Bendix BDX 930 flight control processors. The interface software which provides this SIFT program development capability was developed by AIRLAB personnel. This technical memorandum describes the application and design of this software in detail, and is intended to assist both the user in performance of SIFT research and the systems programmer responsible for maintaining and/or upgrading the SIFT programming environment.

Green, D. F., Jr.↗
NASA NTRS2000

NASA's Upper Atmosphere Research Program (UARP) and Atmospheric Chemistry Modeling and Analysis Program (ACMAP): Research Summaries 1997-1999

Under the mandate contained in the FY 1976 NASA Authorization Act, the National Aeronautics and Space Administration (NASA) has developed and is implementing a comprehensive program of research, technology development, and monitoring of the Earth's upper atmosphere, with emphasis on the upper troposphere and stratosphere. This program aims at expanding our chemical and physical understanding to permit both the quantitative analysis of current perturbations as well as the assessment of possible future changes in this important region of our environment. It is carried out jointly by the Upper Atmosphere Research Program (UARP) and the Atmospheric Chemistry Modeling and Analysis Program (ACMAP), both managed within the Research Division in the Office of Earth Science at NASA. Significant contributions to this effort have also been provided by the Atmospheric Effects of Aviation Project (AEAP) of NASA's Office of Aero-Space Technology. The long-term objectives of the present program are to perform research to: understand the physics, chemistry, and transport processes of the upper troposphere and the stratosphere and their control on the distribution of atmospheric chemical species such as ozone; assess possible perturbations to the composition of the atmosphere caused by human activities and natural phenomena (with a specific emphasis on trace gas geographical distributions, sources, and sinks and the role of trace gases in defining the chemical composition of the upper atmosphere); understand the processes affecting the distributions of radiatively active species in the atmosphere, and the importance of chemical-radiative-dynamical feedbacks on the meteorology and climatology of the stratosphere and troposphere; and understand ozone production, loss, and recovery in an atmosphere with increasing abundances of greenhouse gases. The current report is composed of two parts. Part 1 summarizes the objectives, status, and accomplishments of the research tasks supported under NASA UARP and ACMAP in a document entitled, Research Summaries 1997- 1999. Part 2 is entitled Present State of Knowledge of the Upper Atmosphere 1999 An Assessment Report.

Kurylo, M. J.↗
NASA NTRS1989

A user-friendly, menu-driven, language-free laser characteristics curves graphing program for desk-top IBM PC compatible computers

A facility was established that uses collected data and feeds it into mathematical models that generate improved data arrays by correcting for various losses, base line drift, and conversion to unity scaling. These developed data arrays have headers and other identifying information affixed and are subsequently stored in a Laser Materials and Characteristics data base which is accessible to various users. The two part data base: absorption - emission spectra and tabulated data, is developed around twelve laser models. The tabulated section of the data base is divided into several parts: crystalline, optical, mechanical, and thermal properties; aborption and emission spectra information; chemical name and formulas; and miscellaneous. A menu-driven, language-free graphing program will reduce and/or remove the requirement that users become competent FORTRAN programmers and the concomitant requirement that they also spend several days to a few weeks becoming conversant with the GEOGRAF library and sequence of calls and the continual refreshers of both. The work included becoming thoroughly conversant with or at least very familiar with GEOGRAF by GEOCOMP Corp. The development of the graphing program involved trial runs of the various callable library routines on dummy data in order to become familiar with actual implementation and sequencing. This was followed by trial runs with actual data base files and some additional data from current research that was not in the data base but currently needed graphs. After successful runs, with dummy and real data, using actual FORTRAN instructions steps were undertaken to develop the menu-driven language-free implementation of a program which would require the user only know how to use microcomputers. The user would simply be responding to items displayed on the video screen. To assist the user in arriving at the optimum values needed for a specific graph, a paper, and pencil check list was made available to use on the trial runs.

Klutz, Glenn↗
NASA NTRS1986

The US Space Station program

International participation in the U.S. Space Station program is examined. Proposed Space Station mission studies to be conducted by Canada, Japan, and Europe are described; the establishment and implementation of these programs is discussed. The use of the Space Station as a laboratory, test center, and manufacturing area, and the commercial applicability of the Space Station are analyzed.

Freitag, R. F.↗
NASA NTRS1990

Trajectory optimization for real-time guidance. I - Time-varying LQR on a parallel processor

A key algorithmic element of a real-time trajectory optimization hardware/software implementation, the quadratic program (QP) solver element, is presented. The purpose of the effort is to make nonlinear trajectory optimization fast enough to provide real-time commands during guidance of a vehicle such as an aeromaneuvering orbiter. Many methods of nonlinear programming require the solution of a QP at each iteration. In the trajectory optimization case the QP has a special dynamic programming structure, a LQR-like structure. QP algorithm speed is increased by taking advantage of this special structure and by parallel implementation.

Psiaki, Mark L.↗
NASA NTRS1993

Development of a multilayer interference simulation program for MSS systems

This paper discusses the development of a multilayer interference analysis and simulation program which is used to evaluate interference between non-geostationary and geostationary satellites. In addition to evaluating interference, this program can be used in the development of sharing criteria and coordination among various Mobile Satellite Services (MSS) systems. A C++/Windows implementation of this program, called Globalstar Interference Simulation Program (GISP), has been developed.

Izadian, Jamal S.↗
NASA NTRS1995

Introduction to Penelope

A formal program verification is a (mathematical) proof that a program executed according to its intended model meets some specification. This proves that the algorithm defined by the program is correct in the precise technical sense of being consistent with a particular specification. A program correct in this sense is free from a large and important class of errors, even though its behavior may still produce unintended results--either because the implementation of the programming language itself does not match the model of execution, or because the specification does not correctly express the user's intentions. Penelope is a prototype system for interactively developing and verifying programs that are written in a rich subset of sequential Ada. Penelope can be used to develop a program and its correctness proof incrementally, and in concert with one another. Incrementality is used in a number of ways to help make verification more tractable and more productive. For example, if an already-verified program is modified, one can attempt to prove the modified version by replaying and modifying the original verification. Penelope's specification language, Larch/Ada, belongs to the family of Larch interface languages. Larch/Ada scales up properly, in the sense that it is demonstrably sound to decompose a system hierarchically and reason locally about the implementation of each piece. Penelope has been applied in various demonstration projects--for specification (guidance control, distributed operating systems), verification (of off-the-shelf code), and formal development (by non-expert as well as expert users). Some features of Penelope have been embodied in Ada Wise, a lint-like non-interactive tool that warns of the potential for certain dynamic semantic errors in Ada programs.

Guaspari, David↗
DOE OSTI2024

Demystifying Solar in WAP

Over the last two years, the National Renewable Energy Laboratory has identified the pathways for implementing solar in the Weatherization Assistance Program and Low Income Home Energy Assistance Program and practices for successful implementation. Learn about successful implementation models from around the network and the new resources that can give you a head start in planning solar into your program, including a demonstration of tools to help evaluate solar potential and cost-effectiveness at the household level, as well as a new tool from the U.S. Department of Energy National Community Solar Partnership to help connect households receiving LIHEAP assistance to community solar subscriptions that guarantee energy bill savings.

ENERGY PLANNING, POLICY, AND ECONOMY,SOLAR ENERGY↗
NASA NTRSDate not supplied

Establishing Trust in NASA’s Artemis Campaign Computer-Human Interface (CHI) Implementation

The NASA Artemis program will return humans to the Moon. This time, with the help of commercial and international partners, the program's objective is a permanent moon base. The moon base infrastructure, including an orbiting moon station and moon surface assets, will be developed for astronauts to stay for the long haul to learn to live and work on another planet in preparation for an eventual Humans-to-Mars mission. As the roundtrip communication delays increase in deep space exploration, the crew will need more onboard systems autonomy and functionality to maintain and control the vehicle or habitat. These mission constraints will change the current Earth-based spacecraft to ground control support approach that will demand more safe, efficient, and effective Computer-Human Interface (CHI) control. For Artemis, CHI is defined as the elements that the crew interfaces with: audio, video, lighting, and crew controls subsystems. Understanding how CHI will need to evolve to support deep space missions will be critical for the Artemis program--especially crew controls, which is the focus of this paper. How does NASA ensure crew controls are reliable enough to control complex systems and prevent a catastrophic event due to human error--especially when the astronauts could be physiologically and/or psychologically impaired? NASA's approach to mitigating catastrophic hazards in human spaceflight system development such as crew controls, is through a holistic system engineering and Human System Integration methodology that focuses on incorporating NASA's Human-Rating Requirements-that ensures human performance characteristics to control/safely recover the crew from hazardous situations within the human interface design are considered. This paper discusses, at a high level, CHI for the Artemis program. Next, a discussion of what it means to human-rate a space system crew controls and how trust in the human-computer interface begins with the NASA human rating requirements. Finally, a discussion on how systems engineering and the human system integration process ensures that crew control implementation incorporates the NASA human-rating requirements.

artemis↗
NASA NTRSDate not supplied

Establishing Trust in NASA’s Artemis Campaign Computer-Human Interface (CHI) Implementation

The NASA Artemis program will return humans to the Moon. This time, with the help of commercial and international partners, the program's objective is a permanent moon base. The moon base infrastructure, including an orbiting moon station and moon surface assets, will be developed for astronauts to stay for the long haul to learn to live and work on another planet in preparation for an eventual Humans-to-Mars mission. As the roundtrip communication delays increase in deep space exploration, the crew will need more onboard systems autonomy and functionality to maintain and control the vehicle or habitat. These mission constraints will change the current Earth-based spacecraft to ground control support approach that will demand more safe, efficient, and effective Computer-Human Interface (CHI) control. For Artemis, CHI is defined as the elements that the crew interfaces with: audio, video, lighting, and crew controls subsystems. Understanding how CHI will need to evolve to support deep space missions will be critical for the Artemis program--especially crew controls, which is the focus of this paper. How does NASA ensure crew controls are reliable enough to control complex systems and prevent a catastrophic event due to human error--especially when the astronauts could be physiologically and/or psychologically impaired? NASA's approach to mitigating catastrophic hazards in human spaceflight system development such as crew controls, is through a holistic system engineering and Human System Integration methodology that focuses on incorporating NASA's Human-Rating Requirements-that ensures human performance characteristics to control/safely recover the crew from hazardous situations within the human interface design are considered. This paper discusses, at a high level, CHI for the Artemis program. Next, a discussion of what it means to human-rate a space system crew controls and how trust in the human-computer interface begins with the NASA human rating requirements. Finally, a discussion on how systems engineering and the human system integration process ensures that crew control implementation incorporates the NASA human-rating requirements.

artemis↗
NASA NTRS1995

Software For Design And Analysis Of Tanks And Cylindrical Shells

Skin-stringer Tank Analysis Spreadsheet System (STASS) computer program developed for use as preliminary design software tool that enables quick-turnaround design and analysis of structural domes and cylindrical barrel sections in propellant tanks or other cylindrical shells. Determines minimum required skin thicknesses for domes and cylindrical shells to withstand material failure due to applied pressures (ullage and/or hydrostatic) and runs buckling analyses on cylindrical shells and skin-stringers. Implemented as workbook program, using Microsoft Excel v4.0 on Macintosh II. Also implemented using Microsoft Excel v4.0 for Microsoft Windows v3.1 IBM PC.

Luz, Paul L.↗
NASA NTRS1975

ORACLS - A modern control theory design package

A digital computer program (ORACLS) for implementing the optimal regulator theory approach to the design of controllers for linear time-invariant systems is described. The user-oriented program employs the latest numerical techniques and is applicable to both the digital and continuous control problems.

Armstrong, E. S.↗
NASA NTRS1993

Integrated modeling of advanced optical systems

This poster session paper describes an integrated modeling and analysis capability being developed at JPL under funding provided by the JPL Director's Discretionary Fund and the JPL Control/Structure Interaction Program (CSI). The posters briefly summarize the program capabilities and illustrate them with an example problem. The computer programs developed under this effort will provide an unprecedented capability for integrated modeling and design of high performance optical spacecraft. The engineering disciplines supported include structural dynamics, controls, optics and thermodynamics. Such tools are needed in order to evaluate the end-to-end system performance of spacecraft such as OSI, POINTS, and SMMM. This paper illustrates the proof-of-concept tools that have been developed to establish the technology requirements and demonstrate the new features of integrated modeling and design. The current program also includes implementation of a prototype tool based upon the CAESY environment being developed under the NASA Guidance and Control Research and Technology Computational Controls Program. This prototype will be available late in FY-92. The development plan proposes a major software production effort to fabricate, deliver, support and maintain a national-class tool from FY-93 through FY-95.

Briggs, Hugh C.↗