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 research to develop methods for reducing the effort expended in software and verification is reported. The development of a formal software requirements methodology, a formal specifications language, a programming language, a language preprocessor, and code analysis tools are discussed.
During the past decade, the National Aeronautics and Space Administration (NASA) has been developing and evaluating a suite of decision support tools (DSTs) to aid the air traffic controller in the management of traffic. These tools are known collectively as the Center/TRACON Automation System (CTAS). The primary focus of CTAS is increased capacity. As part of a new NASA program called Quiet Aircraft Technology (QAT), the following question is being addressed: Can CTAS technology also support the noise mitigation requirements imposed by the community? Controllers currently support a variety of low noise procedures in low traffic densities but, as traffic increases, these must be abandoned due to excessive spacing requirements for vectoring or inter-arrival spacing requirements needed to handle a spectrum of low noise procedures. NASA is currently investigating how to provide controllers with noise-mitigation-based advisories which address these issues without negatively impacting capacity. These issues are of global concern which must be addressed as the demand for air travel continues to increase.
This presentation discusses radiation hardness assurance (RHA) for space systems, providing both the programmatic aspects of RHA and the RHA procedure. RHA consists of all activities undertaken to ensure that the electronics and materials of a space system perform to their design specifications after exposure to the space radiation environment. RHA also pertains to environment definition, part selection, part testing, spacecraft layout, radiation tolerant design, and mission/system/subsystems requirements. RHA procedure consists of establishing mission requirements, defining and evaluating the radiation hazard, selecting and categorizing the appropriate parts, and evaluating circuit response to hazard. The RHA approach is based on risk management and is confined only to parts, it includes spacecraft layout, system/subsystem/circuit design, and system requirements and system operations. RHA should be taken into account in the early phases of a program including the proposal and feasibility analysis phases.
NASA's Europa Clipper mission will investigate Jupiter's icy moon Europa using a payload suite consisting of nine instruments to address a range of scientific objectives concerning Europa's habitability. As the project proceeds past its Critical Design Review, confidence is being built in the system's ability to achieve mission objectives through the implementation of a rigorous payload verification and validation (V&V) program. As part of this payload V&V program, instrument box-level testing was performed by the payload team to verify select instrument-avionics interface requirements. This testing was performed at JPL using the avionics testbed's Bulk Data Storage Emulator (BDSEM) with visiting instrument Test Models. This paper summarizes the Data Link test campaign involving roughly four days of functional testing per instrument, including planning, testing methods, types of issues found, and the requirement closure process. Detail is also provided on the development, deployment, and validation of a standardized analysis tool used in data reviews. This testing verified requirements related to commanding rates, loss of link, packet format, clock counters, loopback test capability, and SpaceWire jitter and skew margins. Additional risk reduction testing of basic commanding, counter behavior, science data collection and transfer, and interface swapping was also performed. Because the BDSEM venue was not originally designed to be a run for record venue, the process of characterizing venue fidelity and establishing suitability for requirement closure using data collected in this venue will also be addressed.In order to close requirements, an extensible tool was developed to post-process instrument command and telemetry data from their original binary to a human-readable format and give visibility to errors detected within the data, such as packets with Cyclic Redundancy Check errors. This tool, called payload-packet-parser, is a Python 3.9 command line tool built using a variety of open-source Python libraries. Payload-packet-parser was designed to support parsing command and telemetry packets for all Europa Clipper instruments and additional analysis tools were developed for verification of specific information interface requirements. This test campaign, including post-processing using a single parsing and verification toolset, allowed for early interface testing, alleviating testing burdens on instrument teams and buying down risk on the instrument-avionics interface by finding hardware and software issues and idiosyncrasies prior to integration with system test venues. Over twenty issues were discovered across the payload, resulting in software updates and instrument rework well in advance of any system impacts. This paper concludes with an assessment of benefits and costs of this type of testing and lessons learned.
This annual report describes work to integrate a set of tools to support early model-based analysis of failures and hazards due to system-software interactions. The tools perform and assist analysts in the following tasks: 1) extract model parts from text for architecture and safety/hazard models; 2) combine the parts with library information to develop the models for visualization and analysis; 3) perform graph analysis and simulation to identify and evaluate possible paths from hazard sources to vulnerable entities and functions, in nominal and anomalous system-software configurations and scenarios; and 4) identify resulting candidate scenarios for software integration testing. There has been significant technical progress in model extraction from Orion program text sources, architecture model derivation (components and connections) and documentation of extraction sources. Models have been derived from Internal Interface Requirements Documents (IIRDs) and FMEA documents. Linguistic text processing is used to extract model parts and relationships, and the Aerospace Ontology also aids automated model development from the extracted information. Visualizations of these models assist analysts in requirements overview and in checking consistency and completeness.
This presentation describes work to integrate a set of tools to support early model-based analysis of failures and hazards due to system-software interactions. The tools perform and assist analysts in the following tasks: 1) extract model parts from text for architecture and safety/hazard models; 2) combine the parts with library information to develop the models for visualization and analysis; 3) perform graph analysis and simulation to identify and evaluate possible paths from hazard sources to vulnerable entities and functions, in nominal and anomalous system-software configurations and scenarios; and 4) identify resulting candidate scenarios for software integration testing. There has been significant technical progress in model extraction from Orion program text sources, architecture model derivation (components and connections) and documentation of extraction sources. Models have been derived from Internal Interface Requirements Documents (IIRDs) and FMEA documents. Linguistic text processing is used to extract model parts and relationships, and the Aerospace Ontology also aids automated model development from the extracted information. Visualizations of these models assist analysts in requirements overview and in checking consistency and completeness.
Although the fundamental principles of spin stabilization are well established, uncertainty regarding the potential for rapid nutation growth caused by onboard liquids is a continuing concern. NASA and other organizations regularly encounter the issue of rapid nutation growth due to energy dissipation by liquids on spinning vehicles. Of concern is the stability of spinning upper stages and of spacecraft that spin for part or all of their missions. Several missions have required last-minute hardware or operational changes to deal with rapid nutation divergences that were identified late in the program. In some instances, major schedule slips were barely averted. In at least two cases, it was determined that a spinning upper stage was not a viable option. Historically, the "slosh" issue has been addressed by each space vehicle project individually, if it has been addressed at all. Due to budgetary and programmatic constraints, individual projects are unable to address the problem globally. Hence, there has been little effort to collect available test and flight data and use that data to make a coherent, unified picture of the "slosh" effect and how to deal with it. To some extent, each project has had to "reinvent the wheel", which can be both costly and risky. This study is a step toward correcting the situation. Specifically, the goal was to identify and collect available flight and test data for spinning vehicles with onboard liquid propellants. A total of 149 flight data points and 1,692 test points were collected as part of this study. This data was analyzed, correlated, and is presented here in a normalized form. In most cases, the normalization involves a dimensionless nutation time constant that can be used to predict performance of other vehicles with the same type of tank. For some configurations, it was also possible to identify conditions that can lead to resonance between nutational motion and liquid modes. Gaps in the knowledge base are identified and approaches to filling those gaps are outlined. The data presented here has two different but related uses. First, it can be applied directly to current and future spacecraft programs. Second, it can provide truth models for testing analytical techniques. Experience has shown that purely analytical models of the liquid "slosh" effect on spinning vehicles are unreliable unless they are validated against flight or test data. To the author's knowledge, this report contains the most extensive and varied data set available. As such, it should be a good resource for anyone seeking to develop and validate improved analytical techniques. All of the original digital data sets have been archived on disk, with copies provided to NASA/KSC. With some restrictions, many of these data sets can be made available to researchers within the United States. Whenever possible, spacecraft are identified by name in this report. However, several organizations provided access to data with the explicit proviso that their programs not be identified and that parameters be presented only in normalized form. These constraints have been respected.
The new information-oriented culture in which we find ourselves has created new relationships, new stimulating and expanding opportunities, new methods of doing our work, and new environments in which we carry out our work. An integral part of the NASA aerospace research and development (R and D) process is the scientific and technical information (STI) associated with it; it is both a raw material (input) and a product (output) of this process. Within this process, the NASA STI Program is tasked to provide information management and services, to ensure that accurate and timely STI is generated and entered into an appropriate information service and made available in a usable form to those who have a need for it; in essence, a means to exploit both internal (NASA corporate) and pertinent external (other governmental/industrial/foreign) information to meet the requirements of the R and D community. To understand the STI Program management issues, it is critical to understand the role of the STI Program in the context of the R and D process. STI management must become part of the accepted culture of the R and D community, but it cannot become so unless adopted and accepted by it. A start should be made now to integrate the NASA STI Program into the R and D infrastructure, including funding and operational control. Within this infrastructure, we must obtain management commitment, review and produce policy reflecting the organizational status, allocate responsibilities, and set to work on implementing the true requirements of the R and D community.
NASA Lewis Research Center is currently supporting 66 microgravity science and applications projects. The 66 projects are separated into 23 flight projects and 43 ground-based projects. The part of the NASA Lewis program dealing with flight experiments is divided into six areas: Combustion Science, Materials Science, Fluid Physics, Instrumentation/Equipment, Advanced Technology Development, and Space Station Multi-User Facility studies. The part of the NASA Lewis program dealing with ground-based experiments is coincidentally also divided into six areas: Electronic Materials, Combustion Science, Fluid Dynamics and Transport Phenomena, Metals and Alloys, Glasses and Ceramics, and Physics and Chemistry Experiments. Several purposes exist for ground-based experimenting. Preliminary information is necessary before a decision can be made for flight status, the short low gravity durations available in ground facilities are adequate for a particular study, or extensive ground-based research must be conducted to define and support the microgravity science endeavors contemplated for space. Not all of the 66 microgravity science and application projects at NASA Lewis have temperature requirements, but most do. Since space allocation does not permit a review of all the pertinent projects, a decision was made to restrict the coverage to the science flight projects, flight projects minus the advanced technology development, and multiuser facility efforts. Very little is lost by this decision as the types of temperature requirements for science flight projects can be considered representative of those for the ground-based projects. The noncontact temperature needs at NASA Lewis, as represented by the science flight projects are discussed by describing briefly the experiments themselves, by displaying an illustration of each experimental setup, and by specifying their temperature requisites.
Documentation of the preliminary software developed as a framework for a generalized integrated robotic system simulation is presented. The program structure is composed of three major functions controlled by a program executive. The three major functions are: system definition, analysis tools, and post processing. The system definition function handles user input of system parameters and definition of the manipulator configuration. The analysis tools function handles the computational requirements of the program. The post processing function allows for more detailed study of the results of analysis tool function executions. Also documented is the manipulator joint model software to be used as the basis of the manipulator simulation which will be part of the analysis tools capability.
Prompted by an increasing awareness of the influence of human activity on the chemistry of the global troposphere, a panel was formed to (1) assess the requirement for a global study of the chemistry of the troposphere; (2) develop a scientific strategy for a comprehensive plan taking into account the existing and projected programs of the government; (3) assess the requirements of a global study in terms of theoretical knowledge, numerical modeling, instrumentation, observing platforms, ground-level observational techniques, and other related needs; and (4) outline the appropriate sequence and coordination required to achieve the most effective utilization of available resources. Part 1 presents a coordinated national blueprint for scientific investigations of biogeochemical cycles in the global troposphere. part 2 presents much of the background information of the present knowledge and gaps in the understanding of tropospheric chemical cycles and processes from which the proposed program was developed.
“What gets measured gets done ”or “measure it to manage it”. The statements have become matter of fact. However, measurement (and even metrics) alone cannot fully communicate an organization’s story without the point of accountability. As a dynamic org, we must measure what is necessary, using the appropriate lenses to analyze the most relevant information that allows robust decision-making. A key function of Program Planning and Control (PP&C) is to assist HRP in the development of such strategy that ensures the proper execution of program research goals. With introspection of the Technical Officer role as defined by 2 CFR(i.e., Part 200, Part 1800)and subsequent governance under the NASA Grant and Cooperative Agreement Manual (GCAM), we’ve realized an obvious disconnect among Principal Investigator’s (PI),technical communication with the elements and some of the administrative/fiduciary requirements that should run parallel to the science work. This find has introduced new program risks as evidenced through incomplete deliverables or other less-than-successful requirements through the lifecycle for work we fund. One solution the Grants Technical Officer proposes is for PP&C to share in the communication with stakeholders of grants administration much earlier in the award process in attempt to reduce programmatic risks; particularly in data, reporting and performance management. As such, the planned IWS 2022 session will focus on(plenary) topics that include (1) definition of the grant lifecycle, (2) anatomy of a grant(NF1687 the award document), and (3)performance measurement/post-award monitoring. As HH&P pursues its strategic objectives to evolve the directorate into a data rich and knowledge rich organization, it has become increasingly important to develop the multiple levels of insight across the program to ensure data and other reporting(qualitative/quantitative), alongside proper administration. And the desired outcome is to make certain HRP meets/exceeds the accountability standard that our research information is received, maintained and accessible in posterity.
An experimental program was conducted for the purpose of evaluating propellant behavior characteristics in spinning toroidal tanks. The effects of typical mission requirements, and related phenomena upon propellant slosh and settling, and orientation and stability of the ullage were investigated in a subscale model tank under both one-g and low-g acceleration environments. Specific conditions included were axial acceleration, spin rate, spinrate change, and spacecraft wobble, both singly and in combination. Methanol and water in combination with appropriate spin-rates and accelerations of the scale model system were used to simulate the behavior of fluorine, nitrogen tetroxide, monomethylhydrazine, and hydrazine. The experimental results indicate that no major fluid behavior problems would be encountered with the use of toroidal tanks containing any of the four propellants in a proposed spin-stabilized orbiter spacecraft.
The FINESSE (Field Investigations to Enable Solar System Science and Exploration) team, part of the Solar System Exploration Virtual Institute (SSERVI), is a field-based research program aimed at generating strategic knowledge in preparation for human and robotic exploration of the Moon, near-Earth asteroids, Phobos and Deimos, and beyond. In contract to other technology-driven NASA analog studies, The FINESSE WCIS activity is science-focused and, moreover, is sampling-focused with the explicit intent to return the best samples for geochronology studies in the laboratory. We used the FINESSE field excursion to the West Clearwater Lake Impact structure (WCIS) as an opportunity to test factors related to sampling decisions. We examined the in situ sample characterization and real-time decision-making process of the astronauts, with a guiding hypothesis that pre-mission training that included detailed background information on the analytical fate of a sample would better enable future astronauts to select samples that would best meet science requirements. We conducted three tests of this hypothesis over several days in the field. Our investigation was designed to document processes, tools and procedures for crew sampling of planetary targets. This was not meant to be a blind, controlled test of crew efficacy, but rather an effort to explicitly recognize the relevant variables that enter into sampling protocol and to be able to develop recommendations for crew and backroom training in future endeavors.
The supershield project evaluated the importance of novel shield configurations for suppressing neutron induced background in new classes of gamma-ray detectors such as CZT. The basic concept was to use a two-part shield. The outer shield material heavily moderates the incoming neutron spectrum. This moderated neutron beam is then more easily absorbed by the inner material, which is an efficient neutron absorber. This approach is, in principle, more efficient than that in previous attempts to make neutron shields. These previous attempts involved biatomic, monlithic shields (eg. LiH) in which the shield consisted of a single material but with two types of atoms - one for moderating and one for absorbing. The problem with this type of monolithic shield is that moderating neutrons, without the efficient absorption of them, leads to the leakage into the detector of neutrons with a low energy component (approx. 10-100 KeV). These energy neutrons are particularly problematic for many types of detectors. The project was roughly divided into phases. In the first phase we attempted to carefully define the neutron source function incident on any space instrument. This is essential since the design of any shield depends on the shape of the incident neutron spectrum. We found that approximations commonly used in gamma-ray astronomy for photon background is inadequate. In addition, we found that secondary neutrons produced in any passive shield, and dominated by inelastic neutron scattering, are far more important than background due to neutron activation. The second phase of our work involved design of supershield geometries (one and three dimensional) in order to compare different shield configurations and materials for their effectiveness as neutron shields. Moreover we wanted to compare these supershields with previous neutron shields to confirm the performance differences between the supershield (two material) and monolithic (one material) designs and to understand the physics origins of these differences more clearly. The third phase of the supershield program involved the benchmarking of the supershield designs through direct experimental verification. This required fabricating various supershields and exposing them to beams of neutrons to directly characterize their performance. With explicit verification that our modeling procedures can be used with confidence, we are now in a position to design shields for realistic space geometries. Using the supershield modeling capacity developed as part of this program we are attempting to evaluate their utility for a specific proposed mission--the Energetic X-ray Imaging Survey Telescope (EXIST). It is anticipated that this experiment, which is limited by internal background at high energies, might benefit from a neutron shield.
As part of a modular inverter-converter development program, control techniques were developed to provide load sharing among paralleled inverters or converters. An analysis of the requirements of paralleling circuits and a discussion of the circuits developed and their performance are included in this report. The current sharing was within 5.6 percent of rated-load current for the ac modules and 7.4 percent for the dc modules for an initial output voltage unbalance of 5 volts.
The objective in the NASA Precision Segmented Reflector (PSR) project is to develop new composite material concepts for highly stable and durable reflectors with precision surfaces. The project focuses on alternate material concepts such as the development of new low coefficient of thermal expansion resins as matrices for graphite fiber reinforced composites, quartz fiber reinforced epoxies, and graphite reinforced glass. Low residual stress fabrication methods will be developed. When coupon specimens of these new material concepts have demonstrated the required surface accuracies and resistance to thermal distortion and microcracking, reflector panels will be fabricated and tested in simulated space environments. An important part of the program is the analytical modeling of environmental stability of these new composite materials concepts through constitutive equation development, modeling of microdamage in the composite matrix, and prediction of long term stability (including viscoelasticity). These analyses include both closed form and finite element solutions at the micro and macro levels.
A computer program builds application programming interfaces (APIs) and related software components for installing and uninstalling application programs in any of a variety of computers and operating systems that support the Java programming language in its binary form. This program is partly similar in function to commercial (e.g., Install-Shield) software. This program is intended to enable satisfaction of a quasi-industry-standard set of requirements for a set of APIs that would enable such installation and uninstallation and that would avoid the pitfalls that are commonly encountered during installation of software. The requirements include the following: 1) Properly detecting prerequisites to an application program before performing the installation; 2) Properly registering component requirements; 3) Correctly measuring the required hard-disk space, including accounting for prerequisite components that have already been installed; and 4) Correctly uninstalling an application program. Correct uninstallation includes (1) detecting whether any component of the program to be removed is required by another program, (2) not removing that component, and (3) deleting references to requirements of the to-be-removed program for components of other programs so that those components can be properly removed at a later time.