Search NASA⌕ Search

SEARCH · Search NASA

Results for “program verification”

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 1,657 records · Page 92

Explicit Finite Element Modeling of Multilayer Composite Fabric for Gas Turbine Engine Containment Systems, Phase II: Material Model Development and Simulation of Experiments - Part 3

A team consisting of Arizona State University, Honeywell Engines, Systems & Services, the National Aeronautics and Space Administration Glenn Research Center, and SRI International collaborated to develop computational models and verification testing for designing and evaluating turbine engine fan blade fabric containment structures. This research was conducted under the Federal Aviation Administration Airworthiness Assurance Center of Excellence and was sponsored by the Aircraft Catastrophic Failure Prevention Program. The research was directed toward improving the modeling of a turbine engine fabric containment structure for an engine blade-out containment demonstration test required for certification of aircraft engines. The research conducted in Phase II began a new level of capability to design and develop fan blade containment systems for turbine engines. Significant progress was made in three areas: (1) further development of the ballistic fabric model to increase confidence and robustness in the material models for the Kevlar(TradeName) and Zylon(TradeName) material models developed in Phase I, (2) the capability was improved for finite element modeling of multiple layers of fabric using multiple layers of shell elements, and (3) large-scale simulations were performed. This report concentrates on the material model development and simulations of the impact tests.

Zylon↗

Open-Source RTOS Space Qualification: An RTEMS Case Study

NASA space-qualification of reusable off-the-shelf real-time operating systems (RTOSs) remains elusive due to several factors notably (1) The diverse nature of RTOSs utilized across NASA, (2) No single NASA space-qualification criteria, lack of verification and validation (V&V) analysis, or test beds, and (3) different RTOS heritages, specifically open-source RTOSs and closed vendor-provided RTOSs. As a leader in simulation test beds, the NASA IV&V Program is poised to help jump-start and lead the space-qualification effort of the open source Real-Time Executive for Multiprocessor Systems (RTEMS) RTOS. RTEMS, as a case-study, can be utilized as an example of how to qualify all RTOSs, particularly the reusable non-commercial (open-source) ones that are gaining usage and popularity across NASA. Qualification will improve the overall safety and mission assurance of RTOSs for NASA-agency wide usage. NASA's involvement in space-qualification of an open-source RTOS such as RTEMS will drive the RTOS industry toward a more qualified and mature open-source RTOS product.

Real-time operating system↗

Advances in Rodent Research Missions on the International Space Station

A Research platform for rodent experiment on the ISS is an essential tool for advancing biomedical research in space. The Rodent Research allows for experiments of much longer duration that experiments on the Shuttle. NASA’s Rodent Research (RR)-1 mission was successfully completed, including post-flight analysis and achieved a number of objectives including validation of flight hardware, on-orbit operations, and science capabilities that were developed at the NASA Ames Research Center. Briefly, twenty C57BL/6J adult female mice were launched on the SpX4 Dragon vehicle, which thrived for up to 37 days in microgravity. Daily health checks of the mice were performed during the mission via downlinked video; all animals were healthy and displayed normal behavior without any significant signs of stress. Behavioral analysis demonstrated that Flight and Ground Control mice exhibited the same range of behaviors, including eating, drinking, exploratory behavior, self- and allo-grooming, and social interactions indicative of healthy animals. The animals were euthanized and select tissues were collected from some of the mice on orbit to assess the long-term sample storage capabilities of the ISS. The data obtained from the flight mice were comparable to those from the 3 groups of control mice (baseline, vivarium and ground controls), suggesting that the ISS has adequate capability to support long-duration rodent experimentations. We recovered over 35 tissues from 40 RR1 frozen carcasses, yielded over 3200 aliquots of tissues, and distributed to the scientific community, including NASA’s GeneLab and scientists in the U.S. through Biospecimen Sharing Program via Ames Life Science Data Archive. Tissues were also distributed to Russian research colleagues at the Institute for Biomedical Problems. The expression levels of select genes including albumin, catalase, GAPDH, HMGCoA Reductase, and IGF1 were determined using RNA isolated from the livers by qPCR and no significant differences by one factor ANOVA were found between flight and ground control groups. In addition, some of the liver samples were subject to transcriptomics, epigenomics and proteomics. The data are now available to the scientific community through GeneLab’s open science data website. Since the RR1 mission, another long duration mission (Rodent Research-2) was completed on the ISS in 2015 in which 20 female C57 BL/6J mice were successfully maintained on the ISS for varying time points, with the last group of 5 animals being on-orbit for 54 days. This second Rodent Research flight expanded the program’s capabilities with the introduction of new technologies including blood collection and separation and bone densitometry scanning. Furthermore, we have continued to expand the ISS’s capabilities by running a series of ground-based verification testing using male mice. Our next step is to fly male mice for Rodent Research-4 on SpaceX-10 to study the effects of microgravity on bone healing and regeneration. It will be the first long-duration mission using male mice using Rodent Hardware. In addition, the number of mice will increase from 20 mice (on RR-1 and RR-2) to 40 for RR-4. When samples return to Earth, a number of tissues will be dissected from the frozen carcasses and select tissue samples will become available to the scientific community via BSP. Altogether, we have continued to expand our capabilities for performing long-duration missions on the ISS as emphasized in the National Research Council’s Decadal Survey released in 2011 and to maximize science return from each mission.

