Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Software Requirements”

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,171 records · Page 65
All sourcesNASA NTRSDOE OSTI
NASA NTRS2007

Zero-Propellant Maneuver[TM] Flight Results for 180 deg ISS Rotation

This paper presents results for the Zero Propellant Maneuver (ZPM) TradeMark attitude control concept flight demonstration. On March 3, 2007, a ZPM was used to reorient the International Space Station 180 degrees without using any propellant. The identical reorientation performed with thrusters would have burned 110lbs of propellant. The ZPM was a pre-planned trajectory used to command the CMG attitude hold controller to perform the maneuver between specified initial and final states while maintaining the CMGs within their operational limits. The trajectory was obtained from a PseudoSpectral solution to a new optimal attitude control problem. The flight test established the breakthrough capability to simultaneously perform a large angle attitude maneuver and momentum desaturation without the need to use thrusters. The flight implementation did not require any modifications to flight software. This approach is applicable to any spacecraft that are controlled by momentum storage devices.

Bedrossian, Nazareth↗
NASA NTRS2010

Development of the Data Acquisition and Processing System for a Pulsed 2-Micron Coherent Doppler Lidar System

A general overview of the development of a data acquisition and processing system is presented for a pulsed, 2-micron coherent Doppler Lidar system located in NASA Langley Research Center in Hampton, Virginia, USA. It is a comprehensive system that performs high-speed data acquisition, analysis, and data display both in real time and offline. The first flight missions are scheduled for the summer of 2010 as part of the NASA Genesis and Rapid Intensification Processes (GRIP) campaign for the study of hurricanes. The system as well as the control software is reviewed and its requirements and unique features are discussed.

Beyon, Jeffrey Y.↗
NASA NTRS2011

Software Productivity of Field Experiments Using the Mobile Agents Open Architecture with Workflow Interoperability

We analyzed a series of ten systematically developed surface exploration systems that integrated a variety of hardware and software components. Design, development, and testing data suggest that incremental buildup of an exploration system for long-duration capabilities is facilitated by an open architecture with appropriate-level APIs, specifically designed to facilitate integration of new components. This improves software productivity by reducing changes required for reconfiguring an existing system.

Clancey, William J.↗
NASA NTRS2013

Open Source Subtitle Editor Software Study for Section 508 Close Caption Applications

This paper will focus on a specific item within the NASA Electronic Information Accessibility Policy - Multimedia Presentation shall have synchronized caption; thus making information accessible to a person with hearing impairment. This synchronized caption will assist a person with hearing or cognitive disability to access the same information as everyone else. This paper focuses on the research and implementation for CC (subtitle option) support to video multimedia. The goal of this research is identify the best available open-source (free) software to achieve synchronized captions requirement and achieve savings, while meeting the security requirement for Government information integrity and assurance. CC and subtitling are processes that display text within a video to provide additional or interpretive information for those whom may need it or those whom chose it. Closed captions typically show the transcription of the audio portion of a program (video) as it occurs (either verbatim or in its edited form), sometimes including non-speech elements (such as sound effects). The transcript can be provided by a third party source or can be extracted word for word from the video. This feature can be made available for videos in two forms: either Soft-Coded or Hard-Coded. Soft-Coded is the more optional version of CC, where you can chose to turn them on if you want, or you can turn them off. Most of the time, when using the Soft-Coded option, the transcript is also provided to the view along-side the video. This option is subject to compromise, whereas the transcript is merely a text file that can be changed by anyone who has access to it. With this option the integrity of the CC is at the mercy of the user. Hard-Coded CC is a more permanent form of CC. A Hard-Coded CC transcript is embedded within a video, without the option of removal.

Murphy, F. Brandon↗
NASA NTRS2013

Human Machine Interface Programming and Testing

