Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “agile software development”

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 91 records · Page 5

Hybrid-Electric Aero-Propulsion Controls Laboratory: Overview and Capability

A hardware-in-the-loop (HIL) laboratory is developed to investigate control technologies for electrified aircraft propulsion (EAP). The laboratory emulates a propulsion system by reproducing the mechanical shaft interface to the electrical power system in hardware. The experimental electric power system includes supercapacitor energy storage and a dynamically variable electrical load. A novel method of scaling power and inertia is provided in software to accurately reproduce the transient, off-design turbomachinery performance dynamics without including actual turbomachinery. An overview of how the HIL system can accommodate a broad range of EAP architectures, including power extraction and insertion, with capability for transient energy management is described. The real-time system operates in the 100kW power class and is instrumented to emulate turbomachinery – power system interactions. The platform is an agile, flexible laboratory for low-cost, risk-reduction development and testing of propulsion control, operability, and energy management technologies.

Controls↗

Hybrid-Electric Aero-Propulsion Controls Laboratory: Overview and Capability

A hardware-in-the-loop (HIL) laboratory is developed to investigate control technologies for electrified aircraft propulsion (EAP). The laboratory emulates a propulsion system by reproducing the mechanical shaft interface to the electrical power system in hardware. The experimental electric power system includes supercapacitor energy storage and a dynamically variable electrical load. A novel method of scaling power and inertia is provided in software to accurately reproduce the transient, off-design turbomachinery performance dynamics without including actual turbomachinery. An overview of how the HIL system can accommodate a broad range of EAP architectures, including power extraction and insertion, with capability for transient energy management is described. The real-time system operates in the 100kW power class and is instrumented to emulate turbomachinery – power system interactions. The platform is an agile, flexible laboratory for low-cost, risk-reduction development and testing of propulsion control, operability, and energy management technologies.

controls↗

A multiomics mass spectrometry workflow for fast and comprehensive strain optimization (Abstract CRADA 726 )

The Agile Biofoundry (ABF) is a multi-national lab consortium funded by the DOE Bioenergy Technologies Office that has developed a biofoundry that enables the rapid deployment of bioproducts into the market. The ABF is a flexible platform that can adjust to the needs of numerous government, academic and industrial partners, thus enabling them to rapidly develop and optimize the production of a wide range of bioproducts. To enhance this capability, PNNL and Agilent Technologies are collaborating to expand and demonstrate a prototype system that processes hundreds of samples per day by liquid chromatography-mass spectrometry-based untargeted and targeted methods, and artificial intelligence software for multiomics applications, including metabolomics, lipidomics and proteomics.

Bilbao, Aivett (ORCID:0000000329858249)↗

Science operations interfaces for Mars surface exploration

The Science Activity Planner (SAP) is the science planning tool used for the Mars Exploration Rover (MER) mission. This paper begins with an overview of the software developed for MER and how it was used for science downlink analysis and activity planning.

distributed operations↗

Evaluation of Heave Disturbance Rejection and Control Response Criteria on the Handling Qualities Evaluation of Urban Air Mobility (UAM) eVTOL Quadrotors Using the Vertical Motion Simulator

The first piloted handling qualities study of an urban air mobility (UAM) vehicle leveraging the Vertical Motion Simulator (VMS) at NASA Ames Research Center was conducted in Spring 2021. The VMS provides a unique capability to reduce risk by assessing and iterating control designs. Minimal sources currently exist to provide performance and handling qualities data for large, rotor speed-controlled vehicles outside of the software environment. The study compares multiple handling qualities performance configurations for rotor speed and blade pitch-controlled variants of a six-passenger quadrotor conceptual design model developed by the NASA Revolutionary Vertical Lift Technology (RVLT) Project. Additionally, both ADS-33 and a tailored set of performance standards (notionally representing the agility required of a UAM mission) are examined under conditions with and without light turbulence. Preliminary results did show significant variation in ratings based on the set of standards utilized, controller tuning to either Level 1 or boundary Level 1/ Level 2 conditions, and presence or lack of turbulence. A custom approach and landing maneuver was also designed to bring these evaluation tasks together in a more comprehensive application.