Choi, S.↗

Transistor step stress program for JANTX2N2920

Data on the effect of power/temperature step stress when applied to the dual transistor JANTX2N2920 manufactured by Fairchild and National Semiconductor are presented. Fifty one (51) samples from Fairchild and 44 from National Semiconductor were submitted to the process outlined. In addition, two control sample units were maintained for verification of the electrical parametric testing.

Source record↗

The reduction, verification and interpretation of MAGSAT magnetic data over Canada

Consideration is being given to representing the magnetic field in the area 40 deg N to 83 deg N by means of functions in spherical coordinates. A solution to Laplace's equation for the magnetic potential over a restricted area was found, and programming and testing are currently being carried out. Magnetic anomaly modelling is proceeding. The program SPHERE, which was adapted to function correctly on the Cyber computer, is now operational, for deriving gravity and magnetic models in a spherical coordinate system.

Coles, R. L.↗

Scale 6.1 Enhancements for Nuclear Criticality Safety

The Scale code system developed at Oak Ridge National Laboratory provides a comprehensive, verified and validated, user-friendly tool set for criticality safety, reactor physics, radiation shielding, and sensitivity and uncertainty analysis. For more than 30 years, regulators, licensees, and research institutions around the world have used Scale for safety analysis and design. Scale provides a 'plug-and-play' framework with 89 computational modules, including three deterministic and three Monte Carlo radiation transport solvers that are selected based on the desired solution. Scale's graphical user interfaces assist with accurate system modeling and convenient access to desired results. Scale 6.1 builds on the existing capabilities and ease-of-use of Scale and provides several new features such as improved options and capabilities for sensitivity and uncertainty analysis calculations, improved flexibility in shielding and criticality accident alarm system calculations with automated variance reduction, and new options for the definition of group structures for depletion calculations. The Scale 6.1 development team has focused on improved robustness via substantial additional regression testing and verification for new and existing features, providing improved performance relative to Scale 6.0, especially in reactor physics calculations and in the nuclear data used for source term characterization and shielding calculations.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

Integral Full Core Multi-Physics PWR Benchmark with Measured Data

In recent years, the importance of modeling and simulation has been highlighted extensively in the DOE research portfolio with concrete examples in nuclear engineering with the CASL and NEAMS programs. These research efforts and similar efforts worldwide aim at the development of high-fidelity multi-physics analysis tools for the simulation of current and next-generation nuclear power reactors. Like all analysis tools, verification and validation is essential to guarantee proper functioning of the software and methods employed. The current approach relies mainly on the validation of single physic phenomena (e.g. critical experiment, flow loops, etc.) and there is a lack of relevant multiphysics benchmark measurements that are necessary to validate high-fidelity methods being developed today. This work introduces a new multi-cycle full-core Pressurized Water Reactor (PWR) depletion benchmark based on two operational cycles of a commercial nuclear power plant that provides a detailed description of fuel assemblies, burnable absorbers, in-core fission detectors, core loading and re-loading patterns. This benchmark enables analysts to develop extremely detailed reactor core models that can be used for testing and validation of coupled neutron transport, thermal-hydraulics, and fuel isotopic depletion. The benchmark also provides measured reactor data for Hot Zero Power (HZP) physics tests, boron letdown curves, and three-dimensional in-core flux maps from 58 instrumented assemblies. The benchmark description is now available online and has been used by many groups. However, much work remains to be done on the quantification of uncertainties and modeling sensitivities. This work aims to address these deficiencies and make this benchmark a true non-proprietary international benchmark for the validation of high-fidelity tools. This report details the BEAVRS uncertainty quantification for the first two cycle of operations and serves as the final report of the project.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

