Search NASA⌕ Search

SEARCH · Search NASA

Results for “Autonomous Software”

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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS2016

The Soil Moisture Acttive Passive Mission: Fault Protection Performance and Lessons Learned

Fault protection as a discipline involves a collection of flight software logic and operational processes for detecting unacceptable anomalous behavior, responding prior to reaching criticality, restricting the propagation of a failure beyond a fault containment region, and recovering the vehicle back to full or degraded functionality if possible. The System Fault Protection (SFP) design for the SMAP Earth orbiter was put to the test during its 90-day vehicle commissioning activities. During this time, the SFP software autonomously protected the vehicle from multiple faults to critical hardware, and the operations team successfully returned the observatory to its science state. The SFP also performed well in the presence of anomalous behavior below true safety limits by not taking unnecessary response actions, instead allowing the operations team time to monitor the behavior. Certain aspects of the SFP design were modified during operations via both parameter updates and a full flight software update in order to better match the vehicle behavior in the flight environment. An evaluation of the SMAP SFP performance during vehicle Commissioning will be provided in this paper, as well as a set of lessons learned largely focused on visibility, SFP mutability in operations, responses to peripheral device faults, and Safe Mode recovery and design. By capturing some of the knowledge gained during SMAP Commissioning, it is intended that this paper provide guidance for making future System Fault Protection designs more robust and supportive of operations.

Clark, Jessica↗
NASA NTRS2009

Autonomously Calibrating a Quadrupole Mass Spectrometer

A computer program autonomously manages the calibration of a quadrupole ion mass spectrometer intended for use in monitoring concentrations and changes in concentrations of organic chemicals in the cabin air of the International Space Station. The instrument parameters calibrated include the voltage on a channel electron multiplier, a discriminator threshold, and an ionizer current. Calibration is achieved by analyzing the mass spectrum obtained while sweeping the parameter ranges in a heuristic procedure, developed by mass spectrometer experts, that involves detection of changes in signal trends that humans can easily recognize but cannot necessarily be straightforwardly codified in an algorithm. The procedure includes calculation of signal-to-noise ratios, signal-increase rates, and background-noise-increase rates; finding signal peaks; and identifying peak patterns. The software provides for several recovery-from-error scenarios and error-handling schemes. The software detects trace amounts of contaminant gases in the mass spectrometer and notifies associated command- and-data-handling software to schedule a cleaning. Furthermore, the software autonomously analyzes the mass spectrum to determine whether the parameters of a radio-frequency ramp waveform are set properly so that the peaks of the mass spectrum are at expected locations.

Lee, Seungwon↗
DOE OSTI2020

Radiological Recovery Logistics Tool - 20161

