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 415 records · Page 23
All sourcesNASA NTRSDOE OSTI
NASA NTRS2018

Cybersecurity Information Technology

As technology and security measures improve, hackers keep looking for new techniques and vulnerabilities that allow them to gain access to sensitive data. This includes but is not limited to: user accounts, personal information, databases, operating systems, developmental and testing systems, and operational systems. A hacker is an individual that uses technology such as computers, tablets, and phones for unauthorized access to data. As technology becomes more robust at preventing known attacks, new vulnerabilities always exists. These vulnerabilities usually go unnoticed by developers and could potentially be exploited by an attacker. To prevent hackers from stealing sensitive and potentially harmful information, we must protect our systems and data against these criminals by developing new methods to mitigate the damage caused by these vulnerabilities and prevent them from occurring in the first place. An excellent way to discover how hackers compromise systems is by identifying and analyzing existing vulnerabilities and patching them. The National Aeronautics and Space Administration (NASA) is one of the many federal agencies that operates under a constant threat by hackers. NASA puts a tremendous amount of effort to maintain and improve their security measures, protect critical systems, and secure sensitive information from attackers who would attempt to use it against our nation's interests.

Hackers↗
NASA NTRS1988

A multiprocessor airborne lidar data system

A new multiprocessor data acquisition system was developed for the existing Airborne Oceanographic Lidar (AOL). This implementation simultaneously utilizes five single board 68010 microcomputers, the UNIX system V operating system, and the real time executive VRTX. The original data acquisition system was implemented on a Hewlett Packard HP 21-MX 16 bit minicomputer using a multi-tasking real time operating system and a mixture of assembly and FORTRAN languages. The present collection of data sources produce data at widely varied rates and require varied amounts of burdensome real time processing and formatting. It was decided to replace the aging HP 21-MX minicomputer with a multiprocessor system. A new and flexible recording format was devised and implemented to accommodate the constantly changing sensor configuration. A central feature of this data system is the minimization of non-remote sensing bus traffic. Therefore, it is highly desirable that each micro be capable of functioning as much as possible on-card or via private peripherals. The bus is used primarily for the transfer of remote sensing data to or from the buffer queue.

Wright, C. W.↗
NASA NTRS1987

High performance architecture for robot control

Practical aspects of the design and implementation of a modular, high performance, parallel computer control system for telerobots are discussed. Topics of consideration include system architecture, operator interface, and control execution. In a laboratory environment, a telerobotics test control configuration is used to obtain measurements on communications and control loop timing for use in an effective full scale operational system design. The feasibility of the selected architectural approach has been successfully demonstrated. The modularity of the software and hardware enables ease of transport for use in the operational system. The distributed partioning of the control algorithms and the performance measurements acquired during control system implementation are discussed.

Byler, E.↗
NASA NTRS2006

Mission Control Technologies: A New Way of Designing and Evolving Mission Systems

Current mission operations systems are built as a collection of monolithic software applications. Each application serves the needs of a specific user base associated with a discipline or functional role. Built to accomplish specific tasks, each application embodies specialized functional knowledge and has its own data storage, data models, programmatic interfaces, user interfaces, and customized business logic. In effect, each application creates its own walled-off environment. While individual applications are sometimes reused across multiple missions, it is expensive and time consuming to maintain these systems, and both costly and risky to upgrade them in the light of new requirements or modify them for new purposes. It is even more expensive to achieve new integrated activities across a set of monolithic applications. These problems impact the lifecycle cost (especially design, development, testing, training, maintenance, and integration) of each new mission operations system. They also inhibit system innovation and evolution. This in turn hinders NASA's ability to adopt new operations paradigms, including increasingly automated space systems, such as autonomous rovers, autonomous onboard crew systems, and integrated control of human and robotic missions. Hence, in order to achieve NASA's vision affordably and reliably, we need to consider and mature new ways to build mission control systems that overcome the problems inherent in systems of monolithic applications. The keys to the solution are modularity and interoperability. Modularity will increase extensibility (evolution), reusability, and maintainability. Interoperability will enable composition of larger systems out of smaller parts, and enable the construction of new integrated activities that tie together, at a deep level, the capabilities of many of the components. Modularity and interoperability together contribute to flexibility. The Mission Control Technologies (MCT) Project, a collaboration of multiple NASA Centers, led by NASA Ames Research Center, is building a framework to enable software to be assembled from flexible collections of components and services.

Trimble, Jay↗
NASA NTRS1981

Voyager at Saturn

