Search NASA⌕ Search

SEARCH · Search NASA

Results for “Operating systems”

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 181 records · Page 10

Advanced Transport Operating System (ATOPS) utility library software description

The individual software processes used in the flight computers on-board the Advanced Transport Operating System (ATOPS) aircraft have many common functional elements. A library of commonly used software modules was created for general uses among the processes. The library includes modules for mathematical computations, data formatting, system database interfacing, and condition handling. The modules available in the library and their associated calling requirements are described.

Clinedinst, Winston C.↗

A Detect and Avoid System in the Context of Multiple-Unmanned Aircraft Systems Operations

NASA's Unmanned Aircraft Systems Integration into the National Airspace System (UAS in the NAS) project examines the technical barriers associated with the operation of UAS in civil airspace. For UAS, the removal of the pilot from onboard the aircraft has eliminated the ability of the ground-based pilot in command (PIC) to use out-the-window visual information to make judgements about a potential threat of a loss of well clear with another aircraft. NASA's Phase 1 research supported the development of a Detect and Avoid (DAA) system that supports the ground-based pilot's ability to detect potential traffic conflicts and determine a resolution maneuver, but existing display/alerting requirements did not account for multiple UAS control (1:N). Demands for increased scalability of UAS in the NAS operations are expected to create a need for simultaneous control of UAs, and thus, a new DAA HMI design will likely be necessary. Previous research, however, has found performance degradations as the number of vehicles under operator control has increased. The purpose of the current human-in-the-loop (HITL) simulation was to examine the viability of 1:N operations with the Phase 1 DAA alerting and guidance. Sixteen UAS pilots flew three scenarios with varying number of UAs under their control (1:1, 1:3, 1:5). In addition to their supervisory and sensor mission responsibilities, pilots were to utilize the DAA system to remain DAA well clear (DWC) during scripted conflicts of mixed severity. Measured response times, separation performance, mission task data, and subjective feedback were collected to assess how the multi-UAS control configuration impacted pilots' ability to maintain DAA well clear and perform the mission tasks. Overall, the DAA system proved surprisingly adaptive to multi-UAS control for preventing losses of DAA well clear (LoDWC). The findings suggest that, while multi-UAS operators are able to maintain safe separation (DWC) from other traffic, their ability to efficiently perform missions drastically decreases with their number of controlled vehicles. Pilot feedback indicated that, for this context, the use of automation support tools for completing and managing mission tasks would be appropriate and desired, especially for ensuring efficient use of assets. Finally, human-machine interface (HMI) design considerations for multi-UAS operations are discussed.

Monk, Kevin J.↗

A monitor for the laboratory evaluation of control integrity in digital control systems operating in harsh electromagnetic environments

This paper presents a strategy for dynamically monitoring digital controllers in the laboratory for susceptibility to electromagnetic disturbances that compromise control integrity. The integrity of digital control systems operating in harsh electromagnetic environments can be compromised by upsets caused by induced transient electrical signals. Digital system upset is a functional error mode that involves no component damage, can occur simultaneously in all channels of a redundant control computer, and is software dependent. The motivation for this work is the need to develop tools and techniques that can be used in the laboratory to validate and/or certify critical aircraft controllers operating in electromagnetically adverse environments that result from lightning, high-intensity radiated fields (HIRF), and nuclear electromagnetic pulses (NEMP). The detection strategy presented in this paper provides dynamic monitoring of a given control computer for degraded functional integrity resulting from redundancy management errors, control calculation errors, and control correctness/effectiveness errors. In particular, this paper discusses the use of Kalman filtering, data fusion, and statistical decision theory in monitoring a given digital controller for control calculation errors.

Belcastro, Celeste M.↗

Guidance system operations plan for manned cm earth orbital and lunar missions using program Colossus 3. Section 2: Data links

The data links for use with the guidance system operations plan for manned command module earth orbital and lunar missions using program Colossus 3 are presented. The subjects discussed are: (1) digital uplink to CMC, (2) command module contiguous block update, (3) CMC retrofire external data update, (4) CMC digital downlink, and (5) CMC entry update.

Hamilton, M. H.↗

Challenges Using Linux as a Real-Time Operating System

