SEARCH · Search NASA
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.
The original Langley Working Paper (LWP 448) published on July 27th, 1967, provided guidance to NASA Langley Research Center personnel on how to set up conventional path-integrated schlieren flow visualization systems and what pitfalls could be expected with such setups. The guidance and information contained in the document continues to be used for schlieren setups at NASA Langley Research Center to this day.
Software documentation and a computer program listing for a horizon control of a longwall shearer are presented.
The purpose of this document is to provide experience-based guidance in implementing a software process improvement program in any NASA software development or maintenance community. This guidebook details how to define, operate, and implement a working software process improvement program. It describes the concept of the software process improvement program and its basic organizational components. It then describes the structure, organization, and operation of the software process improvement program, illustrating all these concepts with specific NASA examples. The information presented in the document is derived from the experiences of several NASA software organizations, including the SEL, the SEAL, and the SORCE. Their experiences reflect many of the elements of software process improvement within NASA. This guidebook presents lessons learned in a form usable by anyone considering establishing a software process improvement program within his or her own environment. This guidebook attempts to balance general and detailed information. It provides material general enough to be usable by NASA organizations whose characteristics do not directly match those of the sources of the information and models presented herein. It also keeps the ideas sufficiently close to the sources of the practical experiences that have generated the models and information.
With the rapid development of advanced reactors and numerous companies requesting pre-application engagements with the Nuclear Regulatory Commission (NRC), there is need for the NRC to best prepare themselves for new challenges presented by advanced technologies. One specific reactor type of interest is the molten salt reactor (MSR) that uses liquid salt as the fuel for the reactor. Liquid salt fuel reactors have specific challenges with regards to performing material control and accounting (MC&A). The challenges result from the fuel form being a continuous fissile material form rather than discrete units like is found with fuel assemblies in traditional light water reactors (LWRs). The goal of this document is to provide the NRC with guidance on the different approaches and technologies that may be proposed by reactor designers to address these problems to prepare staff for regulatory reviews.
This audit was initiated in response to a hotline complaint regarding the review, approval, and release of scientific and technical information (STI) at Johnson Space Center. The complainant alleged that Johnson personnel conducting export control reviews of STI were not fully qualified to conduct those reviews and that the reviews often did not occur until after the STI had been publicly released. NASA guidance requires that STI, defined as the results of basic and applied scientific, technical, and related engineering research and development, undergo certain reviews prior to being released outside of NASA or to audiences that include foreign nationals. The process includes technical, national security, export control, copyright, and trade secret (e.g., proprietary data) reviews. The review process was designed to preclude the inappropriate dissemination of sensitive information while ensuring that NASA complies with a requirement of the National Aeronautics and Space Act of 1958 (the Space Act)1 to provide for the widest practicable and appropriate dissemination of information resulting from NASA research activities. We focused our audit on evaluating the STI review process: specifically, determining whether the roles and responsibilities for the review, approval, and release of STI were adequately defined and documented in NASA and Center-level guidance and whether that guidance was effectively implemented at Goddard Space Flight Center, Johnson Space Center, Langley Research Center, and Marshall Space Flight Center. Johnson was included in the review because it was the source of the initial complaint, and Goddard, Langley, and Marshall were included because those Centers consistently produce significant amounts of STI.
Hardware elements in new and advanced astrionics system designs are discussed. This cost effective approach has as its goal the reduction of R&D and testing costs through the application of proven and tested astrionics components. The ready availability to the designer of data facts for applicable system components is highly desirable. The astrionics System Designers Handbook has as its objective this documenting of data facts to serve the anticipated requirements of the astrionics system designer. Eleven NASA programs were selected as the reference base for the document. These programs are: ATS-F, ERTS-B, HEAO-A, OSO-I, Viking Orbiter, OAO-C, Skylab AM/MDA, Skylab ATM, Apollo 17 CSM, Apollo 17 LM and Mariner Mars 71. Four subsystems were chosen for documentation: communications, data management, electrical power and guidance, navigation and control.
The Trace Contaminant Control Simulation computer program is a tool for assessing the performance of various trace contaminant control technologies for removing trace chemical contamination from a spacecraft cabin atmosphere. The results obtained from the program can be useful in assessing different technology combinations, system sizing, system location with respect to other life support systems, and the overall life cycle economics of a trace contaminant control system. The user's manual is extracted in its entirety from NASA TM-108409 to provide a stand-alone reference for using any version of the program. The first publication of the manual as part of TM-108409 also included a detailed listing of version 8.0 of the program. As changes to the code were necessary, it became apparent that the user's manual should be separate from the computer code documentation and be general enough to provide guidance in using any version of the program. Provided in the guide are tips for input file preparation, general program execution, and output file manipulation. Information concerning source code listings of the latest version of the computer program may be obtained by contacting the author.
TDA documents determine the personnel strengths for each Army installation. They reflect the number of people required to accomplish a certain mission by various characteristics. U.S. Army Training and Doctrine Command (TRADOC) analysts continuously scrutinize these documents to ensure that they comply with provided guidance. Part of this guidance has been used to develop a set of manual rules. Analysts apply these rules to the TDA to eliminate positions, downgrade positions, or reduce position strength. However, this process is very time consuming. ln addition, human involvement introduces inconsistencies and errors that are difficult to detect later. This paper explains how I represented these rules using the 'C' Language Production System (CLIPS) to develop an expert system that is applied consistently and comprehensively for all TRADOC installations. The TDA System Analyzer reduces the review process from about five days to just twenty minutes; giving the user more time to analyze the results and thereby make better decisions. Furthermore, the user is assured that the rules are applied uniformly to every TDA document. This paper also explains the integration of the TDA System Analyzer into TRADOC's On-Line TDA System. Providing the analyst an extra utility module that can be accessed from a familiar environment.
A repository for critical and important detailed design data and information, hitherto unpublished, along with significant data on oxygen reactivity phenomena with metallic and nonmetallic materials in moderate to very high pressure environments is documented. This data and information provide a ready and easy to use reference for the guidance of designers of propulsion, power, and life support systems for use in space flight. The document is also applicable to designs for industrial and civilian uses of high pressure oxygen systems. The information presented herein are derived from data and design practices involving oxygen usage at pressures ranging from about 20 psia to 8000 psia equal with thermal conditions ranging from room temperatures up to 500 F.
The purpose of this document is to provide program/project teams necessary instruction and guidance in the best practices for Work Breakdown Structure (WBS) and WBS dictionary development and use for project implementation and management control. This handbook can be used for all types of NASA projects and work activities including research, development, construction, test and evaluation, and operations. The products of these work efforts may be hardware, software, data, or service elements (alone or in combination). The aim of this document is to assist project teams in the development of effective work breakdown structures that provide a framework of common reference for all project elements.
The purpose of this document is to provide program/project teams necessary instruction and guidance in the best practices for Work Breakdown Structure (WBS) and WBS dictionary development and use for project implementation and management control. This handbook can be used for all types of NASA projects and work activities including research, development, construction, test and evaluation, and operations. The products of these work efforts may be hardware, software, data, or service elements (alone or in combination). The aim of this document is to assist project teams in the development of effective work breakdown structures that provide a framework of common reference for all project elements.
(Automated Verification of Flight Software), a collection of tools for analyzing source programs written in FORTRAN and AED is documented. The quality and the reliability of flight software are improved by: (1) indented listings of source programs, (2) static analysis to detect inconsistencies in the use of variables and parameters, (3) automated documentation, (4) instrumentation of source code, (5) retesting guidance, (6) analysis of assertions, (7) symbolic execution, (8) generation of verification conditions, and (9) simplification of verification conditions. Use of AVFS in the verification of flight software is described.
A document describes mathematical derivations and applications of autonomous guidance algorithms for maneuvering spacecraft in the vicinities of small astronomical bodies like comets or asteroids. These algorithms compute fuel- or energy-optimal trajectories for typical maneuvers by solving the associated optimal-control problems with relevant control and state constraints. In the derivations, these problems are converted from their original continuous (infinite-dimensional) forms to finite-dimensional forms through (1) discretization of the time axis and (2) spectral discretization of control inputs via a finite number of Chebyshev basis functions. In these doubly discretized problems, the Chebyshev coefficients are the variables. These problems are, variously, either convex programming problems or programming problems that can be convexified. The resulting discrete problems are convex parameter-optimization problems; this is desirable because one can take advantage of very efficient and robust algorithms that have been developed previously and are well established for solving such problems. These algorithms are fast, do not require initial guesses, and always converge to global optima. Following the derivations, the algorithms are demonstrated by applying them to numerical examples of flyby, descent-to-hover, and ascent-from-hover maneuvers.
The purpose of this style guide is to provide a clear, consistent framework for the design and development of human system interfaces (HSIs) used throughout the Fermilab accelerator complex. It establishes a shared visual and interaction foundation to ensure that interfaces remain intuitive, effective, and cohesive, regardless of when or by whom they are developed. By adhering to these guidelines, developers can avoid introducing unnecessary deviations that compromise usability or increase system training burden. This consistency is especially critical in long-term, multi-contributor projects where interface continuity and maintainability are paramount. This document serves as a practical reference for all HSI development activities related to the accelerator control environment. While the guidance provided is comprehensive, it is not exhaustive of every potential design scenario. As such, the style guide is intended to function as a living document, subject to regular review and revision. Updates will be made at least annually to incorporate emerging best practices, operational feedback, and evolving system needs. Areas where detailed guidance is still under development are clearly indicated in gray throughout the document and will be addressed in future revisions according to project priorities.
This report was created by Sandia National Laboratories (SNL) to document the principles and methodology of performance data collection and integration with modeling and simulation tools to better facilitate the performance evaluation of physical protection systems (PPS). Results and conclusions from the use of modeling and simulation tools are only as good as the data employed by the tools when conducting analysis. Acquiring the performance testing data necessary to ensure effective evaluation can be a complex and sometimes daunting process. It is the desire of the organization to provide guidance that eases the burdens associated with pursuit of these objectives. This document draws heavily upon longstanding principles of systems engineering that have been developed and employed by SNL in the discipline of security since the 1970s. The scope of this document is constrained to the testing of system components and integration of data that is applicable within the context of PPS performance analysis using two tools that have been developed by SNL, PathTrace© and Scribe3D©. For guidance related to testing and evaluation more broadly, the manuals and reports referenced by this document can be consulted.
This handbook provides guidance to mission providers and Planetary Protection (PP) practitioners on implementing PP measures for both robotic and crewed space missions. This handbook represents major updates to PP practices since a previously drafted handbook from 2010. In 2017, NASA reorganized the Office of Planetary Protection (OPP) from the Science Mission Directorate (SMD) to a Technical Authority (TA) within the Office of Safety and Mission Assurance (OSMA). With this organizational change came a complete overhaul of NASA’s PP policy and technical standards. This handbook reflects the latest NASA PP policy updates in NPR 8715.24, Planetary Protection Provisions for Robotic Extraterrestrial Missions and technical requirements of NASA-STD-8719.27, Implementing Planetary Protection Requirements for Space Flight. This handbook is a companion document to the NPR and technical standard and provides guidance, best practices, background information, and advice for practitioners to consider when implementing PP on NASA missions and NASA-partnered missions.
Millions of people are able to exchange information over phones, computers, tablets and an array of new interconnected devices such as sensors, cameras, home appliances and others are increasingly becoming networked. At the core of this sizeable interconnection is a set of underlying protocols that enable millions of devices to seamlessly talk to each other. Aviation, as many other industries have, utilizes the internet protocol for ground-to-ground network communications and efforts are underway to bring it to the cockpit.In 2015, the International Civil Aviation Organization (ICAO) published the second edition of Document 9896 (Doc 9896) titled: Manual on the Aeronautical Telecommunication Network (ATN) using Internet Protocol Suite (IPS) Standards and Protocol. This manual adopted the Internet protocol version 6 (IPv6) for Internet layer interoperability. Document 9896 defined data communications protocols and services to be used for implementing aeronautical telecommunication network (ATN) using the Internet protocol suite (IPS). The document provided technical specifications that addressed security, network and transport protocols, described applications, supported by ATN/IPS and provided communications guidance. The international aviation community working under the guidance of ICAO initiated work on updates to Doc 9896. Under the ICAO Communication Panel, Working Group Internetworking (WG-I) got this challenging task. Key areas of work for WG-I are related to ATN/IPS Security and ANT/IPS Mobility. Two sub-groups have been assembled to work on these elements. The ICAO anticipates the release of updated Doc 9896 in 2020. Additional ATN/IPS standardization efforts include Radio Technical Commission for Aeronautics Special Committee 223 (RTCA SC-223) IPS profile development, Airlines Electronic Engineering Committee (AEEC) A658 Roadmap of IPS future activities and European Organization for Civil Aviation Equipment (EUROCAE) WG-108 development of guidance documentation.This paper describes ICAO WG-I approach to update key areas of the document in closed coordination with AEEC, RTCA and EUROCAE committees supporting the development of ATN/IPS. Additionally, the paper will explore WG-I mobility solutions under investigation, security developments, IPv6 addressing challenges and other proposed updates. Finally, as new operational expectations such as Free Route and Remote Piloted Aircraft System integration are currently pushing the boundaries set by old operational concepts, the paper identifies the emerging new challenges that will drive the ATN/IPS development beyond 2020. They are related to future voice utilization, System Wide Information Management and Remotely Piloted Aircraft System deployment. IPS systems are seen as the only way forward.
This report describes the basis used to develop the radiological dose acceptance and design criteria contained in the draft updates to Army Regulation 50–7 (AR 50–7) Army Reactor Program and its accompanying draft Department of the Army (DA) Pamphlet (PAM), Army Reactor Program Procedures. These criteria will apply to Army nuclear reactors that fall under AR 50–7 and its accompanying DA PAM and ensure alignment with the overall objectives of the Army Reactor Program. The development basis for the radiological dose and design criteria supports a modern, technology-neutral, risk-informed, and performance-based approach to Army regulation of reactors and the demonstration of “adequate protection of the public.” To establish these criteria that support the Army’s unique operational requirements, multiple well-known and well-established standards and their supporting documentation were reviewed to ensure consistency with existing regulatory safety levels, including guidance from U.S. and international sources. These include the U.S. Nuclear Regulatory Commission’s (NRC’s) regulations and policy, the Canadian Nuclear Safety Commission’s (CNSC’s) regulatory documents, the International Atomic Energy Agency’s (IAEA’s) safety standards, as well as industry input that is tailored specifically to advanced microreactors. This report walks through the key definitions and associated references used for these criteria, which are outlined in Section 2.0. Based on these definitions, the dose acceptance criteria were established for various receptors for routine reactor operations (Section 3.2), design basis accidents (Section 3.3), and beyond design basis accidents (Section 3.4). Comparisons of multiple national and international dose limits are provided in these sections. Lastly, Section 4.0 outlines the reactor safety design criteria contained in the draft DA PAM and their associated bases.