Handling Qualities↗

Spacecraft Avionics Software Development Then and Now: Different but the Same

NASA has always been in the business of balancing new technologies and techniques to achieve human space travel objectives. NASA s historic Software Production Facility (SPF) was developed to serve complex avionics software solutions during an era dominated by mainframes, tape drives, and lower level programming languages. These systems have proven themselves resilient enough to serve the Shuttle Orbiter Avionics life cycle for decades. The SPF and its predecessor the Software Development Lab (SDL) at NASA s Johnson Space Center (JSC) hosted flight software (FSW) engineering, development, simulation, and test. It was active from the beginning of Shuttle Orbiter development in 1972 through the end of the shuttle program in the summer of 2011 almost 40 years. NASA s Kedalion engineering analysis lab is on the forefront of validating and using many contemporary avionics HW/SW development and integration techniques, which represent new paradigms to NASA s heritage culture in avionics software engineering. Kedalion has validated many of the Orion project s HW/SW engineering techniques borrowed from the adjacent commercial aircraft avionics environment, inserting new techniques and skills into the Multi-Purpose Crew Vehicle (MPCV) Orion program. Using contemporary agile techniques, COTS products, early rapid prototyping, in-house expertise and tools, and customer collaboration, NASA has adopted a cost effective paradigm that is currently serving Orion effectively. This paper will explore and contrast differences in technology employed over the years of NASA s space program, due largely to technological advances in hardware and software systems, while acknowledging that the basic software engineering and integration paradigms share many similarities.

Mangieri, Mark L.↗

Integration of the Kromek D3S Detector and Spot Robot For Secondary Inspections

Inspecting vehicles and containers for the presence of nuclear material is a challenging task for border control and security. When performed manually by inspectors, this task also has an associated risk of exposing the inspectors to unknown radiation. With the advent of agile, easy-to-program, quadruped robots like the Boston Dynamics Spot, automation of secondary inspection can improve the efficiency of the inspection process and alleviates the radiation risks to inspectors. In this project, Brookhaven National Laboratory and the University of Massachussetts at Lowell explored how to automate a simple secondary inspection mission. The Spot robot comes with its own software development kit (SDK) that allows clients/users to write custom code in the Python programming language to control the robot. Spot also has a payload computer called Spot-CORE, which runs the Ubuntu Linux operating system and allows users to integrate external sensors, such as a radiation detector, with Spot. In this study, the Kromek D3S detector has been integrated with Spot via the Spot-CORE, allowing Spot to capture gamma spectra and neutron counts for a specified acquisition period. Two custom routines, search and confirmation, have been developed and executed in this specified order. The search routine directs Spot to go around the nearest obstacle, e.g., vehicle and container, in a preset distance and step to collect gamma and neutron gross counts with the D3S detector. The radiation data and the robot location corresponding to each step are stored and fed to the confirmation routine at the end of the search. The confirmation routine then navigates Spot to the locations of the highest gamma or neutron counts to perform a long, e.g., one minute, measurement, and gives the operators the signature gamma spectra and neutron counts at the hotspots. This paper presents a detailed description of this automated system along with results of the preliminary tests in identifying the location and signature of a 137Cs radiation source in a vehicle.

98 NUCLEAR DISARMAMENT, SAFEGUARDS, AND PHYSICAL P↗

NASA Tech Briefs, November 2012