PCOR Partnership Best Practices Manual for Subsurface Technical Risk Assessment of Geologic CO 2 Storage Projects

In 2003, the U.S. Department of Energy established the Regional Carbon Sequestration Partnerships (RCSP) Initiative to help develop technology, infrastructure, and regulations needed to facilitate large-scale carbon dioxide (CO 2 ) geologic storage (herein “storage”) and support deployment of commercial carbon capture and storage projects. The Plains CO 2 Reduction (PCOR) Partnership, led by the Energy & Environmental Research Center (EERC), is one of seven partnerships created by this program. The PCOR Partnership is publishing a series of best practices manuals for each of the four PCOR Partnership-defined primary technical elements of a storage site: site characterization; modeling and simulation; risk assessment; and monitoring, verification, and accounting. This document describes the risk assessment process for evaluating subsurface technical risks associated with a CO 2 storage project. This best practices manual identifies the key elements comprising a risk assessment for a CO 2 storage complex and defines important risk management terminology and technical factors that are unique to the geologic storage of CO 2 . It also provides best practices for implementing a risk assessment based on lessons learned from conducting risk assessments for storage complexes within the PCOR Partnership region. Case studies of these real-world examples, which highlight key aspects of applying the risk assessment process to storage projects, are provided to support the proposed best practices. The development of a best practice requires the execution of multiple projects where the knowledge gained and lessons learned are accumulated over time and integrated to yield a best practice. This development progression is an adaptive management process whereby best practices constantly evolve over time in response to knowledge gained and lessons learned. This document encompasses the current body-of-knowledge and best practices for applying a standardized risk assessment approach within risk management for storage projects. Application of these best practices will provide reliable and consistent standards for identifying project-related risks, analyzing the probabilities and potential impacts of these risks, evaluating which risks require treatment, and determining priority for treatment implementation. These best practices will continue to evolve and be refined over time as commercialization of the CO 2 storage industry proceeds.

54 ENVIRONMENTAL SCIENCES↗

S4PST: Sustainability for Programming Systems and Tools: May Workshop Report

The US Department of Energy (DOE) Exascale Computing Project (ECP) has fostered and strengthened the use of modern software engineering practices for developing applications and libraries, and this effort has resulted in the coordinated and interoperable E4S1 and xSDK2 ecosystems. Although this approach is cost-effective, it relies on robust programming systems and tools (PST) as the underlying foundation for our HPC software. At present, our primary PST stack consists of traditional high-performance computing (HPC) languages, namely Fortran, C, C++, and the popular Python language for data analysis and AI workflows. These languages support various programming frameworks and run-time abstractions that enable parallelism and concurrency across multiple node architectures and thousands of nodes through a variety of interconnect systems. However, to accommodate users’ diverse needs, certain aspects of the HPC ecosystem are delegated to vendor-specific or third-party implementations that extend beyond a particular scientific domain. This broader scope results in a multitude of specifications and variations, which leads to a complex orchestration of many-ecosystems. Unfortunately, this complexity in the ecosystem imposes additional overhead costs on consumers during the latter stages of the development cycle. In addition to the software ecosystem challenge, the upcoming conclusion of the ECP by December 2023 has raised significant concerns within the HPC programming systems community, from both the economic and social perspectives. The ECP has implemented a management structure for software development and funding decisions across all ECP participants by following a conventional hierarchical and centralized approach. However, this structure has prompted certain considerations within the community, particularly in anticipation of the Software Sustainability initiative by the DOE’s Advanced Scientific Computing Research Program (ASCR). For the success of this new initiative, it is of utmost importance to secure consistent funding and foster close engagement with researchers and core developers of existing programming-system products. This collaboration is vital to maintaining the critical capabilities of the current software during the transition phase while proactively adapting to future technology and workforce trends. The community recognizes the significance of adapting to emerging trends and is aware of the inherent fragility of the HPC software ecosystem, particularly in relation to programming systems that cater to all users. The ability to adapt and evolve is essential to staying relevant and effectively addressing these technical, economic, and social challenges. The S4PST team, which represents one of the six ASCR Software Sustainability seedling projects, is dedicated to tackling these challenges through community-based approaches that go beyond the scope of the DOE. This involves collaboration between national laboratories with academia, non-DOE institutions, hardware and system vendors, and international partners. By fostering these partnerships, we aim to create a robust and sustainable HPC software ecosystem that can effectively meet the needs of the community. This new community effort, driven by the eight DOE labs, will take on the responsibility of guiding funding decisions for programming-systems development and maintenance with transparency and consistency across all decisions. Additionally, the team will offer common technical services to the programming systems community, irrespective of their funding situations, and facilitate community-wide incubation to proactively nurture the software ecosystem. By actively engaging with stakeholders and employing a collaborative approach, we can collectively shape the future of programming systems and ensure a robust and thriving HPC software landscape. On May 11–12, 2023, the S4PST team conducted its inaugural kick-off workshop at the Innovative Computing Laboratory (ICL) in the University of Tennessee, Knoxville, hosted by Hartwig Anzt. The workshop encompassed various sessions dedicated to presentations and discussions, with the aim of comprehending the team members’ perspectives on the vision of software sustainability. Additionally, the workshop aimed to identify the technical, economic, and social requirements for sustaining the programming-systems community in the field of HPC. This report provides a summary of the S4PST effort by highlighting five major thrust areas discussed during the workshop: (i) community, (ii) technical support, (iii) training and diversity, (iv) verification, validation and correctness, and (v) emerging technologies. It also encompasses an overview of the presentations and discussions held throughout the event, our views and potential synergies with other seedling efforts, along with the outcomes and key takeaways from our initial discussions.