Argonne is building and testing a tool, the Radiological Recovery Logistics Tool (RRLT), that can be used during the response and recovery from a radiological or nuclear incident to effectively allocate appropriate commercial and public works equipment to mitigate, remove, and contain radiological contamination. The requirements for this tool - as well as development of the resulting software - is overseen by a steering committee of stakeholders from DHS's National Urban Security Technology Laboratory (NUSTL), the Federal Emergency Management Agency (FEMA), and the Environmental Protection Agency (EPA). One essential requirement is for RRLT to support the efficient and appropriate allocation of resources for a radiological response. Subsequent discussions between ANL and stakeholders have solidified the nature of this support to include identification of the types of resources to be allocated. The study reported in this paper has both factored fundamental concepts and connections out of this identification process and created a Knowledge Base detailing support goals, response scenarios, and efficacy information on dozens of equipment types. In short, RRLT will dynamically apply these findings to situational conditions surrounding contamination incidents. RRLT's Domain, the model of elements, ideas and relationships with which the tool will work, draws concepts from technical reports and stakeholder vocabularies to connect response goals and scenarios to types of equipment that offer utility towards those goals in those scenarios. RRLT's Knowledge Base will contain details on dozens of equipment types and facilitate the operator's discovery and consumption of these details most pertinent to a dynamically selected subset of goals. The core of its Domain Model is based on a report authored by this team. This report [1] contains a comprehensive list of proposed equipment to accomplish various missions or scenarios that might arise after a large-scale radiological contamination incident in an urban environment or critical infrastructure. The report divides potential response and recovery efforts into five support goals: Survey and monitoring of the contaminated area; Mitigation of received dose to first responders: Decontamination (gross and final) of buildings, vehicles, roadways, parks, and other surfaces: Waste management of solid waste generated during recovery operations: and Containment of wastewater and other waste generated during the response and recovery phases. RRLT's development is driven by use cases. A use case is an intention with which a user approaches the software. Use cases are grouped into delivery increments to schedule development, testing, and presentation to stakeholders. This model partitions the system into seven increments: User Arrival and Authentication, Search and Navigation, Equipment Recommendation, Plan Management, Content Management, and Expanded Access. Once a user 15 authenticated, RRLT will present the user with a dashboard that allows them to explore or search RRLT's content. The dashboard will also include a 'Plan' panel for collecting decisions and relevant observations about an incident at hand to facilitate development of an equipment list. RRLT will offer three general modes of access to items in the knowledge base: - Keyword search for direct discovery of items, - Navigation along predetermined paths from recovery goal towards equipment types, and - Interactive guidance towards equipment types by an autonomous software agent: the Equipment Recommendation Wizard. This presentation will detail progress in the development of the RRLT and also discuss opportunities for those interested in providing feedback on its content and functionality. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
NASA NTRS2008

Desert Research and Technology Studies (RATS) 2007 Field Campaign Objectives and Results

Desert "RATS" (Research and Technology Studies) is a combined, multi-discipline group of inter-NASA center scientists and engineers, net-working and collaborating with representatives of industry and academia, for the purpose of conducting planetary surface exploration-focused remote field exercises. These integrated testing exercises conducted under representative analog Lunar and Mars surface terrain conditions, provide NASA the capability to validate experimental prototype hardware and software systems as well as to evaluate and develop mission operational techniques in order to identify and establish technical requirements and identify potential technology "gaps" applicable for future planetary human exploration. The 2007 D-RATS field campaign test activities were initiated based on the major themes and objectives of a notional 5-year plan developed for conducting relative analog test activities in support of the engineering evaluation and assessment of various system architectural requirements, conceptual prototype support equipment and selected technologies necessary for the establishment of a lunar outpost. Specifically, the major objectives included measuring task efficiency during robot, human, and human-robot interactive tasks associated with lunar outpost site surveying and reconnaissance activities and deployment of a representative solar panel power and distribution system. In addition, technology demonstrations were conducted with a new Lithium-ion battery and autonomous software to coordinate multiple robot activities. Secondary objectives were evaluating airlock concept mockups and prototype removable space suit over-garment elements for dust mitigation, and upgrades to the prototype extravehicular activities (EVA) communication and information system. Dry run test activities, prior to testing at a designated remote field site location, were initially conducted at the Johnson Space Center (JSC) Remote Field Demonstration Test Site. This is a multi-acre external test site located at JSC and has detailed representative terrain features simulating both Lunar and Mars surface characteristics. Both the local JSC and remote field test sites have terrain conditions that are representative and characteristic of both the Moon and Mars, such as strewn rock and volcanic ash fields, craters, rolling plains, hills, gullies, slopes, and outcrops. The D-RATS 2007 field campaign, representing the completion of its tenth year of analog testing, was conducted at the large Cinder Lake volcanic ash bed area adjacent to Flagstaff, Arizona.

Kosmo, Joseph↗
NASA NTRS1991

A six-legged rover for planetary exploration

