SEARCH · Search NASA
Results for “AIRS software development activities”
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.
Formal Methods Case Studies for DO-333
RTCA DO-333, Formal Methods Supplement to DO-178C and DO-278A provides guidance for software developers wishing to use formal methods in the certification of airborne systems and air traffic management systems. The supplement identifies the modifications and additions to DO-178C and DO-278A objectives, activities, and software life cycle data that should be addressed when formal methods are used as part of the software development process. This report presents three case studies describing the use of different classes of formal methods to satisfy certification objectives for a common avionics example - a dual-channel Flight Guidance System. The three case studies illustrate the use of theorem proving, model checking, and abstract interpretation. The material presented is not intended to represent a complete certification effort. Rather, the purpose is to illustrate how formal methods can be used in a realistic avionics software development project, with a focus on the evidence produced that could be used to satisfy the verification objectives found in Section 6 of DO-178C.
Thermal Model Development for Ares I-X
Thermal analysis for the Ares I-X vehicle has involved extensive thermal model integration, since thermal models of vehicle elements came from several different NASA and industry organizations. Many valuable lessons were learned in terms of model integration and validation. Modeling practices such as submodel, analysis group and symbol naming were standardized to facilitate the later model integration. Upfront coordination of coordinate systems, timelines, units, symbols and case scenarios was very helpful in minimizing integration rework. A process for model integration was developed that included pre-integration runs and basic checks of both models, and a step-by-step process to efficiently integrate one model into another. Extensive use of model logic was used to create scenarios and timelines for avionics and air flow activation. Efficient methods of model restart between case scenarios were developed. Standardization of software version and even compiler version between organizations was found to be essential. An automated method for applying aeroheating to the full integrated vehicle model, including submodels developed by other organizations, was developed.
Analysis and Recommendation of Tritium Gas Continuous Air Monitor Alarm Setpoints for the RPL Stack Exhaust
The Radiochemical Processing Laboratory (RPL) tritium continuous air monitor (CAM) is used for near real-time detection of tritium gas (i.e., elemental tritium [HT] and tritiated water vapor [HTO]) in the stack exhaust. The CAM interfaces with software developed by the Pacific Northwest National Laboratory (PNNL)—called the “PNNL OS3700 Tritium Monitoring Software”—that provides near real-time estimates of tritium gas air concentrations and integrated daily activities that are calculated from measured CAM counts. The OS3700 software implements alarm setpoints to alert the facility of larger tritium gas releases that if allowed to persist, could begin to challenge permitted emission and established dose constraints. This report performs a detailed review of historical and current tritium alarm setpoints used at RPL, including discussion of the technical basis used in their development, analysis of alarm frequencies using measured historical data, and performs a detailed dose assessment using more realistic release scenarios and meteorology. Based on the results, the tritium air concentration and integrated daily tritium activity alarm setpoints will remain 2.0 × 10 -5 µCi/ml and 25 Ci/day, respectively. These setpoints achieve the right operational balance in identifying larger releases from planned tritium work at RPL, without being overly conservative so as to cause nuisance alarming. Furthermore, implied doses associated with these setpoints are well below defined and regulatory limits.
Analysis and Recommendation of Alpha-Beta Continuous Air Monitor Alarm Setpoints for the RPL Stack Exhaust
The Radiochemical Processing Laboratory (RPL) alpha-beta continuous air monitor (CAM) is used for real-time detection of “artificial” alpha-beta particulates from the stack exhaust. The CAM interfaces with software developed by the Pacific Northwest National Laboratory—called the “PNNL OS3300 Alpha-Beta Monitoring Software”—that provides real-time estimates of alpha-beta air concentrations and integrated activities that are calculated from measured CAM counts. The OS3300 software has alarm setpoints that can be used to provide an early indication of larger releases, that if allowed to persist, could approach defined dose limits. This report performs a detailed review of historical and current alarm setpoints used at RPL, including discussion of the technical basis used in their development, analysis of alarm frequencies using measured historical data, and performs a detailed dose assessment using more realistic release scenarios, meteorology, and adjustment factors used in estimating released stack activity. Based on the results, the alpha and beta air concentration alarm setpoints will remain 1.77 × 10 -8 µCi/ml and 3.47 × 10 -8 µCi/ml, respectively; and the alpha and beta integrated activity alarm setpoints will remain 70.22 µCi and 137.63 µCi, respectively. These setpoints achieve the right operational balance in identifying larger releases from planned radiological work at RPL, without being overly conservative so as to cause nuisance alarming. Furthermore, implied doses associated with these setpoints are below defined and regulatory limits.
The NASA Urban Air Mobility Testbed Flight Research Aircraft
The National Aeronautics and Space Administration (NASA) is leading government, industry and academic research effort known as Urban Air Mobility (UAM). The UAM activity goal is to develop the technology needed to make possible an urban air transportation system that makes use of human-crewed and crewless vehicles using automation, artificial intelligence and other technologies to safely and efficiently air transport people and goods within an urban environment. The NASA Langley Research Center (LaRC) created a UAM Flight Research Testbed Aircraft from a Cessna LC40 general aviation aircraft. The testbed has updated digital avionics and research systems needed to conduct flight research. The aircraft has two separate autopilots; a standard Federal Aviation Ad-ministration (FAA) certified system, and a modified research autopilot. The research autopilot has modifications that allow increased authority and enhancements to allow more automation and artificial intelligence controls. A network of three research computers hosts software to research several activities including automated air traffic sense and avoid, ground collision avoidance and obstacle avoidance. These UAM research activities involve automation and artificial intelligence technologies developed at three NASA centers. The NASA Langley, NASA Armstrong, and NASA Ames Research Centers are working together to develop and test these UAM technologies. This paper provides details of the systems, capabilities and research projects of the UAM Testbed Research Aircraft.
Multi-Agent Diagnosis and Control of an Air Revitalization System for Life Support in Space
An architecture of interoperating agents has been developed to provide control and fault management for advanced life support systems in space. In this adjustable autonomy architecture, software agents coordinate with human agents and provide support in novel fault management situations. This architecture combines the Livingstone model-based mode identification and reconfiguration (MIR) system with the 3T architecture for autonomous flexible command and control. The MIR software agent performs model-based state identification and diagnosis. MIR identifies novel recovery configurations and the set of commands required for the recovery. The AZT procedural executive and the human operator use the diagnoses and recovery recommendations, and provide command sequencing. User interface extensions have been developed to support human monitoring of both AZT and MIR data and activities. This architecture has been demonstrated performing control and fault management for an oxygen production system for air revitalization in space. The software operates in a dynamic simulation testbed.
[X-33 Systems]
Lockheed Martin Skunk Works has compiled an Annual Performance Report of the X-33/RLV Program. This report consists of individual reports from all industry team members, as well as NASA team centers. This portion of the report is comprised of a status report of Allied-Signal Aerospace's contribution to the program. The following is a summary of the work reviewed under their portion of the agreement: (1) Communication Systems; (2) Environmental Control Systems- Active Thermal Control System (ATCS), Purge and Vent System, Hydrogen Detection System (HDS), Avionics Bay Inerting System (ABIS), and Flush Air Data System (FADS); (2) Landing Systems; (3) Power Management and Generation Systems; (4) Flight Control Actuation System (FCAS)- Electric Power Control & Distribution System (EPCDS), and Battery Power System (BPS); and (5) Vehicle Management Systems (VMS)- VMS Hardware, VMS Software Development Activities, and System Integration Laboratory (SIL).
Argonne News Brief: First Sensors for Chicago’s “City Fitness Tracker”
This week in Chicago, the Array of Things team installed its first 50 nodes on city streets to kick off the groundbreaking urban sensing project. Array of Things is designed as a “fitness tracker” for the city, collecting new streams of data on Chicago’s environment, infrastructure, and activity. This hyper-local, open data can help researchers, city officials, and software developers study and address critical city challenges, such as preventing urban flooding, improving traffic safety and air quality, and assessing the nature and impact of climate change.
CGNS Mid-Level Software Library and Users Guide
The "CFD General Notation System" (CGNS) consists of a collection of conventions, and conforming software, for the storage and retrieval of Computational Fluid Dynamics (CFD) data. It facilitates the exchange of data between sites and applications, and helps stabilize the archiving of aerodynamic data. This effort was initiated in order to streamline the procedures in exchanging data and software between NASA and its customers, but the goal is to develop CGNS into a National Standard for the exchange of aerodynamic data. The CGNS development team is comprised of members from Boeing Commercial Airplane Group, NASA-Ames, NASA-Langley, NASA-Lewis, McDonnell-Douglas Corporation (now Boeing-St. Louis), Air Force-Wright Lab., and ICEM-CFD Engineering. The elements of CGNS address all activities associated with the storage of data on external media and its movement to and from application programs. These elements include: - The Advanced Data Format (ADF) Database manager, consisting of both a file format specification and its I/O software, which handles the actual reading and writing of data from and to external storage media; - The Standard Interface Data Structures (SIDS), which specify the intellectual content of CFD data and the conventions governing naming and terminology; - The SIDS-to-ADF File Mapping conventions, which specify the exact location where the CFD data defined by the SIDS is to be stored within the ADF file(s); and - The CGNS Mid-level Library, which provides CFD-knowledgeable routines suitable for direct installation into application codes. The CGNS Mid-level Library was designed to ease the implementation of CGNS by providing developers with a collection of handy I/O functions. Since knowledge of the ADF core is not required to use this library, it will greatly facilitate the task of interfacing with CGNS. There are currently 48 user callable functions that comprise the Mid-level library and are described in the Users Guide. The library is written in C, but each function has a FORTRAN counterpart.
Regenerable Air Purification System for Gas-Phase Contaminant Control
A regenerable air purification system (RAPS) that uses water vapor to displace adsorbed contaminants from an. adsorbent column into a closed oxidation loop is under development through cooperative R&D between Vanderbilt University and NASA Ames Research Center. A unit based on this design can be used for removing trace gas-phase contaminants from spacecraft cabin air or from polluted process streams including incinerator exhaust. Recent work has focused on fabrication and operation of a RAPS breadboard at NASA Ames, and on measurement of adsorption isotherm data for several important organic compounds at Vanderbilt. These activities support the use and validation of RAPS modeling software also under development at Vanderbilt, which will in turn be used to construct a prototype system later in the project.
A NASA-wide approach toward cost-effective, high-quality software through reuse
NASA Langley Research Center sponsored the second Workshop on NASA Research in Software Reuse on May 5-6, 1992 at the Research Triangle Park, North Carolina. The workshop was hosted by the Research Triangle Institute. Participants came from the three NASA centers, four NASA contractor companies, two research institutes and the Air Force's Rome Laboratory. The purpose of the workshop was to exchange information on software reuse tool development, particularly with respect to tool needs, requirements, and effectiveness. The participants presented the software reuse activities and tools being developed and used by their individual centers and programs. These programs address a wide range of reuse issues. The group also developed a mission and goals for software reuse within NASA. This publication summarizes the presentations and the issues discussed during the workshop.
R&D to Market Success: BTO-Supported Technologies Commercialized from 2010-2015
Technology commercialization plays an essential role in almost every facet of the U.S. economy. It spurs private sector funding that supports innovative breakthroughs, drives growth through increased productivity and product development, increases American competitiveness, and creates domestic jobs. The BTO Technology Commercialization report is an annual publication offering the latest information on successfully commercialized technologies resulting in part from BTO’s research partnerships. This report defines a “commercialized technology” as a process, technique, design, machine, tool, material, or software that was developed with funds provided at least in part by BTO, and that has resulted in domestic sales or is in use in the U.S. This definition also applies to open-source software products developed with support from BTO, all of which are currently distributed freely but are actively used for commercial purposes.
Open-air Demolition: Validation of EPA Approved Alternative Method for Emission Estimation - 19397
Emissions from open-air demolition of US Department of Energy (DOE) facilities are regulated by the US Environmental Protection Agency (EPA) under 40 CFR 61 subpart H. This regulation requires that facilities estimate emissions using an EPA approved method from activities such as open-air demolition prior to commencing the activity. Should those emissions exceed certain thresholds, the facility may be required to obtain an Approval to Construct or Modify the facility and/or installed monitoring methods meeting methods acceptable to EPA. There are no EPA approved methods that are specific to open-air demolition methods. For this project the DOE and CH2M Hill BWXT elected to prepare an alternative method specific to open-air demolition. EPA conditionally approved the method but required validation of the method during the demolition of the Vitrification Facility at the West Valley Demonstration Project (WVDP) before use for open-air demolition at other WVDP structures. The validation method included detailed source characterization, close-in ambient samplers, and a comparison of measured results to predicted emissions using AERMOD (American Meteorological Society (AMS) and U.S. Environmental Protection Agency (EPA) Regulatory Model). The methods evaluated include hydraulic hammers, mechanical shears, load out of waste and handling of the debris piles. The validation method involved the collection and analysis of ambient air samples from air samplers located at strategic locations within the projected plume path of the demolition activities. The analytical results from the air samplers were then compared to ambient air concentrations predicted at the sampler locations with the EPA model AERMOD. The input to the AERMOD software is a source term developed weekly using the alternative method and material at risk disturbed during each week. To account for the building wake effects of the surrounding structures, virtual point sources were developed in the AERMOD model and placed at the locations of the demolition, debris piles, debris handling and load out areas. It was found that the factors used for hydraulic hammering were extremely conservative and that emissions from the debris pile were not only the primary emission source, but that the moisture content of the debris pile and the wind speed were critical factors that must be considered in future open-air demolition projects. Based on the results of the validation process, adjustments were made to the alternative method. The final validated alternative method provides an approach for estimating airborne emissions from open-air demolition methods and techniques. The method will be used in lieu of 40 CFR 61 Appendix D to estimate emissions from future open-air demolition projects at the WVDP. (authors)
NASA's UAS Integration into the NAS: A Report on the Human Systems Integration Phase 1 Simulation Activities
In 2011 the National Aeronautics and Space Administration (NASA) began a five-year Project to address the technical barriers related to routine access of Unmanned Aerial Systems (UAS) in the National Airspace System (NAS). Planned in two phases, the goal of the first phase was to lay the foundations for the Project by identifying those barriers and key issues to be addressed to achieve integration. Phase 1 activities were completed two years into the five-year Project. The purpose of this paper is to review activities within the Human Systems Integration (HSI) subproject in Phase 1 toward its two objectives: 1) develop GCS guidelines for routine UAS access to the NAS, and 2) develop a prototype display suite within an existing Ground Control Station (GCS). The first objective directly addresses a critical barrier for UAS integration into the NAS - a lack of GCS design standards or requirements. First, the paper describes the initial development of a prototype GCS display suite and supporting simulation software capabilities. Then, three simulation experiments utilizing this simulation architecture are summarized. The first experiment sought to determine a baseline performance of UAS pilots operating in civil airspace under current instrument flight rules for manned aircraft. The second experiment examined the effect of currently employed UAS contingency procedures on Air Traffic Control (ATC) participants. The third experiment compared three GCS command and control interfaces on UAS pilot response times in compliance with ATC clearances. The authors discuss how the results of these and future simulation and flight-testing activities contribute to the development of GCS guidelines to support the safe integration of UAS into the NAS. Finally, the planned activities for Phase 2, including an integrated human-in-the-loop simulation and two flight tests are briefly described.
Development of the Orion Life-Support Integration Facility (OLIF)
Testing the life support hardware of a vehicle that is going to take humans beyond low-Earth orbit (LEO) in conditions similar to space is crucial. The Orion Life-Support Integration Facility (OLIF) at NASA Johnson Space Center (JSC) was designed and built to test the Orion vehicle’s hardware and software as integrated systems to provide a complete Environmental Control and Life Support System (ECLSS) system-level qualification. The existing 11 Foot human rated vacuum chamber has been adapted to accommodate and integrate various qualification and flight like components of the Orion vehicle’s Air Revitalization System (ARS), Pressure Control System (PCS), Active Thermal Control System (ATCS) and the Orion Crew Survival System Suits (OCSS). The ultimate goal was to create an analog testbed that could safely support up to four test subjects in open “shirt-sleeve” or closed suit loop configurations and simulate Orion Cabin conditions. This integrated hardware/software ARS and PCS will help identify any technical issues that should be addressed prior to the Artemis-2 mission. This paper will discuss the history of Orion ECLSS hardware development testing in the 11 Foot Chamber, the challenge of integrating flight hardware and software control systems, and the capabilities that make it a unique, world class facility for NASA. It will provide an overview of past and future testing, and the lessons learned along the way.
SIDS-toADF File Mapping Manual
The "CFD General Notation System" (CGNS) consists of a collection of conventions, and conforming software, for the storage and retrieval of Computational Fluid Dynamics (CFD) data. It facilitates the exchange of data between sites and applications, and helps stabilize the archiving of aerodynamic data. This effort was initiated in order to streamline the procedures in exchanging data and software between NASA and its customers, but the goal is to develop CGNS into a National Standard for the exchange of aerodynamic data. The CGNS development team is comprised of members from Boeing Commercial Airplane Group, NASA-Ames, NASA-Langley, NASA-Lewis, McDonnell-Douglas Corporation (now Boeing-St. Louis), Air Force-Wright Lab., and ICEM-CFD Engineering. The elements of CGNS address all activities associated with the storage of data on external media and its movement to and from application programs. These elements include: 1) The Advanced Data Format (ADF) Database manager, consisting of both a file format specification and its I/O software, which handles the actual reading and writing of data from and to external storage media; 2) The Standard Interface Data Structures (SIDS), which specify the intellectual content of CFD data and the conventions governing naming and terminology; 3) The SIDS-to-ADF File Mapping conventions, which specify the exact location where the CFD data defined by the SIDS is to be stored within the ADF file(s); and 4) The CGNS Mid-level Library, which provides CFD-knowledgeable routines suitable for direct installation into application codes. The SIDS-toADF File Mapping Manual specifies the exact manner in which, under CGNS conventions, CFD data structures (the SIDS) are to be stored in (i.e., mapped onto) the file structure provided by the database manager (ADF). The result is a conforming CGNS database. Adherence to the mapping conventions guarantees uniform meaning and location of CFD data within ADF files, and thereby allows the construction of universal software to read and write the data.
Advanced Data Format (ADF) Software Library and Users Guide
The "CFD General Notation System" (CGNS) consists of a collection of conventions, and conforming software, for the storage and retrieval of Computational Fluid Dynamics (CFD) data. It facilitates the exchange of data between sites and applications, and helps stabilize the archiving of aerodynamic data. This effort was initiated in order to streamline the procedures in exchanging data and software between NASA and its customers, but the goal is to develop CGNS into a National Standard for the exchange of aerodynamic data. The CGNS development team is comprised of members from Boeing Commercial. Airplane Group, NASA-Ames, NASA-Langley, NASA-Lewis, McDonnell-Douglas Corporation (now Boeing-St. Louis), Air Force-Wright Lab., and ICEM-CFD Engineering. The elements of CGNS address all activities associated with the storage of data on external media and its movement to and from application programs. These elements include: 1) The Advanced Data Format (ADF) Database manager, consisting of both a file format specification and its 1/0 software, which handles the actual reading and writing of data from and to external storage media; 2) The Standard Interface Data Structures (SIDS), which specify the intellectual content of CFD data and the conventions governing naming and terminology; 3) The SIDS-to-ADF File Mapping conventions, which specify the exact location where the CFD data defined by the SIDS is to be stored within the ADF file(s); and 4) The CGNS Mid-level Library, which provides CFD-knowledgeable routines suitable for direct installation into application codes. The ADF is a generic database manager with minimal intrinsic capability. It was written for the purpose of storing large numerical datasets in an efficient, platform independent manner. To be effective, it must be used in conjunction with external agreements on how the data will be organized within the ADF database such defined by the SIDS. There are currently 34 user callable functions that comprise the ADF Core library and are described in the Users Guide. The library is written in C, but each function has a FORTRAN counterpart.