The topics include: Visual System for Browsing, Analysis, and Retrieval of Data (ViSBARD); Time-Domain Terahertz Computed Axial Tomography NDE System; Adaptive Sampling of Time Series During Remote Exploration; A Tracking Sun Photometer Without Moving Parts; Surface Temperature Data Analysis; Modular, Autonomous Command and Data Handling Software with Built-In Simulation and Test; In-Situ Wire Damage Detection System; Amplifier Module for 260-GHz Band Using Quartz Waveguide Transitions; Wideband Agile Digital Microwave Radiometer; Buckyball Nucleation of HiPco Tubes; FACT, Mega-ROSA, SOLAROSA; An Integrated, Layered-Spinel Composite Cathode for Energy Storage Applications; Engineered Multifunctional Surfaces for Fluid Handling; Polyolefin-Based Aerogels; Adjusting Permittivity by Blending Varying Ratios of SWNTs; Gravity-Assist Mechanical Simulator for Outreach; Concept for Hydrogen-Impregnated Nanofiber/Photovoltaic Cargo Stowage System; DROP: Durable Reconnaissance and Observation Platform; Developing Physiologic Models for Emergency Medical Procedures Under Microgravity; Spectroscopic Chemical Analysis Methods and Apparatus; Low Average Sidelobe Slot Array Antennas for Radiometer Applications; Motion-Corrected 3D Sonic Anemometer for Tethersondes and Other Moving Platforms; Water Treatment Systems for Long Spaceflights; Microchip Non-Aqueous Capillary Electrophoresis (MicronNACE) Method to Analyze Long-Chain Primary Amines; Low-Cost Phased Array Antenna for Sounding Rockets, Missiles, and Expendable Launch Vehicles; Mars Science Laboratory Engineering Cameras; Seismic Imager Space Telescope; Estimating Sea Surface Salinity and Wind Using Combined Passive and Active L-Band Microwave Observations; A Posteriori Study of a DNS Database Describing Super critical Binary-Species Mixing; Scalable SCPPM Decoder; QuakeSim 2.0; HURON (HUman and Robotic Optimization Network) Multi-Agent Temporal Activity Planner/Scheduler; MPST Software: MoonKommand

Source record↗

Evolution of the Scope and Capabilities of Uplink Support Software for Mars Surface Operations

In January of 2004 both of the Mars Exploration Rover spacecraft landed safely, initiating daily surface operations at the Jet Propulsion Laboratory for what was anticipated to be approximately three months of mobile exploration. The longevity of this mission, still ongoing after ten years, has provided not only a tremendous return of scientific data but also the opportunity to refine and improve the methodology by which robotic Mars surface missions are commanded. Since the landing of the Mars Science Laboratory spacecraft in August of 2012, this methodology has been successfully applied to operate a Martian rover which is both similar to, and quite different from, its predecessors. For MER and MSL, daily uplink operations can be most broadly viewed as converting the combined interests of both the science and engineering teams into a spacecraft-safe set of transmittable command files. In order to accomplish these ends a discrete set of mission-critical software tools were developed which not only allowed for conformation to established JPL standards and practices but also enabled innovative technologies specific to each mission. Although these primary programs provided the requisite capabilities for meeting the high-level goals of each distinct phase of the uplink process, there was little in the way of secondary software to support the smooth flow of data from one phase to the next. In order to address this shortcoming a suite of small software tools was developed to aid in phase transitions, as well as to automate some of the more laborious and error-prone aspects of uplink operations. This paper describes the evolution of this software suite, from its initial attempts to merely shorten the duration of the operator's shift, to its current role as an indispensable tool enforcing workflow of the uplink operations process and agilely responding to the new and unexpected challenges of missions which can, and have, lasted many years longer than originally anticipated.

CoUGAR↗

NASA ESTO Advanced Information Systems Technology (AIST)

"(Only Talk/No Publication) NASA’s Advanced Information Systems Technology (AIST) Program identifies, develops, and supports adoption of software and information systems, as well as novel computer science technologies expected to be needed by the Earth Science Division in the 5-10-year timeframe. This presentation gives an overview of the AIST Program. AIST’s previous thrusts have been New Observing Strategies (NOS) and Analytic Collaborative Frameworks (ACF). The current vision is to connect these two thrusts and integrate them into the larger concept of Earth System Digital Twins (ESDT). To implement this new vision, the AIST Program is focusing on technologies and innovative concepts with three main objectives: O1. Enable new observation measurements and new observing systems design and operations through intelligent, timely, dynamic, and coordinated distributed sensing; O2. Enable agile science investigations that fully utilize the large amount of diverse observations using advanced analytic tools, visualizations, and computing environments, and that interact seamlessly with relevant observing systems; O3. Enable the development of integrated Earth Science frameworks that mirror the Earth with state-of-the-art models (Earth system models and others), timely and relevant observations, and analytic tools. This thrust will provide technology for enabling near- and long-term science and policy decisions (“science decisions” including planning for the acquisition of new measurements; the development of new models or science analysis; the integration of Earth observations in novel ways; applications to inform choices, support decisions, and guide actions for societal benefit; etc.)."

