Results for “avoiding communication” — Page 22

NASA NTRS1997

The Taxiway Navigation and Situation Awareness (T-NASA) System

The goal of NASA's Terminal Area Productivity (TAP) Low-Visibility Landing and Surface Operations (LVLASO) subelement is to improve the efficiency of airport surface operations for commercial aircraft operating in weather conditions to Category IIIB while maintaining a high degree of safety. Currently, surface operations are one of the least technologically sophisticated components of the air transport system, being conducted in the 1990's with the same basic technology as in the 1930's. Pilots are given little or no explicit information about their current position, and routing information is limited to ATC communications and airport charts. In TAP/LVLASO, advanced technologies such as satellite navigation systems, digital data communications, advanced information presentation technology, and ground surveillance systems will be integrated into flight deck displays to enable expeditious and safe traffic movement on the airport surface. The cockpit display suite is called the T-NASA (Taxiway Navigation and Situation Awareness) System. This system has three integrated components: 1) Moving Map track-up airport surface display with own-ship, traffic and graphical route guidance 2) Scene-Linked Symbology - route/taxi information virtually projected via a Head-up Display (HUD) onto the forward scene; and, 3) 3-D Audio Ground Collision Avoidance and Navigation system - spatially-localized auditory traffic and navigation alerts. In the current paper, the design philosophy of the T-NASA system will be presented, and the T-NASA system display components described.

Foyle, David C.↗

NASA NTRS1990

Evaluation of off-road terrain with static stereo and monoscopic displays

The National Aeronautics and Space Administration is currently funding research into the design of a Mars rover vehicle. This unmanned rover will be used to explore a number of scientific and geologic sites on the Martian surface. Since the rover can not be driven from Earth in real-time, due to lengthy communication time delays, a locomotion strategy that optimizes vehicle range and minimizes potential risk must be developed. In order to assess the degree of on-board artificial intelligence (AI) required for a rover to carry out its' mission, researchers conducted an experiment to define a no AI baseline. In the experiment 24 subjects, divided into stereo and monoscopic groups, were shown video snapshots of four terrain scenes. The subjects' task was to choose a suitable path for the vehicle through each of the four scenes. Paths were scored based on distance travelled and hazard avoidance. Study results are presented with respect to: (1) risk versus range; (2) stereo versus monocular video; (3) vehicle camera height; and (4) camera field-of-view.

Yorchak, John P.↗

NASA NTRS2012

UAS Integration Into the NAS: An Examination of Baseline Compliance in the Current Airspace System

As a result of the FAA Modernization and Reform Act of 2012, Unmanned Aerial Systems (UAS) are expected to be integrated into the National Airspace System (NAS) by 2015. Several human factors challenges need to be addressed before UAS can safely and routinely fly in the NAS with manned aircraft. Perhaps the most significant challenge is for the UAS to be non-disruptive to the air traffic management system. Another human factors challenge is how to provide UAS pilots with intuitive traffic information in order to support situation awareness (SA) of their airspace environment as well as a see-and-avoid capability comparable to manned aircraft so that a UAS pilot could safely maneuver the aircraft to maintain separation and collision avoidance if necessary. A simulation experiment was conducted to examine baseline compliance of UAS operations in the current airspace system. Researchers also examined the effects of introducing a Cockpit Situation Display (CSD) into a UAS Ground Control Station (GCS) on UAS pilot performance, workload and situation awareness while flying in a positively controlled sector. Pilots were tasked with conducting a highway patrol police mission with a Medium Altitude Long Endurance (MALE) UAS in L.A. Center airspace with two mission objectives: 1) to reroute the UAS when issued new instructions from their commander, and 2) to communicate with Air Traffic Control (ATC) to negotiate flight plan changes and respond to vectoring and altitude change instructions. Objective aircraft separation data, workload ratings, SA data, and subjective ratings regarding UAS operations in the NAS were collected. Results indicate that UAS pilots were able to comply appropriately with ATC instructions. In addition, the introduction of the CSD improved pilot SA and reduced workload associated with UAS and ATC interactions.

Fern, Lisa↗

NASA NTRS2003

Collective Intelligence