Human Machine Interface (HMI) Programming and Testing is about creating graphical displays to mimic mission critical ground control systems in order to provide NASA engineers with the ability to monitor the health management of these systems in real time. The Health Management System (HMS) is an online interactive human machine interface system that monitors all Kennedy Ground Control Subsystem (KGCS) hardware in the field. The Health Management System is essential to NASA engineers because it allows remote control and monitoring of the health management systems of all the Programmable Logic Controllers (PLC) and associated field devices. KGCS will have equipment installed at the launch pad, Vehicle Assembly Building, Mobile Launcher, as well as the Multi-Purpose Processing Facility. I am designing graphical displays to monitor and control new modules that will be integrated into the HMS. The design of the display screen will closely mimic the appearance and functionality of the actual modules. There are many different field devices used to monitor health management and each device has its own unique set of health management related data, therefore each display must also have its own unique way to display this data. Once the displays are created, the RSLogix5000 application is used to write software that maps all the required data read from the hardware to the graphical display. Once this data is mapped to its corresponding display item, the graphical display and hardware device will be connected through the same network in order to test all possible scenarios and types of data the graphical display was designed to receive. Test Procedures will be written to thoroughly test out the displays and ensure that they are working correctly before being deployed to the field. Additionally, the Kennedy Ground Controls Subsystem's user manual will be updated to explain to the NASA engineers how to use the new module displays.

Foster, Thomas Garrison↗
NASA NTRS2015

Reliability and Probabilistic Risk Assessment - How They Play Together

PRA methodology is one of the probabilistic analysis methods that NASA brought from the nuclear industry to assess the risk of LOM, LOV and LOC for launch vehicles. PRA is a system scenario based risk assessment that uses a combination of fault trees, event trees, event sequence diagrams, and probability and statistical data to analyze the risk of a system, a process, or an activity. It is a process designed to answer three basic questions: What can go wrong? How likely is it? What is the severity of the degradation? Since 1986, NASA, along with industry partners, has conducted a number of PRA studies to predict the overall launch vehicles risks. Planning Research Corporation conducted the first of these studies in 1988. In 1995, Science Applications International Corporation (SAIC) conducted a comprehensive PRA study. In July 1996, NASA conducted a two-year study (October 1996 - September 1998) to develop a model that provided the overall Space Shuttle risk and estimates of risk changes due to proposed Space Shuttle upgrades. After the Columbia accident, NASA conducted a PRA on the Shuttle External Tank (ET) foam. This study was the most focused and extensive risk assessment that NASA has conducted in recent years. It used a dynamic, physics-based, integrated system analysis approach to understand the integrated system risk due to ET foam loss in flight. Most recently, a PRA for Ares I launch vehicle has been performed in support of the Constellation program. Reliability, on the other hand, addresses the loss of functions. In a broader sense, reliability engineering is a discipline that involves the application of engineering principles to the design and processing of products, both hardware and software, for meeting product reliability requirements or goals. It is a very broad design-support discipline. It has important interfaces with many other engineering disciplines. Reliability as a figure of merit (i.e. the metric) is the probability that an item will perform its intended function(s) for a specified mission profile. In general, the reliability metric can be calculated through the analyses using reliability demonstration and reliability prediction methodologies. Reliability analysis is very critical for understanding component failure mechanisms and in identifying reliability critical design and process drivers. The following sections discuss the PRA process and reliability engineering in detail and provide an application where reliability analysis and PRA were jointly used in a complementary manner to support a Space Shuttle flight risk assessment.

Safie, Fayssal M.↗
NASA NTRS2016

Empirical Analysis and Automated Classification of Security Bug Reports

With the ever expanding amount of sensitive data being placed into computer systems, the need for effective cybersecurity is of utmost importance. However, there is a shortage of detailed empirical studies of security vulnerabilities from which cybersecurity metrics and best practices could be determined. This thesis has two main research goals: (1) to explore the distribution and characteristics of security vulnerabilities based on the information provided in bug tracking systems and (2) to develop data analytics approaches for automatic classification of bug reports as security or non-security related. This work is based on using three NASA datasets as case studies. The empirical analysis showed that the majority of software vulnerabilities belong only to a small number of types. Addressing these types of vulnerabilities will consequently lead to cost efficient improvement of software security. Since this analysis requires labeling of each bug report in the bug tracking system, we explored using machine learning to automate the classification of each bug report as a security or non-security related (two-class classification), as well as each security related bug report as specific security type (multiclass classification). In addition to using supervised machine learning algorithms, a novel unsupervised machine learning approach is proposed. An ac- curacy of 92%, recall of 96%, precision of 92%, probability of false alarm of 4%, F-Score of 81% and G-Score of 90% were the best results achieved during two-class classification. Furthermore, an accuracy of 80%, recall of 80%, precision of 94%, and F-score of 85% were the best results achieved during multiclass classification.