The spacecraft design and operations and mission results of the Voyager Project are reviewed with particular emphasis on the results of the Saturn encounters. The mission was undertaken by two spacecraft: Voyager 2, launched first on August 20, 1977 on a lower energy trajectory to Jupiter, Saturn, Uranus and Neptune; and Voyager 1, launched on September 5, 1977 on a higher energy trajectory to closer flybys of Jupiter and Saturn. The Voyager spacecraft make use of earlier Mariner and Viking Orbiter design concepts, with additional capabilities for solar independent power, long-range communications and autonomy as well as equipment for the 11 science investigations. The Voyager operations system consists of a ground data system, missions operations system, and support by the Mission Control and Computer Center and Deep Space Network. Among the results of the Jupiter encounter are data concerning the magnetospheric structure and atmospheric dynamics of the planet and the surface features of the Galilean satellites. The encounters with Saturn produced scientific data concerning wind speeds, auroral emissions, and radio emissions from the planet, the fine structure of the previously known and newly discovered rings, the surface features of the satellites and the atmospheric composition and conditions of Titan. Voyager 1 is presently making field and particle measurements on its flight into interstellar space, while Voyager 2 is headed for an encounter with Uranus in January 1986 and Neptune in August 1989.

Heacock, R. L.↗
NASA NTRS1977

On the transfer of remote sensing technology to an operational data system

Data processing techniques for the transfer of remote sensing technology to an operational data system are evaluated. The study is aimed at developing a scheme for the improvement of the quantifying cost/performance ratio, noting the timeliness of the results, the ease of system development, system operating costs, and accuracy. The method is applicable to the Production Area and Yield Estimation System (PAYES) and the Large Area Crop Inventory Experiment (LACIE).

Tarbet, J. D.↗
NASA NTRS1986

Fundamentals and advances in the development of remote welding fabrication systems

Operational and man-machine issues for welding underwater, in outer space, and at other remote sites are investigated, and recent process developments are described. Probable remote welding missions are classified, and the essential characteristics of fundamental remote welding tasks are analyzed. Various possible operational modes for remote welding fabrication are identified, and appropriate roles for humans and machines are suggested. Human operator performance in remote welding fabrication tasks is discussed, and recent advances in the development of remote welding systems are described, including packaged welding systems, stud welding systems, remotely operated welding systems, and vision-aided remote robotic welding and autonomous welding systems.

Agapakis, J. E.↗
NASA NTRS1993

Operator assistant systems - An experimental approach using a telerobotics application

This article presents a knowledge-based system methodology for developing operator assistant (OA) systems in dynamic and interactive environments. This is a problem both of training and design, which is the subject of this article. Design includes both design of the system to be controlled and design of procedures for operating this system. A specific knowledge representation is proposed for representing the corresponding system and operational knowledge. This representation is based on the situation recognition and analytical reasoning paradigm. It tries to make explicit common factors involved in both human and machine intelligence, including perception and reasoning. An OA system based on this representation has been developed for space telerobotics. Simulations have been carried out with astronauts and the resulting protocols have been analyzed. Results show the relevance of the approach and have been used for improving the knowledge representation and the OA architecture.

Boy, Guy A.↗
NASA NTRS1968

Operational integrator

System operates in the nonreturn-to-zero mode, maintaining the increased bit density capability of this mode but with much higher noise immunity than conventional schemes offer. This integrator performs a mathematical integrating function on inputs from 100 Hz through 100 MHz.

Lutz, E. B.↗
NASA NTRS1988

Interactive orbital proximity operations planning system

An interactive graphical proximity operations planning system was developed, which allows on-site design of efficient, complex, multiburn maneuvers in a dynamic multispacecraft environment. Maneuvering takes place in and out of the orbital plane. The difficulty in planning such missions results from the unusual and counterintuitive character of orbital dynamics and complex time-varying operational constraints. This difficulty is greatly overcome by visualizing the relative trajectories and the relevant constraints in an easily interpretable graphical format, which provides the operator with immediate feedback on design actions. The display shows a perspective bird's-eye view of a Space Station and co-orbiting spacecraft on the background of the Station's orbital plane. The operator has control over the two modes of operation: a viewing system mode, which enables the exporation of the spatial situation about the Space Station and thus the ability to choose and zoom in on areas of interest; and a trajectory design mode, which allows the interactive editing of a series of way points and maneuvering burns to obtain a trajectory that complies with all operational constraints. A first version of this display was completed. An experimental program is planned in which operators will carry out a series of design missions which vary in complexity and constraints.

Grunwald, Arthur J.↗
NASA NTRS1989

Interactive orbital proximity operations planning system