Human-in-the-loop (HITL) simulation groups at NASA and the Air Force Research Lab have been using Linux as a real-time operating system (RTOS) for over a decade. More recently, SpaceX has revealed that it is using Linux as an RTOS for its Falcon launch vehicles and Dragon capsules. As Linux makes its way from ground facilities to flight critical systems, it is necessary to recognize that the real-time capabilities in Linux are cobbled onto a kernel architecture designed for general purpose computing. The Linux kernel contain numerous design decisions that favor throughput over determinism and latency. These decisions often require workarounds in the application or customization of the kernel to restore a high probability that Linux will achieve deadlines.

Madden, Michael M.↗

Distributed operating system for NASA ground stations

NASA ground stations are characterized by ever changing support requirements, so application software is developed and modified on a continuing basis. A distributed operating system was designed to optimize the generation and maintenance of those applications. Unusual features include automatic program generation from detailed design graphs, on-line software modification in the testing phase, and the incorporation of a relational database within a real-time, distributed system.

Doyle, John F.↗

NASA's Advanced Multimission Operations System: A Case Study in Formalizing Software Architecture Evolution

All software systems of significant size and longevity eventually undergo changes to their basic architectural structure. Such changes may be prompted by evolving requirements, changing technology, or other reasons. Whatever the cause, software architecture evolution is commonplace in real world software projects. Recently, software architecture researchers have begun to study this phenomenon in depth. However, this work has suffered from problems of validation; research in this area has tended to make heavy use of toy examples and hypothetical scenarios and has not been well supported by real world examples. To help address this problem, I describe an ongoing effort at the Jet Propulsion Laboratory to re-architect the Advanced Multimission Operations System (AMMOS), which is used to operate NASA's deep-space and astrophysics missions. Based on examination of project documents and interviews with project personnel, I describe the goals and approach of this evolution effort and then present models that capture some of the key architectural changes. Finally, I demonstrate how approaches and formal methods from my previous research in architecture evolution may be applied to this evolution, while using languages and tools already in place at the Jet Propulsion Laboratory.

software architecture evolution↗

The Human-Robot Interaction Operating System

In order for humans and robots to work effectively together, they need to be able to converse about abilities, goals and achievements. Thus, we are developing an interaction infrastructure called the "Human-Robot Interaction Operating System" (HRI/OS). The HRI/OS provides a structured software framework for building human-robot teams, supports a variety of user interfaces, enables humans and robots to engage in task-oriented dialogue, and facilitates integration of robots through an extensible API.

Fong, Terrence↗

Satellite power system operations

A projection of the electrical energy demands over the next 30 to 50 years, coupled with reasonable assessments of known or developable energy sources, indicates that a shortage of electrical energy will occur about the turn of the century. Recognizing the criticality of such a shortage, the Department of Energy is currently evaluating alternative power generation concepts. One of these candidate concepts is the Satellite Power System. The power levels considered during the evaluation of the various satellite systems have ranged from 5 to 10 GW. It is apparent that, with this power level, both the satellite and the rectenna must be very large and encompass a large number of complex operational system activities. Major elements of the Satellite Power System (SPS) consist of a power satellite placed in a geosynchronous equatorial orbit, and a dedicated ground receiving station (GRS) located at a selected site within the continental United States. The nominal power output of the SPS is established at 5 gigawatts (5 million kilowatts) although, because of various system constraints or losses, it may actually produce between 4 and 5 gigawatts.

Pugh, F. L.↗

The elements of a space operations system

The Space Shuttle has completed its flight test program and is entering operational service with its fifth flight in November 1982. With the completion of Shuttle development, its entry to operational service, and delivery of additional units into field service, it is timely to initiate development of the next elements of the system. The elements of a Space Operations System are the Shuttle, a Station in low earth orbit, and upper stages for low and high energy orbit delivery. To design these elements properly will require a substantial operations analysis effort to characterize the most effective performance tradeoffs among the discrete elements. The Shuttle establishes a new context for the design and execution of operations in space. The components of the Shuttle, Space Station, and upper stages will need to share technology and components to minimize the cost and complexity of the logistics of ownership and operation.

Loftus, J. P., Jr.↗

A cost-benefit evaluation of the LANDSAT flow-on operational system