Mathematical and Computer Sciences (General)↗

Non-Maximally Decimated Filter Banks Enable Adaptive Frequency Hopping for Unmanned Aircraft Vehicles

In the last few years, radio technologies for unmanned aircraft vehicle (UAV) have advanced very rapidly. The increasing need to fly unmanned aircraft systems (UAS) in the national airspace system (NAS) to perform missions of vital importance to national security, defense, and science has pushed ahead the design and implementation of new radio platforms. However, a lot still has to be done to improve those radios in terms of performance and capabilities. In addition, an important aspect to account for is hardware cost and the feasibility to implement these radios using commercial off-the-shelf (COTS) components. UAV radios come with numerous technical challenges and their development involves contributions at different levels of the design. Cognitive algorithms need to be developed in order to perform agile communications using appropriate frequency allocation while maintaining safe and efficient operations in the NAS and, digital reconfigurable architectures have to be designed in order to ensure a prompt response to environmental changes. Command and control (C2) communications have to be preserved during "standard" operations while crew operations have to be minimized. It is clear that UAV radios have to be software-defined systems, where size, weight and power consumption (SWaP) are critical parameters. This paper provides preliminary results of the efforts performed to design a fully digital radio architecture as part of a NASA Phase I STTR. In this paper, we will explain the basic idea and technical principles behind our dynamic/adaptive frequency hopping radio for UAVs. We will present our Simulink model of the dynamic FH radio transmitter design for UAV communications and show simulation results and FPGA system analysis.

UAV↗

Content Documents Management

The Content Documents are created and managed under the System Software group with. Launch Control System (LCS) project. The System Software product group is lead by NASA Engineering Control and Data Systems branch (NE~C3) at Kennedy Space Center. The team is working on creating Operating System Images (OSI) for different platforms (i.e. AIX, Linux, Solaris and Windows). Before the OSI can be created, the team must create a Content Document which provides the information of a workstation or server, with the list of all the software that is to be installed on it and also the set where the hardware belongs. This can be for example in the LDS, the ADS or the FR-l. The objective of this project is to create a User Interface Web application that can manage the information of the Content Documents, with all the correct validations and filters for administrator purposes. For this project we used one of the most excellent tools in agile development applications called Ruby on Rails. This tool helps pragmatic programmers develop Web applications with Rails framework and Ruby programming language. It is very amazing to see how a student can learn about OOP features with the Ruby language, manage the user interface with HTML and CSS, create associations and queries with gems, manage databases and run a server with MYSQL, run shell commands with command prompt and create Web frameworks with Rails. All of this in a real world project and in just fifteen weeks!

Muniz, R.↗

Bridging Python to Silicon: The SODA Toolchain

Systems performing scientific computing, data analysis, and machine learning tasks have a growing demand for application-specific accelerators that can provide high computational performance while meeting strict size and power requirements. However, the algorithms and applications that need to be accelerated are evolving at a rate that is incompatible with manual design processes based on hardware description languages. Agile hardware design tools based on compiler techniques can help by quickly producing an application-specific integrated circuit (ASIC) accelerator starting from a high-level algorithmic description. Here, we present the software-defined accelerator (SODA) synthesizer, a modular and open-source hardware compiler that provides automated end-to-end synthesis from high-level software frameworks to ASIC implementation, relying on multilevel representations to progressively lower and optimize the input code. Our approach does not require the application developer to write any register-transfer level code, and it is able to reach up to 364 giga floating point operations per second (GFLOPS)/W efficiency (32-bit precision) on typical convolutional neural network operators.

97 MATHEMATICS AND COMPUTING↗

Energy Northwest — Advanced Grid Interactive Load Efficiency (AGILE) : A Techno-economic Assessment

