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 955 records · Page 53

Measurement of high altitude air quality using aircraft

The minor atmospheric constituents associated with and affected by aircraft exhaust emissions at altitudes from 6 to 20 km will be monitored in flight programs presently being implemented. Preliminary in situ data are available from flight tests of dedicated instruments to be used in these programs. A Global Atmospheric Sampling Program using Boeing 747 airliners was determined to be feasible in studies conducted by airlines and airframe companies. Worldwide monitoring in the troposphere and the lower stratosphere is planned. Stratospheric air sampling on a more local basis will be done with a U2 aircraft. Measuring system evaluations and improvements have been required to detect the low background levels.

Rudey, R. A.↗

Measurement of high-altitude air quality using aircraft.

The minor atmospheric constituents associated with and affected by aircraft exhaust emissions at altitudes from 6 to 20 km will be monitored in flight programs presently being implemented. Preliminary in situ data are available from flight tests of dedicated instruments to be used in these programs. A Global Atmospheric Sampling Program using Boeing 747 airliners was determined to be feasible in studies conducted by airlines and airframe companies. Worldwide monitoring in the troposphere and the lower stratosphere is planned. Stratospheric air sampling on a more local basis will be done with a U2 aircraft. Measuring system evaluations and improvements have been required to detect the low background levels.

Rudey, R. A.↗

Evaluation of the electrochemical O2 concentrator as an O2 compressor

A program was successfully completed to analytically and experimentally evaluate the feasibility of using an electrochemical oxygen (O2) concentrator as an O2 compressor. The electrochemical O2 compressor (EOC) compresses 345 kN/sq m (50 psia) O2 generated on board the space vehicle by the water electrolysis subsystem (WES) in a single stage to 20,700 kN/sq m (3000 psia) to refill spent extravehicular equipment O2 bottles and to eliminate the need for high pressure O2 storage. The single cell EOC designed, fabricated, and used for the feasibility testing is capable of being tested at O2 pressures up to 41,400 kN/sq m (6000 psia). A ground support test facility to test the EOC cell was designed, fabricated, and used for the EOC feasibility testing. A product assurance program was established, implemented, and maintained which emphasized safety and materials compatibility associated with high pressure O2 operation. A membrane development program was conducted to develop a membrane for EOC application. Data obtained using a commercially available membrane were used to guide the development of the membranes fabricated specifically for an EOC. A total of 15 membranes were fabricated.

Marshall, R. D.↗

The SIFT Code Specification

The specification of Software Implemented Fault Tolerance (SIFT) consists of two parts, the specifications of the SIFT models and the specifications of the SIFT PASCAL program which actually implements the SIFT system. The code specifications are the last of a hierarchy of models describing the operation of the SIFT system and are related to the SIFT models as well as the PASCAL program. These Specifications serve to link the SIFT models to the running program. The specifications are very large and detailed and closely follow the form and organization of the PASCAL code. In addition to describing each of the components of the SIFT code, the code specifications describe the assumptions of the upper SIFT models which are required to actually prove that the code will work as specified. These constraints are imposed primarily on the schedule tables.

Source record↗

Neutron flux reduction programs for reactor pressure vessel

The objective of this work is to implement various fast neutron flux reduction programs on the belt-line region of the reactor pressure vessel to reduce the increasing rate of reference temperature for pressurized thermal shock (RT PTS) for Korea Nuclear Unit 1. A pressurized thermal shock (PTS) event is an event or transient in pressurized water reactors (PWRs) causing severe overcooling (thermal shock) concurrent with or followed by significant pressure in the reactor vessel. A PTS concern arises if one of these transients acts in the belt-line region of a reactor vessel where a reduced fracture resistance exists because of neutron irradiation. Generally, the RT PTS value is continuously increasing according to the fast neutron irradiation during the reactor operation, and it can reach the screening criterion prior to the expiration of the operating license. To reduce the increasing rate of RT PTS, various neutron flux reduction programs can be implemented, which are focused on license renewal. In this paper, neutron flux reduction programs, such as low leakage loading pattern strategy, loading of neutron absorber rods, and dummy fuel assembly loading are considered for Korea Nuclear Unit 1, of which the RT PTS value of the leading material (circumferential weld) is going to reach the screening criterion in the near future. To evaluate the effects of the neutron flux reduction programs, plant and cycle specific forward neutron transport calculations for the various neutron flux reduction programs were carried out. For the analysis, all transport calculations were carried out by using the DORT 3.1 discrete ordinate code and BUGLE-96 cross-section library. (authors)

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

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↗

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↗

Tank Inspection NDE Results for Fiscal Year 2014, Waste Tanks 26, 27, 28 and 33