To survive the rigors and isolation of planetary exploration, an autonomous rover must be competent, reliable, and efficient. This paper presents the Ambler, a six-legged robot featuring orthogonal legs and a novel circulating gait, which has been designed for traversal of rugged, unknown environments. An autonomous software system that integrates perception, planning, and real-time control has been developed to walk the Ambler through obstacle strewn terrain. The paper describes the information and control flow of the walking system, and how the design of the mechanism and software combine to achieve competent walking, reliable behavior in the face of unexpected failures, and efficient utilization of time and power.

Simmons, Reid↗
NASA NTRS2005

A CSP-Based Agent Modeling Framework for the Cougaar Agent-Based Architecture

Cognitive Agent Architecture (Cougaar) is a Java-based architecture for large-scale distributed agent-based applications. A Cougaar agent is an autonomous software entity with behaviors that represent a real-world entity (e.g., a business process). A Cougaar-based Model Driven Architecture approach, currently under development, uses a description of system's functionality (requirements) to automatically implement the system in Cougaar. The Communicating Sequential Processes (CSP) formalism is used for the formal validation of the generated system. Two main agent components, a blackboard and a plugin, are modeled as CSP processes. A set of channels represents communications between the blackboard and individual plugins. The blackboard is represented as a CSP process that communicates with every agent in the collection. The developed CSP-based Cougaar modeling framework provides a starting point for a more complete formal verification of the automatically generated Cougaar code. Currently it is used to verify the behavior of an individual agent in terms of CSP properties and to analyze the corresponding Cougaar society.

Gracanin, Denis↗
NASA NTRS2007

Autonomous Payload Operations Onboard the International Space Station

Operating the International Space Station (ISS) involves many complex crew tended, ground operated and combined systems. Over the life of the ISS program, it has become evident that by having automated and autonomous systems on board, more can be accomplished and at the same time reduce the workload of the crew and ground operators. Engineers at the National Aeronautics and Space Administration's (NASA) Marshall Space Flight Center in Huntsville Alabama, working in collaboration with The Charles Stark Draper Laboratory have developed an autonomous software system that uses the Timeliner User Interface Language and expert logic to continuously monitor ISS payload systems, issue commands and signal ground operators as required. This paper describes the development history of the system, its concept of operation and components. The paper also discusses the testing process as well as the facilities used to develop the system. The paper concludes with a description of future enhancement plans for use on the ISS as well as potential applications to Lunar and Mars exploration systems.

Stetson, Howard K.↗
NASA NTRS2005

The Mars Exploration Rover Instrument Positioning System

During Mars Exploration Rover (MER) surface operations, the scientific data gathered by the in situ instrument suite has been invaluable with respect to the discovery of a significant water history at Meridiani Planum and the hint of water processes at work in Gusev Crater. Specifically, the ability to perform precision manipulation from a mobile platform (i.e., mobile manipulation) has been a critical part of the successful operation of Spirit and Opportunity rovers. As such, this paper describes the MER Instrument Positioning System that allows the in situ instruments to operate and collect their important science data using a robust, dexterous robotic arm combined with visual target selection and autonomous software functions.

in situ instruments↗
NASA NTRS2007

Feasibility of Turing-Style Tests for Autonomous Aerial Vehicle "Intelligence"