Cybersecurity↗
NASA NTRSDate not supplied

Analytical Partial Derivatives of the Q-Law Guidance Algorithm

One method of producing low-thrust trajectories is the closed-loop Q-Law guidance algorithm. This work wraps Q-Law inside a nonlinear programming problem to search for locally optimal gain combinations and enforce nonlinear constraints on the initial state. Gradient-based trajectory optimization has been shown to benefit greatly when analytical partial derivatives are supplied to the optimizer. This paper presents the Q-Law optimization problem setup and derives the Q-Law thrust vector partial derivatives for the State Transition Matrix required by standard nonlinear optimization software.

Jackson L Shannon↗
NASA NTRSDate not supplied

Design and Testing of an Approach to Automated In-Flight Safety Risk Management for sUAS Operations

An onboard risk management automation design is presented based on run-time assurance principles, as well as the concept for In-Time Aviation Safety Management Systems (IASMS) as described by the National Academies. The automation is designed to operate independently of the autopilot and perform real-time risk assessment spanning multiple classes of hazards, predict constraint violations, and track autopilot states. In the event of elevated risk conditions or predicted constraint violations, the automation will select from a set of available contingencies and trigger autopilot mode changes if necessary to mitigate risk exposure. The onboard automation also informs the remote operator/pilot of what the independent monitor is observing and any contingency decisions or actions that may arise during flight. Details of an implementation of this design and results of verification and validation activities, as required to meet stringent NASA software and system assurance standards, are also presented. This includes simulation and flight testing using small unmanned aircraft systems.

Ersin Ancel↗
NASA NTRS2023

Easy, Scalable Subsetting of GEDI Point Clouds

The GEDI Subsetter, a Python tool developed for NASA’s Multi-mission Algorithm and Analysis Platform (MAAP), optimizes the accessibility and visualization of GEDI point clouds by enabling users to efficiently subset data in a convenient, scalable manner. Complex science data often requires users to learn new software skills and handle many large files. Handling and cleaning large data sets is tedious and error-prone. These challenges significantly impede analysis. One of the goals of NASA's MAAP is to provide a platform that lowers the barrier to conducting research and analysis at scale. When a group of MAAP users wanted to conduct above-ground biomass estimation using GEDI data, we found that their existing workflow for leveraging GEDI data suffered from the barriers mentioned above. Furthermore, their workflow did not scale easily beyond a small number of granules. We found that existing tools related to GEDI data retrieval and subsetting were too limiting, so the GEDI Subsetter was written to support MAAP users’ needs. Being able to run many subsetting jobs simultaneously in the MAAP, and parallelizing the code itself, has led to significant speed improvements in obtaining relevant data, reducing subsetting time from hours to minutes. MAAP users can now more quickly and easily obtain only the data relevant to their research, by choosing which GEDI collection they want to work with (L1A, L2A, L2B, or L4A), and how they want to subset it, by specifying an area of interest, a temporal range, and relevant attributes. This has significantly reduced the feedback loop for users, allowing them to much more quickly subset GEDI data and begin their analysis. Although the GEDI Subsetter originally targeted users of the MAAP, it is generalized such that it can also be used outside of the MAAP and includes a command-line interface for convenience. Furthermore, with minor modifications, it should be possible to use it with non-GEDI data as the general pattern should be applicable to other sparse/track-based sensors.

Charles Daniels↗
DOE OSTI2020

All Hands On Deck: Raising the Bar on Whole Building Performance-Based Code Compliance and Above-Code Programs