The Advanced Grid Interactive Load Efficiency project team, led by Energy Northwest, was awarded funding as part of the fourth round of the Clean Energy Fund program to investigate, co-create, and complete a preliminary design for grid-interactive efficient buildings (GEBs) for a number of schools served by Grays Harbor PUD. The project team has evaluated different combinations of systems at selected school buildings and the potential to respond to grid and customer needs, and develop a preliminary system technical design, including specifying desired GEB technology options, determining communication and electrical interface requirements, assessing control software sensor requirements, and interfacing with building management systems. PNNL led the techno-economic assessment efforts, leveraging its advanced modeling and analytical methods and tools developed for building-to-grid integration. This report documents the economic assessment for different GEB design options, encompassing an in-depth examination of use cases and value propositions, assumptions and inputs, models, methods, case studies, as well as key findings.

24 POWER TRANSMISSION AND DISTRIBUTION↗

Flight Evaluation of the Army/NASA Variable Stability Fly-by-Wire Rotorcraft Aircrew Systems Concept Airborne Laboratory (RASCAL) JUH-60A

NASA Ames Research Center and the U.S. Army Aeroflight dynamics Directorate (AFDD) have performed initial flight evaluations of the Research Flight Control System (RFCS) integrated into the Army/NASA Rotorcraft Aircrew Systems Concepts Airborne Laboratory (RASCAL) JUH-GOA. The highly modified JUH-GOA Black Hawk helicopter is a full authority, high bandwidth, variable stability, in-flight simulator designed to support development of advanced flight control, sensor, and integrated display and control technologies in a fail safe environment. Preparation for flight test required an extensive hazard analysis and ground testing to ensure proper system operation. A hardware in the loop development facility was utilized to evaluate control law stability following software changes, assess servo hardover upset conditions during manual and monitor disengagements and provide pilot familiarization of test techniques and software changes prior to flight. First engagement of the RFCS was conducted on 31 Aug 2001. RFCS transfer system operation, envelope expansion and a limited rate monitor evaluation have been completed with low bandwidth and model following control laws. The presentation will discuss the following - System overview including aircraft modifications and integrated development facilities used with the RASCAL facility. - Preliminary hazard identification and mitigation prior to flight test. - Ground testing used to qualify the RFCS transfer system and verify fault monitor operation. - Flight test results of low-bandwidth and model following control law evaluations including maneuver agility, control limitations, fault monitor reliability, and recovery from manual and monitor disengagement. - Lessons learned including test techniques using a passive three-axis sidearm controller, the value of the development facility in reducing risk and crew coordination issues related to the operation of a full authority, variable stability platform. - Future research and modifications planned for the RASCAL aircraft.

Dave Arterburn↗

Understanding and Evaluating Assurance Cases

Assurance cases are a method for providing assurance for a system by giving an argument to justify a claim about the system, based on evidence about its design, development, and tested behavior. In comparison with assurance based on guidelines or standards (which essentially specify only the evidence to be produced), the chief novelty in assurance cases is provision of an explicit argument. In principle, this can allow assurance cases to be more finely tuned to the specific circumstances of the system, and more agile than guidelines in adapting to new techniques and applications. The first part of this report (Sections 1-4) provides an introduction to assurance cases. Although this material should be accessible to all those with an interest in these topics, the examples focus on software for airborne systems, traditionally assured using the DO-178C guidelines and its predecessors. A brief survey of some existing assurance cases is provided in Section 5. The second part (Section 6) considers the criteria, methods, and tools that may be used to evaluate whether an assurance case provides sufficient confidence that a particular system or service is fit for its intended use. An assurance case cannot provide unequivocal "proof" for its claim, so much of the discussion focuses on the interpretation of such less-than-definitive arguments, and on methods to counteract confirmation bias and other fallibilities in human reasoning.

Rushby, John↗

Developing and testing capabilities for simulating cases with heterogeneous land/water surfaces in a novel atmospheric large eddy simulation code