An interactive, graphical proximity operations planning system was developed which allows on-site design of efficient, complex, multiburn maneuvers in the dynamic multispacecraft environment about the space station. Maneuvering takes place in, as well as out of, the orbital plane. The difficulty in planning such missions results from the unusual and counterintuitive character of relative orbital motion trajectories and complex operational constraints, which are both time varying and highly dependent on the mission scenario. This difficulty is greatly overcome by visualizing the relative trajectories and the relative constraints in an easily interpretable, graphical format, which provides the operator with immediate feedback on design actions. The display shows a perspective bird's-eye view of the space station and co-orbiting spacecraft on the background of the station's orbital plane. The operator has control over two modes of operation: (1) a viewing system mode, which enables him or her to explore the spatial situation about the space station and thus choose and frame in on areas of interest; and (2) a trajectory design mode, which allows the interactive editing of a series of way-points and maneuvering burns to obtain a trajectory which complies with all operational constraints. Through a graphical interactive process, the operator will continue to modify the trajectory design until all operational constraints are met. The effectiveness of this display format in complex trajectory design is presently being evaluated in an ongoing experimental program.

Grunwald, Arthur J.↗
NASA NTRS1990

Interactive orbital proximity operations planning system

An interactive graphical planning system for on-site planning of proximity operations in the congested multispacecraft environment about the space station is presented. The system shows the astronaut a bird's eye perspective of the space station, the orbital plane, and the co-orbiting spacecraft. The system operates in two operational modes: (1) a viewpoint mode, in which the astronaut is able to move the viewpoint around in the orbital plane to range in on areas of interest; and (2) a trajectory design mode, in which the trajectory is planned. Trajectory design involves the composition of a set of waypoints which result in a fuel-optimal trajectory which satisfies all operational constraints, such as departure and arrival constraints, plume impingement constraints, and structural constraints. The main purpose of the system is to present the trajectory and the constraints in an easily interpretable graphical format. Through a graphical interactive process, the trajectory waypoints are edited until all operational constraints are satisfied. A series of experiments was conducted to evaluate the system. Eight airline pilots with no prior background in orbital mechanics participated in the experiments. Subject training included a stand-alone training session of about 6 hours duration, in which the subjects became familiar with orbital mechanics concepts and performed a series of exercises to familiarize themselves with the control and display features of the system. They then carried out a series of production runs in which 90 different trajectory design situations were randomly addressed. The purpose of these experiments was to investigate how the planning time, planning efforts, and fuel expenditures were affected by the planning difficulty. Some results of these experiments are presented.

Grunwald, Arthur J.↗
NASA NTRS1992

A distributed telerobotics system for space operations

Robotic systems for space operations will require a combination of teleoperation, closely supervised autonomy, and loosely supervised autonomy. They may involve multiple robots, multiple controlling sites, and long communication delays. We have constructed a distributed telerobotics system as a framework for studying these problems. Our system is based on a modular interconnection scheme which allows the components of either manual or autonomous control systems to communicate and share information. It uses a wide area network to connect robots and operators at several different sites. This presentation will describe the structure of our system, the components used in our configurations, and results of some of our teleoperation experiments.

Wise, James D.↗
NASA NTRS2013

Model-based Systems Engineering: Creation and Implementation of Model Validation Rules for MOS 2.0

Model-based Systems Engineering (MBSE) is an emerging modeling application that is used to enhance the system development process. MBSE allows for the centralization of project and system information that would otherwise be stored in extraneous locations, yielding better communication, expedited document generation and increased knowledge capture. Based on MBSE concepts and the employment of the Systems Modeling Language (SysML), extremely large and complex systems can be modeled from conceptual design through all system lifecycles. The Operations Revitalization Initiative (OpsRev) seeks to leverage MBSE to modernize the aging Advanced Multi-Mission Operations Systems (AMMOS) into the Mission Operations System 2.0 (MOS 2.0). The MOS 2.0 will be delivered in a series of conceptual and design models and documents built using the modeling tool MagicDraw. To ensure model completeness and cohesiveness, it is imperative that the MOS 2.0 models adhere to the specifications, patterns and profiles of the Mission Service Architecture Framework, thus leading to the use of validation rules. This paper outlines the process by which validation rules are identified, designed, implemented and tested. Ultimately, these rules provide the ability to maintain model correctness and synchronization in a simple, quick and effective manner, thus allowing the continuation of project and system progress.

Model-based Systems Engineering (MBSE)↗
NASA NTRS2018

From Formal Requirements to Highly Assured Software for Unmanned Aircraft Systems

Operational requirements of safety-critical systems are often written in restricted specification logics. These restricted logics are amenable to automated analysis techniques such as model-checking, but are not rich enough to express complex requirements of unmanned systems. This short paper advocates for the use of expressive logics, such as higher-order logic, to specify the complex operational requirements and safety properties of unmanned systems. These rich logics are less amenable to automation and, hence, require the use of interactive theorem proving techniques. However, these logics support the formal verification of complex requirements such as those involving the physical environment. Moreover, these logics enable validation techniques that increase con dence in the correctness of numerically intensive software. These features result in highly-assured software that may be easier to certify. The feasibility of this approach is illustrated with examples drawn for NASA's unmanned aircraft systems.

Munoz, Cesar↗