In 2019 a large-scale national effort was launched with support from U.S. Department of Energy, Pacific Northwest National Laboratory and Northwest Energy Efficiency Alliance (NEEA). The project aimed to develop a long-term vision and a roadmap for achieving a practical application of whole building performance-based code and above code program compliance in commercial buildings. The work was aided by engaging over 70 stakeholders across the country representing jurisdictions, above-code programs such as LEED and ENERGY STAR Multifamily Program, members of the ASHRAE Standard 90.1 and other Standard committees, IBPSA and software developers. The performance path requires whole building energy modeling and is gaining momentum. Many see it as the future of the commercial energy codes and the main pathway for achieving zero energy buildings. The paper describes the findings from a stakeholder survey funded by NEEA on the current state of performance-based path, its market penetration, trends, implementation practices and adoption challenges. It discusses the patterns revealed by experience of the states with decades-long history of performance-based compliance such as Florida and California and opportunities for taking advantage of the synergies between code and above-code programs. In addition, the paper provides an overview of the tools and resources developed as part of the effort including the compliance form for ASHRAE Standard 90.1 Section 11 and Appendix G, modeling submittal review manual, and modeler and reviewer qualification requirements. The tools and resources would help remove market barriers, deliver immediate benefits to jurisdictions and rating authorities, and achieve energy efficiency through whole-building performance path.

TSPR, Performance Based Complinace, Washington Sta↗
DOE OSTI2022

Nuclear Quality Assurance Certification of the MCNP-ORIGEN Activation Automation tool

The MCNP-ORIGEN Activation Automation (MOAA) tool couples MCNP and ORIGEN-S, allowing to support ATR and TREAT experiments by predicting their composition and activity before their irradiation takes place. MOAA is developed and maintained by the Irradiation Experiment Neutronics Analysis group (C-150) at INL. This poster presents the motivation behind the development of MOAA, its main workflow, as well as the software quality assurance (SQA) efforts required by LWP-13620, "Managing Information Technology Assets."

07 ISOTOPE AND RADIATION SOURCES↗
DOE OSTI2024

Toolpath considerations for DED: Arc and laser welding

Directed energy deposition (DED) is a form of additive manufacturing that uses localized melted metal, similar to traditional arc welding, to construct an object. In comparison to polymer systems, metal systems can exert additional control over the build process through manipulation of the pool of melted metal, called the “melt pool.” This is especially important to maintain appropriate layer heights and create high quality builds. Additionally, metal systems allow site-specific control of the printed part, which enables advanced construction techniques that would otherwise not be possible. However, both of these types of control require support from the slicing software and, potentially, sensor feedback. This chapter will discuss these control processes and their basic implementation in a slicing program. The processes described here lay the foundation for more advanced solutions, particularly sensor feedback, that will be discussed later.

Borish, Michael↗
NASA NTRS1993

An assessment of space shuttle flight software development processes