Disciplines to benefit from the LANDSAT Follow-on System include agriculture, petroleum and mineral exploration, hydrologic land use, water resources management, forestry, land use planning and monitoring, and soil management. The annual quantified benefits are in the range of 420 to 970 million (FY 1976 dollars). The operational system sized to achieve the quantified benefits involves a single orbiting satellite with a backup satellite in launch readiness. The ground system includes a basic processing system which feeds information to three user systems - one for agriculture, one for hydrologic land use, and a third for all other users. The resulting present worth benefit cost ratio is at least equal to four with a reasonable likelihood of exceeding nine. This benefit cost ratio is evaluated for an infinite time horizon at the discount rate of 10 percent.

Source record↗

Fault-tolerant software - Experiment with the sift operating system

Results are presented of an experiment conducted in the NASA Avionics Integrated Research Laboratory (AIRLAB) to investigate the implementation of fault-tolerant software techniques on fault-tolerant computer architectures, in particular the Software Implemented Fault Tolerance (SIFT) computer. The N-version programming and recovery block techniques were implemented on a portion of the SIFT operating system. The results indicate that, to effectively implement fault-tolerant software design techniques, system requirements will be impacted and suggest that retrofitting fault-tolerant software on existing designs will be inefficient and may require system modification.

Brunelle, J. E.↗

Operating systems in the air transportation environment.

Consideration of the problems facing air transport at present, and to be expected in the future. In the Northeast Corridor these problems involve community acceptance, airway and airport congestion and delays, passenger acceptance, noise reduction, and improvements in low-density short-haul economics. In the development of a superior short-haul operating system, terminal-configured vs cruise-configured vehicles are evaluated. CTOL, STOL, and VTOL aircraft of various types are discussed. In the field of noise abatement, it is shown that flight procedural techniques are capable of supplementing ?quiet engine' technology.

Cherry, G. W.↗

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↗

Space station automation and robotics study. Operator-systems interface

This is the final report of a Space Station Automation and Robotics Planning Study, which was a joint project of the Boeing Aerospace Company, Boeing Commercial Airplane Company, and Boeing Computer Services Company. The study is in support of the Advanced Technology Advisory Committee established by NASA in accordance with a mandate by the U.S. Congress. Boeing support complements that provided to the NASA Contractor study team by four aerospace contractors, the Stanford Research Institute (SRI), and the California Space Institute. This study identifies automation and robotics (A&R) technologies that can be advanced by requirements levied by the Space Station Program. The methodology used in the study is to establish functional requirements for the operator system interface (OSI), establish the technologies needed to meet these requirements, and to forecast the availability of these technologies. The OSI would perform path planning, tracking and control, object recognition, fault detection and correction, and plan modifications in connection with extravehicular (EV) robot operations.

Source record↗

Defining Well Clear Separation for Unmanned Aircraft Systems Operating with Noncooperative Aircraft

Detect-and-Avoid (DAA) systems are essential to the safe operations of Unmanned Aircraft Systems, and have the objectives of mitigating collisions with and remaining Well Clear of manned aircraft. This paper analyzes four candidate DAA Well Clear definitions for non-cooperative aircraft using mitigated performance metrics of DAA systems. These DAA Well Clear definitions were proposed in previous work based on their unmitigated collision risk and maneuver initiation range. In this work they are evaluated using safety and operational suitability metrics computed from a large number of representative encounters. Results suggest that although the four candidate DAA Well Clear definitions provide comparable safety, the alerting characteristics give preference for the DAA Well Clear definition without a temporal parameter.

Well Clear↗

Core Community Specifications for Electron Microprobe Operating Systems: Software, Quality Control, and Data Management Issues

Modem electron microprobe systems have become increasingly sophisticated. These systems utilize either UNIX or PC computer systems for measurement, automation, and data reduction. These systems have undergone major improvements in processing, storage, display, and communications, due to increased capabilities of hardware and software. Instrument specifications are typically utilized at the time of purchase and concentrate on hardware performance. The microanalysis community includes analysts, researchers, software developers, and manufacturers, who could benefit from exchange of ideas and the ultimate development of core community specifications (CCS) for hardware and software components of microprobe instrumentation and operating systems.

Fournelle, John↗