Ultrasonic nondestructive examinations (NDE) were performed on waste storage tanks 26, 27, 28 and 33 at the Savannah River Site as a part of the “In-Service Inspection (ISI) Program for High Level Waste Tanks.” No reportable conditions were identified during these inspections. The results indicate that the implemented corrosion control program continues to effectively mitigate corrosion in the SRS waste tanks. Ultrasonic inspection (UT) is used to detect general wall thinning, pitting and interface attack, as well as vertically oriented cracks through inspection of an 8.5 inch wide strip extending over the accessible height of the primary tank wall and accessible knuckle regions. Welds were also inspected in tanks 27, 28 and 33 with no reportable indications. In a Type III/IIIA primary tank, a complete vertical strip includes scans of five plates (including knuckles) so five “plate/strips” would be completed at each vertical strip location. In FY 2014, a combined total of 79 plate/strips were examined for thickness mapping and crack detection, equating to over 45,000 square inches of area inspected on the primary tank wall. Of the 79 plate/strips examined in FY 2014 all but three have average thicknesses that remain at or above the construction minimum thickness which is nominal thickness minus 0.010 inches. There were no service induced reportable thicknesses or cracking encountered. A total of 2 pits were documented in 2014 with the deepest being 0.032 inches deep. One pit was detected in Tank 27 and one in Tank 33. No pitting was identified in Tanks 26 or 28. The maximum depth of any pit encountered in FY 2014 is 5% of nominal thickness, which is less than the minimum reportable criteria of 25% through-wall for pitting. In Tank 26 two vertical strips were inspected, as required by the ISI Program, due to tank conditions being outside normal chemistry controls for more than 3 months. Tank 28 had an area of localized thinning on the exterior wall of the secondary tank noted during the initial inspections in 2005. That area was inspected again in 2014 and found to be larger and slightly deeper. The deepest area of thinning in the secondary wall is less than 20% wall loss. The maximum length of thinning is less than 24 inches and does not impact structural or leak integrity per WSRC-TR-2002-00063. Inspection results were presented to the In-service Inspection Review Committee (ISIRC) where it was determined that no additional data was required to complete these inspections.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Energy Efficiency Finance Programs: Use Case Analysis to Define Data Needs and Guidelines

There are over 200 energy efficiency loan programs—across 49 U.S. states—administered by utilities, state/local government agencies, or private lenders.1 This distributed model has led to significant variation in program design and implementation practices including how data is collected and used. The challenge of consolidating and aggregating data across independently administered programs has been illustrated by a recent pilot of an open source database for energy efficiency financing program data. This project was led by the Environmental Defense Fund (EDF), the Investor Confidence Project, the Clean Energy Finance Center (CEFC), and the University of Chicago. This partnership discussed data collection practices with a number of existing energy efficiency loan programs and identified four programs that were suitable and willing to participate in the pilot database (Diamond 2014).2 The partnership collected information related to ~12,000 loans with an aggregate value of ~$100M across the four programs. Of the 95 data fields collected across the four programs, 30 fields were common between two or more programs and only seven data fields were common across all programs. The results of that pilot study illustrate the inconsistencies in current data definition and collection practices among energy efficiency finance programs and may contribute to certain barriers.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗

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.↗

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↗

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↗

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'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.↗

UNDERSTANDING METHANE EMISSIONS SOURCES AND VIABLE MITIGATION MEASURES IN THE NATURAL GAS TRANSMISSION SYSTEMS: RUSSIAN AND U.S. EXPERIENCE

This article will compare the natural gas transmission systems in the U.S. and Russia and review experience with methane mitigation technologies in the two countries. Russia and the United States (U.S.) are the world's largest consumers and producers of natural gas, and consequently, have some of the largest natural gas infrastructure. This paper compares the natural gas transmission systems in Russia and the U.S., their methane emissions and experiences in implementing methane mitigation technologies. Given the scale of the two systems, many international oil and natural gas companies have expressed interest in better understanding the methane emission volumes and trends as well as the methane mitigation options. This paper compares the two transmission systems and documents experiences in Russia and the U.S. in implementing technologies and programs for methane mitigation. The systems are inherently different. For instance, while the U.S. natural gas transmission system is represented by many companies, which operate pipelines with various characteristics, in Russia predominately one company, Gazprom, operates the gas transmission system. However, companies in both countries found that reducing methane emissions can be feasible and profitable. Examples of technologies in use include replacing wet seals with dry seals, implementing Directed Inspection and Maintenance (DI&M) programs, performing pipeline pump-down, applying composite wrap for non-leaking pipeline defects and installing low-bleed pneumatics. The research methodology for this paper involved a review of information on methane emissions trends and mitigation measures, analytical and statistical data collection; accumulation and analysis of operational data on compressor seals and other emission sources; and analysis of technologies used in both countries to mitigate methane emissions in the transmission sector. Operators of natural gas transmission systems have many options to reduce natural gas losses. Depending on the value of gas, simple, low-cost measures, such as adjusting leaking equipment components, or larger-scale measures, such as installing dry seals on compressors, can be applied.

03 NATURAL GAS↗

Quantum Fast Circuit Optimizer (qFactor) v1

Quantum programs are represented as circuits, or sequences of gates. A common problem during quantum compilation to find a circuit that implements a target program. This is an optimizer, it optimizes a circuit's distance to the target by solving for the best fit gates. It is not a standard optimizer, it only optimizes circuits. It is not a compiler or synthesizer, it cannot build circuits, but given a circuit structure, it will solve for the gates. Quantum compilers (qsearch, qfast) use standard numerical optimizers. This has advantages over those general-purpose optimizers since it is domain-specific.

Younis, Ed↗

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↗