97 MATHEMATICS AND COMPUTING↗

H2-O2 auxiliary power unit for space shuttle vehicles

A program to establish technology readiness of hydrogen-oxygen (H2-O2) auxiliary power units for use on board the space shuttle orbiter vehicle is discussed. Fundamental objectives include experimentally establishing an acceptable propellant flow control method, verification of combustor stability, and adequate thermal management. An initial APU configuration with recycled hydrogen flow has been studied and revised towards greater simplicity and scaling ease. The selected APU is a recuperated open-cycle, turbine-driven unit. Series flow of cryogenic hydrogen removes internally-generated heat and from the hydraulic system. Steady-state test of the combustor has been successful.

Joyce, J. P.↗

TERSSE: Definition of the Total Earth Resources System for the Shuttle Era. Volume 8: User's Mission and System Requirements Data (appendix A of Volume 3)

A computer printout is presented of the mission requirement for the TERSSE missions and their associated user tasks. The data included in the data base represents a broad-based attempt to define the amount, extent, and type of information needed for an earth resources management program in the era of the space shuttle. An effort was made to consider all aspects of remote sensing and resource management; because of its broad scope, it is not intended that the data be used without verification for in-depth studies of particular missions and/or users. The data base represents the quantitative structure necessary to define the TERSSE architecture and requirements, and to an overall integrated view of the earth resources technology requirements of the 1980's.

Source record↗

The effect of nonlinearities on the dynamic response of a large shuttle payload

The STS Centaur was designed to be a high energy upper stage for use with the Space Shuttle. Two versions were designed under development when the program was cancelled. The first version, designated G-prime, was for planetary missions. The second version, designated G, was to place spacecraft in geosynchronous orbit. As a part of the STS Centaur finite-element model verification effort, test articles of both versions were subjected to a series of static tests. In addition the Centaur G-prime test article was subjected to a series of dynamic tests including a modal survey. Both the static and dynamic tests showed that nonlinearities existed in the Centaur and its support system. The support system included flight-like latches. The nonlinearities were particularly apparent in tests that loaded the forward support structure of the Centaur. These test results were used to aid in the development of two improved finite-element models. The first was a linear model, while the second contained nonlinear elements at the boundaries. Results from both models were compared with the transient response obtained from a step-relaxation or twang test. The linear model was able to accurately match the low frequency response found in the test data. However, only the nonlinear model was able to match higher frequency response that was present in some of the test data. In addition the nonlinear model was able to predict other nonlinear behavior such as the dynamic jump that occurs in systems with nonlinear stiffness.

Sullivan, Timothy L.↗

Collected software engineering papers, volume 3

Topics addressed include: software technology evaluation programs; collection of valid software engineering data; test processes using structural coverage; prototype expert system for software engineering management; use of an environment characteristic software metric set; software modulation; software development by analysis of change; and independent verification and validation.

Source record↗

Comparison of ORSAT and SCARAB Reentry Analysis Tools for a Generic Satellite Test Case