Many systems of self-interested agents have an associated performance criterion that rates the dynamic behavior of the overall system. This chapter presents an introduction to the science of such systems. Formally, collectives are defined as any system having the following two characteristics: First, the system must contain one or more agents each of which we view as trying to maximize an associated private utility; second, the system must have an associated world utility function that rates the possible behaviors of that overall system. In practice, collectives are often very large, distributed, and support little, if any, centralized communication and control, although those characteristics are not part of their formal definition. A naturally occurring example of a collective is a human economy. One can identify the agents and their private utilities as the human individuals in the economy and the associated personal rewards they are each trying to maximize. One could then identify the world utility as the time average of the gross domestic product. ("World utility" per se is not a construction internal to a human economy, but rather something defined from the outside.) To achieve high world utility it is necessary to avoid having the agents work at cross-purposes lest phenomena like liquidity traps or the Tragedy of the Commons (TOC) occur, in which agents' individually pursuing their private utilities lowers world utility. The obvious way to avoid such phenomena is by modifying the agents utility functions to be "aligned" with the world utility. This can be done via punitive legislation. A real-world example of an attempt to do this was the creation of antitrust regulations designed to prevent monopolistic practices.

Wolpert, David H.↗

NASA NTRS2023

Lunar Dust Mitigation: A Guide and Reference: First Edition (2021)

On the surface of the Moon, lunar dust specifically presents unique challenges to operations long-term due to regolith particles’ ubiquitous presence in the lunar environment, potential to electrostatically charge and possible chemical reactivity. Whether to avoid exposure, try to remove or simply to tolerate lunar dust infiltrating a system becomes a complex question involving length of required service life, dust effects and critical risks, mass and complexity trades for the entire system. This publication provides a snapshot of advice from topical experts for specific areas of concern to systems targeted for deployment on the lunar surface. Following introductory overview commentary, dust mitigation approaches appropriate to the lunar surface are first addressed for typically static structures such as optical surfaces, radiators, and other thermal control surfaces, followed by regolith exposure concerns for communications equipment and non-optical sensors. The broad topic of mechanisms and mechanical assemblies is broken down to address relevant component level concerns, such as for bearings and for seals. “Soft goods” components of space suits (fabric) specific concerns are discussed, followed finally by brief coverage of human health issues and concerns, though the emphasis of this publication remains with components directly exposed to the harsh lunar surface environment. A description of some lunar surface hazard details, in particular characteristics of lunar surface dust, follows in Appendix A, and more detailed explanations of quantification issues for particulates are in Appendix B. The simple inertial removal of particles from a surface is discussed in Appendix C, followed by a summary of terrestrial best practices for dust mitigation recommended within select industries in Appendix D. The aggregated bibliography of references, while extensive and very useful, should not be construed to be exhaustive and can serve as a constructive start.

dust↗

NASA NTRS2001

Neural network based automatic limit prediction and avoidance system and method

A method for performance envelope boundary cueing for a vehicle control system comprises the steps of formulating a prediction system for a neural network and training the neural network to predict values of limited parameters as a function of current control positions and current vehicle operating conditions. The method further comprises the steps of applying the neural network to the control system of the vehicle, where the vehicle has capability for measuring current control positions and current vehicle operating conditions. The neural network generates a map of current control positions and vehicle operating conditions versus the limited parameters in a pre-determined vehicle operating condition. The method estimates critical control deflections from the current control positions required to drive the vehicle to a performance envelope boundary. Finally, the method comprises the steps of communicating the critical control deflection to the vehicle control system; and driving the vehicle control system to provide a tactile cue to an operator of the vehicle as the control positions approach the critical control deflections.

Calise, Anthony J.↗

DOE OSTI2020

UPC++ v1.0 Specification, Revision 2020.10.0

UPC++ is a C++11 library providing classes and functions that support Partitioned Global Address Space (PGAS) programming. The key communication facilities in UPC++ are one-sided Remote Memory Access (RMA) and Remote Procedure Call (RPC). All communication operations are syntactically explicit and default to non-blocking; asynchrony is managed through the use of futures, promises and continuation callbacks, enabling the programmer to construct a graph of operations to execute asynchronously as high-latency dependencies are satisfied. A global pointer abstraction provides system-wide addressability of shared memory, including host and accelerator memories. The parallelism model is primarily process-based, but the interface is thread-safe and designed to allow efficient and expressive use in multi-threaded applications. The interface is designed for extreme scalability throughout, and deliberately avoids design features that could inhibit scalability.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2021

UPC++ v1.0 Specification, Revision 2021.9.0

UPC++ is a C++ library providing classes and functions that support Partitioned Global Address Space (PGAS) programming. The key communication facilities in UPC++ are one-sided Remote Memory Access (RMA) and Remote Procedure Call (RPC). All communication operations are syntactically explicit and default to non-blocking; asynchrony is managed through the use of futures, promises and continuation callbacks, enabling the programmer to construct a graph of operations to execute asynchronously as high-latency dependencies are satisfied. A global pointer abstraction provides system-wide addressability of shared memory, including host and accelerator memories. The parallelism model is primarily process-based, but the interface is thread-safe and designed to allow efficient and expressive use in multi-threaded applications. The interface is designed for extreme scalability throughout, and deliberately avoids design features that could inhibit scalability.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

