Search NASA⌕ Search

SEARCH · Search NASA

Results for “Routing”

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 613 records · Page 34

AI and workflow automation: The prototype electronic purchase request system

Automating 'paper' workflow processes with electronic forms and email can dramatically improve the efficiency of those processes. However, applications that involve complex forms that are used for a variety of purposes or that require numerous and varied approvals often require additional software tools to ensure that (1) the electronic form is correctly and completely filled out, and (2) the form is routed to the proper individuals and organizations for approval. The prototype electronic purchase request (PEPR) system, which has been in pilot use at NASA Ames Research Center since December 1993, seamlessly links a commercial electronics forms package and a CLIPS-based knowledge system that first ensures that electronic forms are correct and complete, and then generates an 'electronic routing slip' that is used to route the form to the people who must sign it. The PEPR validation module is context-sensitive, and can apply different validation rules at each step in the approval process. The PEPR system is form-independent, and has been applied to several different types of forms. The system employs a version of CLIPS that has been extended to support AppleScript, a recently-released scripting language for the Macintosh. This 'scriptability' provides both a transparent, flexible interface between the two programs and a means by which a single copy of the knowledge base can be utilized by numerous remote users.

Compton, Michael M.↗

Unstructured grids on SIMD torus machines

Unstructured grids lead to unstructured communication on distributed memory parallel computers, a problem that has been considered difficult. Here, we consider adaptive, offline communication routing for a SIMD processor grid. Our approach is empirical. We use large data sets drawn from supercomputing applications instead of an analytic model of communication load. The chief contribution of this paper is an experimental demonstration of the effectiveness of certain routing heuristics. Our routing algorithm is adaptive, nonminimal, and is generally designed to exploit locality. We have a parallel implementation of the router, and we report on its performance.

Bjorstad, Petter E.↗

A decentralized software bus based on IP multicas ting

We describe decentralized reconfigurable implementation of a conference management system based on the low-level Internet Protocol (IP) multicasting protocol. IP multicasting allows low-cost, world-wide, two-way transmission of data between large numbers of conferencing participants through the Multicasting Backbone (MBone). Each conference is structured as a software bus -- a messaging system that provides a run-time interconnection model that acts as a separate agent (i.e., the bus) for routing, queuing, and delivering messages between distributed programs. Unlike the client-server interconnection model, the software bus model provides a level of indirection that enhances the flexibility and reconfigurability of a distributed system. Current software bus implementations like POLYLITH, however, rely on a centralized bus process and point-to-point protocols (i.e., TCP/IP) to route, queue, and deliver messages. We implement a software bus called the MULTIBUS that relies on a separate process only for routing and uses a reliable IP multicasting protocol for delivery of messages. The use of multicasting means that interconnections are independent of IP machine addresses. This approach allows reconfiguration of bus participants during system execution without notifying other participants of new IP addresses. The use of IP multicasting also permits an economy of scale in the number of participants. We describe the MULITIBUS protocol elements and show how our implementation performs better than centralized bus implementations.

Callahan, John R.↗

Crew performance and communication: Performing a terrain navigation task

A study was conducted to examine the map and route cues pilots use while navigating under controlled, but realistic, nap-of-the-earth (NOE) flight conditions. US Army helicopter flight crews were presented a map and route overlay and asked to perform normal mission planning. They then viewed a video-recording of the out-the-window scene during low-level flights, without the route overlay, and were asked periodically to locate their current position on the map. The pilots and navigators were asked to communicate normally during the planning and flight phases. During each flight the navigator's response time, accuracy, and subjective workload were assessed. Post-flight NASA-TLX workload ratings were collected. No main effect of map orientation (north-up vs. track-up) was found for errors or response times on any of the tasks evaluated. Navigators in the north-up group rated their workload lower than those in the track-up group.

Battiste, Vernol↗

High-Speed Civil Transport Forecast: Simulated Airlines Scenarios for Mach 1.6, Mach 2.0, and Mach 2.4 Configurations for Year 2015