Reentry analysis is essential to understanding the consequences of the full life cycle of a spacecraft. Since reentry is a key factor in spacecraft development, NASA and ESA have separately developed tools to assess the survivability of objects during reentry. Criteria such as debris casualty area and impact energy are particularly important to understanding the risks posed to people on Earth. Therefore, NASA and ESA have undertaken a series of comparison studies of their respective reentry codes for verification and improvements in accuracy. The NASA Object Reentry Survival Analysis Tool (ORSAT) and the ESA Spacecraft Atmospheric Reentry and Aerothermal Breakup (SCARAB) reentry analysis tools serve as standard codes for reentry survivability assessment of satellites. These programs predict whether an object will demise during reentry and calculate the debris casualty area of objects determined to survive, establishing the reentry risk posed to the Earth's population by surviving debris. A series of test cases have been studied for comparison and the most recent uses "Testsat," a conceptual satellite composed of generic parts, defined to use numerous simple shapes and various materials for a better comparison of the predictions of these two codes. This study is an improvement on the others in this series because of increased consistency in modeling techniques and variables. The overall comparison demonstrated that the two codes arrive at similar results. Either most objects modeled resulted in close agreement between the two codes, or if the difference was significant, the variance could be explained as a case of semantics in the model definitions. This paper presents the main results of ORSAT and SCARAB for the Testsat case and discusses the sources of any discovered differences. Discussion of the results of previous comparisons is made for a summary of differences between the codes and lessons learned from this series of tests.

Kelley, Robert L.↗

Fault Management Architectures and the Challenges of Providing Software Assurance

The satellite systems Fault Management (FM) is focused on safety, the preservation of assets, and maintaining the desired functionality of the system. How FM is implemented varies among missions. Common to most is system complexity due to a need to establish a multi-dimensional structure across hardware, software and operations. This structure is necessary to identify and respond to system faults, mitigate technical risks and ensure operational continuity. These architecture, implementation and software assurance efforts increase with mission complexity. Because FM is a systems engineering discipline with a distributed implementation, providing efficient and effective verification and validation (VV) is challenging. A breakout session at the 2012 NASA Independent Verification Validation (IVV) Annual Workshop titled VV of Fault Management: Challenges and Successes exposed these issues in terms of VV for a representative set of architectures. NASA's IVV is funded by NASA's Software Assurance Research Program (SARP) in partnership with NASA's Jet Propulsion Laboratory (JPL) to extend the work performed at the Workshop session. NASA IVV will extract FM architectures across the IVV portfolio and evaluate the data set for robustness, assess visibility for validation and test, and define software assurance methods that could be applied to the various architectures and designs. This work focuses efforts on FM architectures from critical and complex projects within NASA. The identification of particular FM architectures, visibility, and associated VVIVV techniques provides a data set that can enable higher assurance that a satellite system will adequately detect and respond to adverse conditions. Ultimately, results from this activity will be incorporated into the NASA Fault Management Handbook providing dissemination across NASA, other agencies and the satellite community. This paper discusses the approach taken to perform the evaluations and preliminary findings from the research including identification of FM architectures, visibility observations, and methods utilized for VVIVV.

Fault Management↗

A Tailored Concept of Operations for NASA LSP Integrated Operations

An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this project is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services.

Systems↗

Tailoring a ConOps for NASA LSP Integrated Operations

An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this paper is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services. This tailoring effort was performed as the authors final Masters Project in the Spring of 2016 for the Stevens Institute of Technology and modified for publication with INCOSE (Owens, 2016).

Knowledge↗

Medical Data Architecture Platform and Recommended Requirements for a Medical Data System for Exploration Missions

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically- relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm of medical data management on the International Space Station. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products derived from the third MDA prototype development will directly inform exploration medical system requirements for Level of Care IV in Gateway missions. In fiscal year 2019, the MDA project developed Test Bed 3, the third iteration in a series of prototypes, that featured integrations with cognition tool data, ultrasound image analytics and core Flight Software (cFS). Maintaining a layered architecture design, the framework implemented a plug-in, modular approach in the integration of these external data sources. An early version of MDA Test Bed 3 software was deployed and operated in a simulated analog environment that was part of the Next Space Technologies for Exploration Partnerships (NextSTEP) Gateway tests of multiple habitat prototypes. In addition, the MDA team participated in the Gateway Test and Verification Demonstration, where the MDA cFS applications was integrated with Gateway-in-a-Box software to send and receive medically relevant data over a simulated vehicle network. This software demonstration was given to ExMC and Gateway Program stakeholders at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Also, the integrated prototypes served as a vehicle to provide Level 5 requirements for the Crew Health and Performance Habitat Data System for Gateway Missions (Medical Level of Care IV). In the upcoming fiscal year, the MDA project will continue to provide systems engineering and vertical prototypes to refine requirements for medical Level of Care IV and inform requirements for Level of Care V.

Krihak, M.↗