Large eddy simulations (LES) are the primary computational tool used to simulate high Reynolds number three-dimensional turbulent flows. In the context of earth system sciences, particularly atmospheric science, LES are uniquely able to resolve the scales of atmospheric motion that are key for building process-level understanding of boundary layer turbulence, atmosphere-surface interaction, clouds, and cloud-aerosol-chemistry interaction, and are a core limited-area modeling capability. Increasing demands are being placed on LES code bases as growing high performance computing resources allow LES to address a wider range of scientific problems. In addition, LES are emerging as a source of high-quality machine learning training data. These demands necessitate an agile and extensible code base that allows the model to quickly adapt to emergent needs. However, LES have largely relied on legacy Fortran code bases that lack flexibility. A new, Python-based LES capability called Predicting INteractions of Aerosol and Clouds in Large Eddy Simulation (PINACLES) has been developed as part of the Department of Energy’s Earth System Model Development (ESMD) program area’s Enabling Aerosol-cloud interactions at Global convection-permitting scalES (EAGLES) project. PINACLES was developed from the ground up with a philosophy of maximizing scientific throughput, by attempting to optimize for both model throughput and software extensibility. The initial development of PINACLES delivered a state-of-the-art idealized LES capability solving the non-hydrostatic anelastic equations of motion with doubly periodic boundary conditions and idealized homogenous surface boundary conditions. Here we provide a final report on the outcomes of a fiscal year 2021 Seed Laboratory Directed Research Project that extended PINACLES in two key ways. First, PINACLES was coupled to a state-of-the-art land surface model enabling it to simulate spatially inhomogeneous land-atmosphere interactions that are known to control key atmospheric processes. Second, the dynamical core of PINACLES was modified to permit non-periodic boundary conditions. This model enhancement enables simulation of realistic cases with boundary conditions prescribed from atmospheric reanalysis and enables nested simulations conducted on a hierarchy of computational domains with increasing resolution. Together, these extensions to PINACLES make it a formidable modeling capability and expand its potential application to diverse components of DOE’s atmospheric science portfolio.

42 ENGINEERING↗

The Ejectable Data Recorder: A Lean, Risk-Informed Approach for Hardware Development

NASA is developing the Orion spacecraft to transport crew from the Earth to the Moon as part of the Artemis series of missions. To provide a crew escape capability from pre-launch through ascent, the Orion vehicle is equipped with a Launch Abort System (LAS), built by Lockheed Martin, which pulls the capsule away from the launch vehicle in the event of an abort scenario. The Ascent Abort 2 (AA-2) test flight occurred on July 2, 2019,and tested a production version of the LAS to ensure that it can operate as intended, and to collect a large data set from hundreds of sensors on the vehicle to support Orion flight certification. In the original AA-2 architecture, a single-string set of communications antennas on the LAS would downlink all of the in-flight test data to ground stations. However, that communications architecture was predicted to have data dropouts during abort and jettison of the LAS, and would not support data transmission at all after LAS jettison. As a result, a comprehensive trade study was completed, yielding the addition of antennas on the crew module (CM), a buffer/rebroadcast capability for key portions of the flight, and an ejectable data recorder (EDR) subsystem. This EDR subsystem would serve as a backup to the radio frequency (RF) communications system, and would be non-flight critical, providing a unique capability that enabled management to take a different approach with the hardware and software development. The Crew Module and Separation Ring were developed as “Class 1”Flight Hardware, albeit with some tailoring approaches to enable efficiencies. The Class 1 designation requires full rigor for flight hardware and software, documenting everything that happens to a piece of hardware from procurement through disposal, requiring a full spectrum of acceptance tests, and the highest rigor of quality assurance processes. At the other end of the spectrum, Class 3hardware is controlled, but not intended for flight, and leaves the level of rigor up to the project manager. This classification is often used for research and development projects. Similarly,Class-1E has been recently defined at NASA for ISS payloads and technology development projects that are not flight critical and do not need the full rigor of Class 1 to be successful. The EDR subsystem was challenged at commencement to adopt a skunkworks and agile-like approach to hardware development, allowing for a different risk posture than the rest of the AA-2 hardware. After initially pursuing Class 1 processes, the EDR subsystem design evolved to incorporating numerous commercial components, leading to re-designation as a Class-1E subsystem. The resulting EDR subsystem was fully successful in meeting all flight system requirements, and achieved 100% retrieval of flight test data. This paper will discuss the risk posture of the EDR subsystem and the subsequent tailoring that was enacted as part of its Class-1E status.

EDR↗