A new approach is suggested to define and evaluate key metrics as to autonomous aerial vehicle performance. This approach entails the conceptual definition of a "Turing Test" for UAVs. Such a "UAV Turing test" would be conducted by means of mission simulations and/or tailored flight demonstrations of vehicles under the guidance of their autonomous system software. These autonomous vehicle mission simulations and flight demonstrations would also have to be benchmarked against missions "flown" with pilots/human-operators in the loop. In turn, scoring criteria for such testing could be based upon both quantitative mission success metrics (unique to each mission) and by turning to analog "handling quality" metrics similar to the well-known Cooper-Harper pilot ratings used for manned aircraft. Autonomous aerial vehicles would be considered to have successfully passed this "UAV Turing Test" if the aggregate mission success metrics and handling qualities for the autonomous aerial vehicle matched or exceeded the equivalent metrics for missions conducted with pilots/human-operators in the loop. Alternatively, an independent, knowledgeable observer could provide the "UAV Turing Test" ratings of whether a vehicle is autonomous or "piloted." This observer ideally would, in the more sophisticated mission simulations, also have the enhanced capability of being able to override the scripted mission scenario and instigate failure modes and change of flight profile/plans. If a majority of mission tasks are rated as "piloted" by the observer, when in reality the vehicle/simulation is fully- or semi- autonomously controlled, then the vehicle/simulation "passes" the "UAV Turing Test." In this regards, this second "UAV Turing Test" approach is more consistent with Turing s original "imitation game" proposal. The overall feasibility, and important considerations and limitations, of such an approach for judging/evaluating autonomous aerial vehicle "intelligence" will be discussed from a theoretical perspective.

Young, Larry A.↗
NASA NTRS2021

Case Studies in Verifying Spacecraft Autonomy

Spacecraft, operating with a time-to-effect faster than human command response, or with absent or delayed communication, have depended on autonomy. It is likely that this reliance will continue, and increase further in future missions. Spacecraft autonomy is used when operator intervention is not available or feasible, or when dynamic aspects of a spacecraft situation cannot be predicted in advance. This paper provides case studies of several successfully verified autonomous software systems across multiple spacecraft, flight phases (launch, transit, entry and landing, science utilization), and software classifications, and can serve as examples to future missions in methods of successfully assuring spacecraft autonomy.

Johnson, Stephen B.↗
DOE OSTI2022

Autonomous Energy Management Software System for Small Commercial Buildings in Support of Decarbonization (Abstract)

The primary goal for the project is to develop and validate an autonomous energy management software (AEMS) system that will continuously optimize small commercial building operations by minimizing energy consumption and cost, providing a solution for maximizing decarbonization benefits from electrification of buildings. The work will leverage vast experience of Pacific Northwest National Laboratory (PNNL) research and development staff who have over two decades of experience in developing and successfully transferring software technologies to the private sector. This solution will be jointly developed with Intellimation LLC who plans to use it to scale their building energy efficiency offering. The project plan will include collaboratively working with Intellimation to package a set of solutions into the AEMS system, validate and demonstrate their capability, and value proposition through field demonstrations. If the deployment of the AEMS system optimizes RTUs’ set points, schedules, setbacks and optimal start and results in energy consumption reduction of 20%, the technical potential savings is approximately 675 trillion Btus of site energy savings and 2,000 trillion Btus of source energy. It will also result in carbon reductions of approximately 2.4 MMTCO2 and contribute to the climate change mitigation plans of many cities and states across the United States. Additional cost savings and emissions reduction are possible from management of peak electricity demand. The primary outcome will be an AEMS system that can be deployed at scale on small commercial buildings to improve operating efficiency.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗
NASA NTRS2020

Software assurance of autonomous spacecraft control

The work described addresses assurance of a planning and execution software system being added to an in-orbit CubeSat to demonstrate autonomous control of that spacecraft. Our focus was on how to develop assurance of the correct operation of the added software in its operational context, our approach to which was to use an assurance case to guide and organize the information involved.

Bocchino, Robert↗
NASA NTRS2013

Autonomous Aerobraking Development Software: Phase 2 Summary

NASA has used aerobraking at Mars and Venus to reduce the fuel required to deliver a spacecraft into a desired orbit compared to an all-propulsive solution. Although aerobraking reduces the propellant, it does so at the expense of mission duration, large staff, and DSN coverage. These factors make aerobraking a significant cost element in the mission design. By moving on-board the current ground-based tasks of ephemeris determination, atmospheric density estimation, and maneuver sizing and execution, a flight project would realize significant cost savings. The NASA Engineering and Safety Center (NESC) sponsored Phase 1 and 2 of the Autonomous Aerobraking Development Software (AADS) study, which demonstrated the initial feasibility of moving these current ground-based functions to the spacecraft. This paper highlights key state-of-the-art advancements made in the Phase 2 effort to verify that the AADS algorithms are accurate, robust and ready to be considered for application on future missions that utilize aerobraking. The advancements discussed herein include both model updates and simulation and benchmark testing. Rigorous testing using observed flight atmospheres, operational environments and statistical analysis characterized the AADS operability in a perturbed environment.