DOE OSTI2023

UPC++ v1.0 Specification (Rev. 2023.9.0)

UPC++ is a C++ library providing classes and functions that support Partitioned Global Address Space (PGAS) programming. The key communication facilities in UPC++ are one-sided Remote Memory Access (RMA) and Remote Procedure Call (RPC). All communication operations are syntactically explicit and default to non-blocking; asynchrony is managed through the use of futures, promises and continuation callbacks, enabling the programmer to construct a graph of operations to execute asynchronously as high-latency dependencies are satisfied. A global pointer abstraction provides system-wide addressability of shared memory, including host and accelerator memories. The parallelism model is primarily process-based, but the interface is thread-safe and designed to allow efficient and expressive use in multi-threaded applications. The interface is designed for extreme scalability throughout, and deliberately avoids design features that could inhibit scalability.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2022

UPC++ v1.0 Specification (Revision 2022.3.0)

UPC++ is a C++ library providing classes and functions that support Partitioned Global Address Space (PGAS) programming. The key communication facilities in UPC++ are one-sided Remote Memory Access (RMA) and Remote Procedure Call (RPC). All communication operations are syntactically explicit and default to non-blocking; asynchrony is managed through the use of futures, promises and continuation callbacks, enabling the programmer to construct a graph of operations to execute asynchronously as high-latency dependencies are satisfied. A global pointer abstraction provides system-wide addressability of shared memory, including host and accelerator memories. The parallelism model is primarily process-based, but the interface is thread-safe and designed to allow efficient and expressive use in multi-threaded applications. The interface is designed for extreme scalability throughout, and deliberately avoids design features that could inhibit scalability.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2022

UPC++ v1.0 Specification, Revision 2023.3.0

UPC++ is a C++ library providing classes and functions that support Partitioned Global Address Space (PGAS) programming. The key communication facilities in UPC++ are one-sided Remote Memory Access (RMA) and Remote Procedure Call (RPC). All communication operations are syntactically explicit and default to non-blocking; asynchrony is managed through the use of futures, promises and continuation callbacks, enabling the programmer to construct a graph of operations to execute asynchronously as high-latency dependencies are satisfied. A global pointer abstraction provides system-wide addressability of shared memory, including host and accelerator memories. The parallelism model is primarily process-based, but the interface is thread-safe and designed to allow efficient and expressive use in multi-threaded applications. The interface is designed for extreme scalability throughout, and deliberately avoids design features that could inhibit scalability.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2021

UPC++ v1.0 Specification (Revision 2021.3.0)

UPC++ is a C++11 library providing classes and functions that support Partitioned Global Address Space (PGAS) programming. The key communication facilities in UPC++ are one-sided Remote Memory Access (RMA) and Remote Procedure Call (RPC). All communication operations are syntactically explicit and default to non-blocking; asynchrony is managed through the use of futures, promises and continuation callbacks, enabling the programmer to construct a graph of operations to execute asynchronously as high-latency dependencies are satisfied. A global pointer abstraction provides system-wide addressability of shared memory, including host and accelerator memories. The parallelism model is primarily process-based, but the interface is thread-safe and designed to allow efficient and expressive use in multi-threaded applications. The interface is designed for extreme scalability throughout, and deliberately avoids design features that could inhibit scalability.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2022

UPC++ v1.0 Specification, Revision 2022.9.0

UPC++ is a C++ library providing classes and functions that support Partitioned Global Address Space (PGAS) programming. The key communication facilities in UPC++ are one-sided Remote Memory Access (RMA) and Remote Procedure Call (RPC). All communication operations are syntactically explicit and default to non-blocking; asynchrony is managed through the use of futures, promises and continuation callbacks, enabling the programmer to construct a graph of operations to execute asynchronously as high-latency dependencies are satisfied. A global pointer abstraction provides system-wide addressability of shared memory, including host and accelerator memories. The parallelism model is primarily process-based, but the interface is thread-safe and designed to allow efficient and expressive use in multi-threaded applications. The interface is designed for extreme scalability throughout, and deliberately avoids design features that could inhibit scalability.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2020

UPC++ v1.0 Specification, Revision 2020.3.0

UPC++ is a C++11 library providing classes and functions that support Partitioned Global Address Space (PGAS) programming. The key communication facilities in UPC++ are one-sided Remote Memory Access (RMA) and Remote Procedure Call (RPC). All communication operations are syntactically explicit and default to non-blocking; asynchrony is managed through the use of futures, promises and continuation callbacks, enabling the programmer to construct a graph of operations to execute asynchronously as high-latency dependencies are satisfied. A global pointer abstraction provides system-wide addressability of shared memory, including host and accelerator memories. The parallelism model is primarily process-based, but the interface is thread-safe and designed to allow efficient and expressive use in multi-threaded applications. The interface is designed for extreme scalability throughout, and deliberately avoids design features that could inhibit scalability.