The report describes the development of a database of fuel burn and emissions from projected High Speed Civil Transport (HSCT) fleets that reflect actual airlines' networks, operational requirement, and traffic flow as operated by simulated world wide airlines for Mach 1.6, 2.0, and 2.4 HSCT configurations. For the year 2015, McDonnell Douglas Corporation created two supersonic commercial air traffic networks consisting of origin-destination city pair routes and associated traffic levels. The first scenario represented a manufacturing upper limit producible HSCT fleet availability by year 2015. The fleet projection of the Mach 2.4 configuration for this scenario was 1059 units with a traffic capture of 70 percent. The second scenario focused on the number of units that can minimally be produced by the year 2015. Using realistic production rates, the HSCT fleet projection amounts to 565 units. The traffic capture associated with this fleet was estimated at 40 percent. The airlines network was extracted from the actual networks of 21 major world airlines. All the routes were screened for suitability for HSCT operations. The route selection criteria included great circle distance, difference between flight path distance and great circle distance to avoid overland operations, and potential flight frequency.

Metwally, Munir↗

Analysis of Trajectory Parameters for Probe and Round-Trip Missions to Venus

For one-way transfers between Earth and Venus, charts are obtained that show velocity, time, and angle parameters as functions of the eccentricity and semilatus rectum of the Sun-focused vehicle conic. From these curves, others are obtained that are useful in planning one-way and round-trip missions to Venus. The analysis is characterized by circular coplanar planetary orbits, successive two-body approximations, impulsive velocity changes, and circular parking orbits at 1.1 planet radii. For round trips the mission time considered ranges from 65 to 788 days, while wait time spent in the parking orbit at Venus ranges from 0 to 467 days. Individual velocity increments, one-way travel times, and departure dates are presented for round trips requiring the minimum total velocity increment. For both single-pass and orbiting Venusian probes, the time span available for launch becomes appreciable with only a small increase in velocity-increment capability above the minimum requirement. Velocity-increment increases are much more effective in reducing travel time for single-pass probes than they are for orbiting probes. Round trips composed of a direct route along an ellipse tangent to Earth's orbit and an aphelion route result in the minimum total velocity increment for wait times less than 100 days and mission times ranging from 145 to 612 days. Minimum-total-velocity-increment trips may be taken along perihelion-perihelion routes for wait times ranging from 300 to 467 days. These wait times occur during missions lasting from 640 to 759 days.

Dugan, James F., Jr.↗

Modeling the Effect of Wetlands, Flooding, and Irrigation on River Flow: Application to the Aral Sea

As the world's population continues to increase, additional stress is placed on water resources. This stress, coupled with future uncertainties regarding climate change, makes arid and semi-arid regions particularly vulnerable. One example is the Aral Sea where the freshwater inflow, which is dominated by snowmelt runoff, has decreased significantly since the expansion of intensive irrigation in the 1960s. The purpose of this paper is to use a river routing scheme from a global climate model to examine the flow of the Amu Dar'ya River into the Aral Sea. The river routing scheme is modified to include groundwater flow, flooding, and evaporative losses in the river's wetlands and floodplain, and anthropogenic withdrawals for irrigation. A set of scenarios is designed to test the sensitivity of river flow to the inclusion of these modifications into the river routing scheme. When riverine wetlands and floodplains are present, the river flow is reduced significantly and is similar to the observed flow. In addition the model results show that it is essential to incorporate human diversions to accurately represent the inflow to the Aral Sea, and they also indicate potential management strategies that might be appropriate to maintain a balance between inflow to the Sea and upstream diversions for irrigation.

Ferrari, Michael R.↗

Novel Highly Parallel and Systolic Architectures Using Quantum Dot-Based Hardware

VLSI technology has made possible the integration of massive number of components (processors, memory, etc.) into a single chip. In VLSI design, memory and processing power are relatively cheap and the main emphasis of the design is on reducing the overall interconnection complexity since data routing costs dominate the power, time, and area required to implement a computation. Communication is costly because wires occupy the most space on a circuit and it can also degrade clock time. In fact, much of the complexity (and hence the cost) of VLSI design results from minimization of data routing. The main difficulty in VLSI routing is due to the fact that crossing of the lines carrying data, instruction, control, etc. is not possible in a plane. Thus, in order to meet this constraint, the VLSI design aims at keeping the architecture highly regular with local and short interconnection. As a result, while the high level of integration has opened the way for massively parallel computation, practical and full exploitation of such a capability in many applications of interest has been hindered by the constraints on interconnection pattern. More precisely. the use of only localized communication significantly simplifies the design of interconnection architecture but at the expense of somewhat restricted class of applications. For example, there are currently commercially available products integrating; hundreds of simple processor elements within a single chip. However, the lack of adequate interconnection pattern among these processing elements make them inefficient for exploiting a large degree of parallelism in many applications.