Cianciolo, Alicia D.↗
NASA NTRS1997

Software Architecture for Autonomous Spacecraft

The thesis objective is to design an autonomous spacecraft architecture to perform both deliberative and reactive behaviors. The Autonomous Small Planet In-Situ Reaction to Events (ASPIRE) project uses the architecture to integrate several autonomous technologies for a comet orbiter mission.

Software Spacecraft ASPIRE project↗
NASA NTRS2014

The Use of Software Agents for Autonomous Control of a DC Space Power System

In order to enable manned deep-space missions, the spacecraft must be controlled autonomously using on-board algorithms. A control architecture is proposed to enable this autonomous operation for an spacecraft electric power system and then implemented using a highly distributed network of software agents. These agents collaborate and compete with each other in order to implement each of the control functions. A subset of this control architecture is tested against a steadystate power system simulation and found to be able to solve a constrained optimization problem with competing objectives using only local information.

autonomous control↗
NASA NTRS2012

Autonomous Aerobraking Development Software: Phase One Performance Analysis at Mars, Venus, and Titan

When entering orbit about a planet or moon with an appreciable atmosphere, instead of using only the propulsion system to insert the spacecraft into its desired orbit, aerodynamic drag can be used after the initial orbit insertion to further decelerate the spacecraft. Several past NASA missions have used this aerobraking technique to reduce the fuel required to deliver a spacecraft into a desired orbit. Aerobraking was first demonstrated at Venus with Magellan in 1993 and then was used to achieve the science orbit of three Mars orbiters: Mars Global Surveyor in 1997, Mars Odyssey in 2001, and Mars Reconnaissance Orbiter in 2006. Although aerobraking itself reduces the propellant required to reach a final low period orbit, it does so at the expense of additional mission time to accommodate the aerobraking operations phase (typically 3-6 months), a large mission operations staff, and significant Deep Space Network (DSN) coverage. By automating ground based tasks and analyses associated with aerobraking and moving these onboard the spacecraft, a flight project could save millions of dollars in operations staffing and DSN costs (Ref. 1).

Maddock, Robert W.↗
NASA NTRSDate not supplied

The Anatomy of Software Changes and Bugs in Autonomous Operating System

Cyberphysical systems with autonomous functions are complex pieces of software, consisting of many components, some of which implement autonomous functionality and some may use AI or machine learning algorithms. Software bugs in an autonomous system are of particular concern, as they can have catastrophic consequences. However, detailed studies based on empirical data are rare and therefore these bugs are not well understood. This paper aims to contribute towards filling that gap by investigating the software changes and bugs in Autonomy Operating System (AOS) for Unmanned Aircraft Systems (UAS), which consist of 26 components containing about 103,000 lines of code and having a total of 772 bugfixes. Based on the data extracted from the code repository and semi-structured interviews with the developers of AOS, we explore the differences among autonomous software components, components developed using Model-based Software Engineering, and reuse with respect to change proneness, fault proneness, distribution of bugfixes among AOS components and files of these components, and characteristics of bugs of different AOS components. Our results show that the autonomous components were significantly more change prone (measured in number of commits and code churn) and fault prone (measured in bugfixes per KLoC) than non-autonomous components. The distribution of the locations of bugfixes was skewed, both at component and file level (i.e., a small number of components / files contained the majority of bugs). These evidence-based findings provide important insights to researchers and practitioners alike and can be used to efficiently improve the quality and reliability of autonomous systems.

Katerina Goseva-Popstojanova↗