97 MATHEMATICS AND COMPUTING↗

NASA NTRS1995

Fast interrupt platform for extended DOS

Extended DOS offers the unique combination of a simple operating system which allows direct assess to the interrupt tables, 32 bit protected mode access to a 4096 MByte address space, and the use of industry standard C compilers. The drawback is that fast interrupt handling requires both 32 bit and 16 bit versions of each real-time process interrupt handler to avoid mode switches on the interrupts. A set of tools has been developed which automates the process of transforming the output of a standard 32 bit C compiler to 16 bit interrupt code which directly handles the real mode interrupts. The entire process compiles one set of source code via a make file, which boosts productivity by making the management of the compile-link cycle very simple. The software components are in the form of classes written mostly in C. A foreground process written as a conventional application which can use the standard C libraries can communicate with the background real-time classes via a message passing mechanism. The platform thus enables the integration of high performance real-time processing into a conventional application framework.

Duryea, T. W.↗

NASA NTRS1995

STS-63 Space Shuttle report

The STS-63 Space Shuttle Program Mission Report summarizes the Payload activities and provides detailed data on the Orbiter, External Tank (ET), Solid Rocket Booster (SRB), Reusable Solid Rocket Motor (RSRM), and the Space Shuttle Main Engine (SSME) systems performance during this sixty-seventh flight of the Space Shuttle Program, the forty-second since the return to flight, and twentieth flight of the Orbiter vehicle Discovery (OV-103). In addition to the OV-103 Orbiter vehicle, the flight vehicle consisted of an ET that was designated ET-68; three SSME's that were designated 2035, 2109, and 2029 in positions 1, 2, and 3, respectively; and two SRB's that were designated BI-070. The RSRM's that were an integral part of the SRB's were designated 360Q042A for the left SRB and 360L042B for the right SRB. The STS-63 mission was planned as an 8-day duration mission with two contingency days available for weather avoidance or Orbiter contingency operations. The primary objectives of the STS-63 mission were to perform the Mir rendezvous operations, accomplish the Spacehab-3 experiments, and deploy and retrieve the Shuttle Pointed Autonomous Research Tool for Astronomy-204 (SPARTAN-204) payload. The secondary objectives were to perform the Cryogenic Systems Experiment (CSE)/Shuttle Glo-2 Experiment (GLO-2) Payload (CGP)/Orbital Debris Radar Calibration Spheres (ODERACS-2) (CGP/ODERACS-2) payload objectives, the Solid Surface Combustion Experiment (SSCE), and the Air Force Maui Optical Site Calibration Tests (AMOS). The objectives of the Mir rendezvous/flyby were to verify flight techniques, communication and navigation-aid sensor interfaces, and engineering analyses associated with Shuttle/Mir proximity operations in preparation for the STS-71 docking mission.

Fricke, Robert W., Jr.↗

NASA NTRS1995

Fast interrupt platform for extended DOS

Extended DOS offers the unique combination of a simple operating system which allows direct access to the interrupt tables, 32 bit protected mode access to 4096 MByte address space, and the use of industry standard C compilers. The drawback is that fast interrupt handling requires both 32 bit and 16 bit versions of each real-time process interrupt handler to avoid mode switches on the interrupts. A set of tools has been developed which automates the process of transforming the output of a standard 32 bit C compiler to 16 bit interrupt code which directly handles the real mode interrupts. The entire process compiles one set of source code via a make file, which boosts productivity by making the management of the compile-link cycle very simple. The software components are in the form of classes written mostly in C. A foreground process written as a conventional application which can use the standard C libraries can communicate with the background real-time classes via a message passing mechanism. The platform thus enables the integration of high performance real-time processing into a conventional application framework.

Duryea, T. W.↗

NASA NTRS1987

A/C 67 Investigation Board Final Report

On March 26, 1987, after the launch of an Atlas/Centaur rocket with a payload of a Navy Communications Satellite, a problem developed and the rocket was lost. John Busse chaired the Accident Investigation Board that was convened to investigate the incident. This videotape is a press conference with Mr Busse, who reviews the findings of the investigation concerning the loss of the Atlas/Centaur-67 launch vehicle. The loss is primarily attributed to a hardover engine yaw command that was caused by an erroneous signal from the digital computer unit. The generation of the erroneous signal is blamed on unfavorable weather conditions which created a lightning hazard. Mr. Busse, also, reviews the investigation's recommendations for avoiding similar occurrences. The press then asks questions about the findings and recommendations.

Source record↗