Fijany, Amir↗

Flight Crew Factors for CTAS/FMS Integration in the Terminal Area

Center TRACON Automation System (CTAS)/Flight Management System (FMS) integration on the flightdeck implies flight crews flying coupled in highly automated FMS modes [i.e. Vertical Navigation (VNAV) and Lateral Navigation (LNAV)] from top of descent to the final approach phase of flight. Pilots may also have to make FMS route edits and respond to datalink clearances in the Terminal Radar Approach Control (TRACON) airspace. This full mission simulator study addresses how the introduction of these FMS descent procedures affect crew activities, workload, and performance. It also assesses crew acceptance of these procedures. Results indicate that the number of crew activities and workload ratings are significantly reduced below current day levels when FMS procedures can be flown uninterrupted, but that activity numbers increase significantly above current day levels and workload ratings return to current day levels when FMS procedures are interrupted by common ATC interventions and CTAS routing advisories. Crew performance showed some problems with speed control during FMS procedures. Crew acceptance of the FMS procedures and route modification requirements was generally high; a minority of crews expressed concerns about use of VNAV in the TRACON airspace. Suggestions for future study are discussed.

Crane, Barry W.↗

AWE: Aviation Weather Data Visualization

The two official sources for aviation weather reports both require the pilot to mentally visualize the provided information. In contrast, our system, Aviation Weather Environment (AWE) presents aviation specific weather available to pilots in an easy to visualize form. We start with a computer-generated textual briefing for a specific area. We map this briefing onto a grid specific to the pilot's route that includes only information relevant to his flight route that includes only information relevant to his flight as defined by route, altitude, true airspeed, and proposed departure time. By modifying various parameters, the pilot can use AWE as a planning tool as well as a weather briefing tool.

Spirkovska, Lilly↗

A Fast-Time Study of Aircraft Reordering in Arrival Sequencing and Scheduling

In order to ensure that the safe capacity of the terminal area is not exceeded, Air Traffic Management ATM often places restrictions on arriving flights transitioning from en route airspace to terminal airspace. This restriction of arrival traffic is commonly referred to as arrival flow management, and includes techniques such as metering, vectoring, fix-load balancing, and the imposition of miles-in-trail separations. These restrictions are enacted without regard for the relative priority which airlines may be placing on individual flights based on factors such as crew criticality, passenger connectivity, critical turn times, gate availability, on-time performance, fuel status, or runway preference. The development of new arrival flow management techniques which take into consideration priorities expressed by air carriers will likely reduce the economic impact of ATM restrictions on the airlines and lead to increased airline economic efficiency by allowing airlines to have greater control over their individual arrival banks of aircraft. NASA and the Federal Aviation Administration (FAA) have designed and developed a suite of software decision support tools (DSTs) collectively known as the Center TRACON Automation System (CTAS). One of these tools, the Traffic Management Advisor (TMA) is currently being used at the Fort Worth Air Route Traffic Control Center to perform arrival flow management of traffic into the Dallas/Fort Worth airport (DFW). The TMA is a time-based strategic planning tool that assists Traffic Management Coordinators (TMCs) and En Route Air Traffic Controllers in efficiently balancing arrival demand with airport capacity. The primary algorithm in the TMA is a real-time scheduler which generates efficient landing sequences and landing times for arrivals within about 200 no a. from touchdown. This scheduler will sequence aircraft so that they arrive in a first- come - first-served (FCFS) order. While FCFS sequencing establishes a fair order based on estimated times of arrival, it does not take into account individual airline priorities among incoming flights. NASA is exploring the possibility of allowing airlines to express relative arrival priorities to air traffic management through the development of new CTAS scheduling algorithms which take into consideration airline arrival preferences. The accommodation of airline priorities in arrival sequencing and scheduling would under most circumstances result in a deviation from a "natural" or FCFS arrival order. As a First step toward developing airline influenced sequencing algorithms, an investigation was conducted to determine the feasibility of reordering arrival traffic from a strict FCFS sequence. A fast-time simulation has been developed which allows statistical evaluation of sequencing and scheduling algorithms for arrival traffic at the Dallas/Fort Worth Airport. In contrast to real-time simulation or field tests, which would require on the order of ninety minutes to examine a single traffic rush period, the fast-time simulation allows examination of multiple rush periods in a matter of seconds.