In early 1991, the National Aeronautics and Space Administration's (NASA's) Office of Space Flight commissioned the Aeronautics and Space Engineering Board (ASEB) of the National Research Council (NRC) to investigate the adequacy of the current process by which NASA develops and verifies changes and updates to the Space Shuttle flight software. The Committee for Review of Oversight Mechanisms for Space Shuttle Flight Software Processes was convened in Jan. 1992 to accomplish the following tasks: (1) review the entire flight software development process from the initial requirements definition phase to final implementation, including object code build and final machine loading; (2) review and critique NASA's independent verification and validation process and mechanisms, including NASA's established software development and testing standards; (3) determine the acceptability and adequacy of the complete flight software development process, including the embedded validation and verification processes through comparison with (1) generally accepted industry practices, and (2) generally accepted Department of Defense and/or other government practices (comparing NASA's program with organizations and projects having similar volumes of software development, software maturity, complexity, criticality, lines of code, and national standards); (4) consider whether independent verification and validation should continue. An overview of the study, independent verification and validation of critical software, and the Space Shuttle flight software development process are addressed. Findings and recommendations are presented.

Source record↗
NASA NTRSDate not supplied

Designing Autonomy into Interfaces for Long-Duration Missions

As NASA develops technologies for long-duration crewed missions, we must understand how communication between ground control teams and astronauts differs from the current dynamic to adapt new concepts for long-duration mission operations. Today, ground control teams support astronauts with immediate availability to answer questions, resolve issues, and manage activities. In the near future, however, extended communication delays during long-duration missions will require astronauts to become more autonomous. As many of the responsibilities shift from the ground control teams to the astronauts on-board, the concept of operations must also change from how it functions today. With increased astronaut autonomy, software tools must be developed that enable efficient completion of mission tasks without increased mental workload. Designing software tools to facilitate crew autonomy requires development teams to know which data will enhance quick decision making while providing necessary context for situational awareness of systems being managed on-board. NASA's Autonomous Systems and Operations (ASO) team is presently developing a software interface tool, EXPRESS (EXpedite the PRocessing of Experiments for Space Station) 2.5 to enable a long-duration crew to schedule activities for and operate autonomous systems. This paper describes details of the integrated human factors approach that drove the design of the elements of the software tool, including self-managed scheduling, constraint-driven planning, autonomous system fault recovery, and recommended troubleshooting actions. Additionally, this paper will chronicle ASO modifications of the user interface after the team's first flight demonstration, how it was based on lessons learned during software development, as well as from crew feedback in order to develop the current version which will be demonstrated on ISS in 2021. In the upcoming ISS demonstration, the astronaut crew will be given scenarios for scheduling and operating autonomous system activities, including off-nominal scenarios and autonomous system recoveries. The demonstration of the EXPRESS 2.5 tool is a step towards improved levels of autonomy as our new journeys take us farther into space.

autonomy↗
NASA NTRS2011

Ares I-X Range Safety Simulation Verification and Analysis Independent Validation and Verification

NASA s Ares I-X vehicle launched on a suborbital test flight from the Eastern Range in Florida on October 28, 2009. To obtain approval for launch, a range safety final flight data package was generated to meet the data requirements defined in the Air Force Space Command Manual 91-710 Volume 2. The delivery included products such as a nominal trajectory, trajectory envelopes, stage disposal data and footprints, and a malfunction turn analysis. The Air Force s 45th Space Wing uses these products to ensure public and launch area safety. Due to the criticality of these data, an independent validation and verification effort was undertaken to ensure data quality and adherence to requirements. As a result, the product package was delivered with the confidence that independent organizations using separate simulation software generated data to meet the range requirements and yielded consistent results. This document captures Ares I-X final flight data package verification and validation analysis, including the methodology used to validate and verify simulation inputs, execution, and results and presents lessons learned during the process

Merry, Carl M.↗
NASA NTRS2015

Flight Software for the LADEE Mission

The Lunar Atmosphere and Dust Environment Explorer (LADEE) spacecraft was launched on September 6, 2013, and completed its mission on April 17, 2014 with a directed impact to the Lunar Surface. Its primary goals were to examine the lunar atmosphere, measure lunar dust, and to demonstrate high rate laser communications. The LADEE mission was a resounding success, achieving all mission objectives, much of which can be attributed to careful planning and preparation. This paper discusses some of the highlights from the mission, and then discusses the techniques used for developing the onboard Flight Software. A large emphasis for the Flight Software was to develop it within tight schedule and cost constraints. To accomplish this, the Flight Software team leveraged heritage software, used model based development techniques, and utilized an automated test infrastructure. This resulted in the software being delivered on time and within budget. The resulting software was able to meet all system requirements, and had very problems in flight.

LADEE↗
NASA NTRS2018

Radio-hosted Flight / Ground Interface for Operations Standardization

The interface between a spacecraft and its ground operations segment includes the flow of commands, configuration, and sequencing elements to the spacecraft, and the flow of telemetry and data products from the spacecraft. Creating and implementing a complete definition of this interface simplifies and standardizes mission operations, allowing easy sharing of operations personnel across missions. Early spacecraft featured a simple flight / ground interface (FGI) using hardware command decoding in the radio, driven by technological limitations of the time. Modern spacecraft use command and data handling (CDH) avionics on which flight software executes, which in turn controls and configures the mission, executes subsystem and instrument instructions, and implements critical fault protection actions. Deep space missions feature advanced operations software for running sequenced activities over a period of weeks, which allows them to function with only infrequent ground contact. This approach comes at the cost of increased complexity in the FGI, requiring expensive modifications to heritage flight software and ground systems. By hosting the interface in the radio instead of the CDH avionics, modern missions can approximate the FGI design simplicity of early spacecraft, with significant advantages for vendor competition, lowered costs, standardization of operations, and reduction of implementation risk.

Lock, Patricia D.↗