Carr, Greg↗

Experimental Evaluation of CTAS/FMS Integration in TRACON Airspace

A CTAS/FMS integration project at Ames Research Center addresses extensions to the CTAS air traffic management concept, among them the introduction of arrival routes specially designed for the use with a Flight Management System. These FMS arrival routes shall allow for the use of the INS' lateral and vertical navigation capabilities throughout the arrival until final approach. For the use in this project CTAS controller support tools that compliment the concept have been created. These tools offer controllers access to CTAS' prediction and planning capabilities in terms of speed and route advisories. The objective is to allow for a more strategic way of controlling aircraft. Expected benefits are an increase in arrival rate and a reduction of average travel times through TRACER airspace. A real time simulation is being conducted at Ames to investigate how FMS arrivals and approach transitions - with and without the support of CTAS tools - effect the flow of arriving traffic within TRACER airspace and the controllers' task performance. Four conditions will be investigated and compared to today's technique of controlling traffic with tactical vectoring: 1. FMS arrivals and approach transitions are available for controllers to issue to equipped aircraft - traffic permitting; 2. Speed advisories that match CTAS' runway balancing and sequencing plan are displayed to Feeder controllers; 3. Approach transition advisories (e.g., location of the base turn point) are displayed to Final controllers for tactical clearances ("Turn base now"); and 4. Approach transition advisories (voice and data link) are generated by CTAS and displayed to final controllers for strategic voice clearances ("Turn base five miles after waypoint xyz") or prepared in terms of a trajectory description for strategic data link clearance. Scenarios used in the study will represent current traffic and vary in density of arriving traffic and the kind and mix of equipage of arriving aircraft. Data will be collected from experiment runs with active TRACON controllers on the final approach spacing, the aircraft's speed profiles, the controllers interaction with CTAS tools, and number and timing of pilot controllers communications under the described conditions.

Romahn, Stephen↗

An Operational Concept for Flying FMS Trajectories in Center and TRACON Airspace

Current Flight Management Systems (FMS) do a good job of constructing and flying an optimal trajectory for a single aircraft. Unfortunately, flight crews are often unable to fly these FMS routes during arrivals at busy airports. The Center TRACON Automation System (CTAS) has been designed to aid Center and TRACON (Terminal Radar Approach Control) controllers in assigning runways, sequencing and vectoring all classes of aircraft. CTAS bases its advisories on trajectory predictions for arriving aircraft using algorithms very similar to those in airborne FMS systems. This paper presents near and far term operational concepts for how a ground ATM (air traffic management) automation system like CTAS could work more effectively with the airborne automation in FMS equipped aircraft. The concepts for a more compatible air-ground system include: 1) a common route databases for both CTAS and FMS; 2) datalink to downlink information on aircraft weight, final approach speed and trajectory intent and to uplink wind information; 3) new FMS functions to allow flight crews to easily update their FMS trajectory to match the trajectory suggested by the ground automation with voice clearances, and 4) in the far term, datalink to downlink user preferred trajectories and to uplink trajectory clearances in the terminal area. The paper analyses some of the human factors issues that may result in allowing aircraft to fly FMS routes during enroute descent and in the terminal area. A series of linked human in the loop flight deck and air traffic control simulations and a field test with the NASA 757 are being conducted at NASA's Ames and Langley Research Centers to address these issues and to evaluate the operational feasibility of these approaches to more efficient flight and increased airport throughput.

Palmer, Everett↗

Operational Limitations of the High Rate Frame Multiplexer (HRFM) Onboard the International Space Station(ISS)-and How These Limitations Affect Payload Developers (PDs) and International Partners (IPs)

The data system onboard the United States Operating Segment (USOS) of the ISS is currently used to capture, route, record and downlink high-rate science data from experiments inside the US Lab. Once NASDA's Japanese Experiment Module (JEM) and ESA's Attached Pressurized Module (APM) are launched - in the 2004 to 2005 timeframe - data from these facilities will also be routed to the ground using the USOS data system. A critical component of the USOS data system is the High Rate Frame Multiplexer (HRFM). The HRFM combines multiple data/video inputs and combines them into one data stream. This Ku-band data stream is then routed through the Tracking and Data Relay Satellite (TDRS) system to the ground. The Data Management Coordinator (DMC) - located at the Marshall Space Flight Center's Payload Operations Center (POC) - is responsible for commanding and controlling the HRFM. The HRFM can multiplex a maximum of eight digital data sources and four digital video sources. Thus far, this limitation has not been constraining to operations. However, once the JEM and APM are integrated, the HRFM limitations will become a major constraint to science operations onboard. The purpose of this paper is to characterize the limitations of the HRFM and to explain how these limitations can be successfully managed. With this information, Payload Developers and International Partners will be able to more effectively utilize the data systems onboard the ISS. Ultimately, more science data can be captured and downlinked to Flight Controllers and Scientists on the ground.

Mixson, Charles D.↗

A Genetic Representation for Evolutionary Fault Recovery in Virtex FPGAs

Most evolutionary approaches to fault recovery in FPGAs focus on evolving alternative logic configurations as opposed to evolving the intra-cell routing. Since the majority of transistors in a typical FPGA are dedicated to interconnect, nearly 80% according to one estimate, evolutionary fault-recovery systems should benefit hy accommodating routing. In this paper, we propose an evolutionary fault-recovery system employing a genetic representation that takes into account both logic and routing configurations. Experiments were run using a software model of the Xilinx Virtex FPGA. We report that using four Virtex combinational logic blocks, we were able to evolve a 100% accurate quadrature decoder finite state machine in the presence of a stuck-at-zero fault.

Lohn, Jason↗

Neighboring Optimal Aircraft Guidance in a General Wind Environment

Method and system for determining an optimal route for an aircraft moving between first and second waypoints in a general wind environment. A selected first wind environment is analyzed for which a nominal solution can be determined. A second wind environment is then incorporated; and a neighboring optimal control (NOC) analysis is performed to estimate an optimal route for the second wind environment. In particular examples with flight distances of 2500 and 6000 nautical miles in the presence of constant or piecewise linearly varying winds, the difference in flight time between a nominal solution and an optimal solution is 3.4 to 5 percent. Constant or variable winds and aircraft speeds can be used. Updated second wind environment information can be provided and used to obtain an updated optimal route.

Jardin, Matthew R.↗

Document Concurrence System

The Document Concurrence System is a combination of software modules for routing users' expressions of concurrence with documents. This system enables determination of the current status of concurrences and eliminates the need for the prior practice of manually delivering paper documents to all persons whose approvals were required. This system runs on a server, and participants gain access via personal computers equipped with Web-browser and electronic-mail software. A user can begin a concurrence routing process by logging onto an administration module, naming the approvers and stating the sequence for routing among them, and attaching documents. The server then sends a message to the first person on the list. Upon concurrence by the first person, the system sends a message to the second person, and so forth. A person on the list indicates approval, places the documents on hold, or indicates disapproval, via a Web-based module. When the last person on the list had concurred, a message is sent to the initiator, who can then finalize the process through the administration module. A background process running on the server identifies concurrence processes that are overdue and sends reminders to the appropriate persons.

Muhsin, Mansour↗

Document Concurrence System

The Document Concurrence System is a combination of software modules for routing users' expressions of concurrence with documents. This system enables determination of the current status of concurrences and eliminates the need for the prior practice of manually delivering paper documents to all persons whose approvals were required. This system runs on a server, and participants gain access via personal computers equipped with Web-browser and electronic-mail software. A user can begin a concurrence routing process by logging onto an administration module, naming the approvers and stating the sequence for routing among them, and attaching documents. The server then sends a message to the first person on the list. Upon concurrence by the first person, the system sends a message to the second person, and so forth. A person on the list indicates approval, places the documents on hold, or indicates disapproval, via a Web-based module. When the last person on the list has concurred, a message is sent to the initiator, who can then finalize the process through the administration module. A background process running on the server identifies concurrence processes that are overdue and sends reminders to the appropriate persons.

Muhsin, Mansour↗