Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “user interfaces”

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

Deploying a Route Optimization EFB Application for Commercial Airline Operational Trials

The Traffic Aware Planner (TAP), developed for NASA Langley Research Center to support the Traffic Aware Strategic Aircrew Requests (TASAR) project, is a flight-efficiency software application developed for an Electronic Flight Bag (EFB). Tested in two flight trials and planned for operational testing by two commercial airlines, TAP is a real-time trajectory optimization application that leverages connectivity with onboard avionics and broadband Internet sources to compute and recommend route modifications to flight crews to improve fuel and time performance. The application utilizes a wide range of data, including Automatic Dependent Surveillance Broadcast (ADS-B) traffic, Flight Management System (FMS) guidance and intent, on-board sensors, published winds and weather, and Special Use Airspace (SUA) schedules. This paper discusses the challenges of developing and deploying TAP to various EFB platforms, our solutions to some of these challenges, and lessons learned, to assist commercial software developers and hardware manufacturers in their efforts to implement and extend TAP functionality in their environments. EFB applications (such as TAP) typically access avionics data via an ARINC 834 Simple Text Avionics Protocol (STAP) server hosted by an Aircraft Interface Device (AID) or other installed hardware. While the protocol is standardized, the data sources, content, and transmission rates can vary from aircraft to aircraft. Additionally, the method of communicating with the AID may vary depending on EFB hardware and/or the availability of onboard networking services, such as Ethernet, WIFI, Bluetooth, or other mechanisms. EFBs with portable and installed components can be implemented using a variety of operating systems, and cockpits are increasingly incorporating tablet-based technologies, further expanding the number of platforms the application may need to support. Supporting multiple EFB platforms, AIDs, avionics datasets, and user interfaces presents a challenge for software developers and the management of their code baselines. Maintaining multiple baselines to support all deployment targets can be extremely cumbersome and expensive. Certification also needs to be considered when developing the application. Regardless of whether the software is itself destined to be certified, data requirements in support of the application and user interface elements may introduce certification requirements for EFB manufacturers and the airlines. The example of TAP, the challenges faced, solutions implemented, and lessons learned will give EFB application and hardware developers insight into future potential requirements in deploying TAP or similar flight-deck EFB applications.

Roscoe, David A.↗
NASA NTRS1997

Transfer of the CONSOL-OPTCAD Rotorcraft Design Tool to Industry

Significant progress was made. Initial results on the improvement of the user-friendliness and useability of GIFCORCODE led to the decision to provide GIFCORCODE with a menu-driven user interface. In collaboration with staff at Moffett field and students from Cal Poly this objective has been largely met. GIFCORCODE is now menu-driven and very much easier to use. Complete designs for stability and control augmentation systems for the UH-60A ADOCS/RASCAL rotorcraft in both hover and 80 knots forward flight have been completed and documented. The originally planned presentations to industry were deferred so the new user interface for GIFCORCODE could be completed. The industry presentations are now planned for the next year. Similarly, the work on preparing a short course on the use of GIFCORCODE was deferred. The details of the original goals for this contract are presented in this report. The modifications to these goals and the reasons for them are also described. This is followed by a section containing the results of work on this contract. A final section, conclusions, contains suggestions for future work on this project.

Levine, William S.↗
NASA NTRS1998

Next Generation User Support Tools

One of the manually intensive efforts of Hubble Space Telescope (HST) observing is the specification and validation of the detailed proposals for scientists observing with the telescope. In order to meet the operational cost objectives for the Next Generation Space Telescope (NGST), this process needs to be dramatically less time consuming and less costly. We have prototyped a new proposal development system, the Scientist's Expert Assistant (SEA), using a combination of artificial intelligence and user interface techniques to reduce the time and effort involved for both scientists and the telescope operations staff. The Advanced Architectures and Automation Branch of NASA's Goddard Space Flight Center is working with the Space Telescope Science Institute (ST ScI) to explore SEA alternatives. We are testing the usefulness of rule-based expert systems to painlessly guide a scientist to his or her desired observation specification. We are also examining several potential user interface paradigms and exploring data visualization schemes to see which techniques are more intuitive. Our prototypes will be validated using HST's Advanced Camera for Surveys (ACS) instrument (scheduled for installation in 1999) as a live test instrument. Having an operational test-bed will ensure the most realistic feedback possible for the prototyping cycle. In addition, once the NGST instruments are better defined, the SEA will already be a proven platform that simply needs adapting to NGST-specific instruments.

Jones, Jeremy E.↗
NASA NTRS2011

Content Documents Management

The Content Documents are created and managed under the System Software group with. Launch Control System (LCS) project. The System Software product group is lead by NASA Engineering Control and Data Systems branch (NE~C3) at Kennedy Space Center. The team is working on creating Operating System Images (OSI) for different platforms (i.e. AIX, Linux, Solaris and Windows). Before the OSI can be created, the team must create a Content Document which provides the information of a workstation or server, with the list of all the software that is to be installed on it and also the set where the hardware belongs. This can be for example in the LDS, the ADS or the FR-l. The objective of this project is to create a User Interface Web application that can manage the information of the Content Documents, with all the correct validations and filters for administrator purposes. For this project we used one of the most excellent tools in agile development applications called Ruby on Rails. This tool helps pragmatic programmers develop Web applications with Rails framework and Ruby programming language. It is very amazing to see how a student can learn about OOP features with the Ruby language, manage the user interface with HTML and CSS, create associations and queries with gems, manage databases and run a server with MYSQL, run shell commands with command prompt and create Web frameworks with Rails. All of this in a real world project and in just fifteen weeks!

Muniz, R.↗
NASA NTRS1993

Visualization techniques to aid in the analysis of multi-spectral astrophysical data sets

The goal of this project was to support the scientific analysis of multi-spectral astrophysical data by means of scientific visualization. Scientific visualization offers its greatest value if it is not used as a method separate or alternative to other data analysis methods but rather in addition to these methods. Together with quantitative analysis of data, such as offered by statistical analysis, image or signal processing, visualization attempts to explore all information inherent in astrophysical data in the most effective way. Data visualization is one aspect of data analysis. Our taxonomy as developed in Section 2 includes identification and access to existing information, preprocessing and quantitative analysis of data, visual representation and the user interface as major components to the software environment of astrophysical data analysis. In pursuing our goal to provide methods and tools for scientific visualization of multi-spectral astrophysical data, we therefore looked at scientific data analysis as one whole process, adding visualization tools to an already existing environment and integrating the various components that define a scientific data analysis environment. As long as the software development process of each component is separate from all other components, users of data analysis software are constantly interrupted in their scientific work in order to convert from one data format to another, or to move from one storage medium to another, or to switch from one user interface to another. We also took an in-depth look at scientific visualization and its underlying concepts, current visualization systems, their contributions, and their shortcomings. The role of data visualization is to stimulate mental processes different from quantitative data analysis, such as the perception of spatial relationships or the discovery of patterns or anomalies while browsing through large data sets. Visualization often leads to an intuitive understanding of the meaning of data values and their relationships by sacrificing accuracy in interpreting the data values. In order to be accurate in the interpretation, data values need to be measured, computed on, and compared to theoretical or empirical models (quantitative analysis). If visualization software hampers quantitative analysis (which happens with some commercial visualization products), its use is greatly diminished for astrophysical data analysis. The software system STAR (Scientific Toolkit for Astrophysical Research) was developed as a prototype during the course of the project to better understand the pragmatic concerns raised in the project. STAR led to a better understanding on the importance of collaboration between astrophysicists and computer scientists.

Brugel, Edward W.↗
NASA NTRS1993

Visualization techniques to aid in the analysis of multispectral astrophysical data sets

The goal of this project was to support the scientific analysis of multi-spectral astrophysical data by means of scientific visualization. Scientific visualization offers its greatest value if it is not used as a method separate or alternative to other data analysis methods but rather in addition to these methods. Together with quantitative analysis of data, such as offered by statistical analysis, image or signal processing, visualization attempts to explore all information inherent in astrophysical data in the most effective way. Data visualization is one aspect of data analysis. Our taxonomy as developed in Section 2 includes identification and access to existing information, preprocessing and quantitative analysis of data, visual representation and the user interface as major components to the software environment of astrophysical data analysis. In pursuing our goal to provide methods and tools for scientific visualization of multi-spectral astrophysical data, we therefore looked at scientific data analysis as one whole process, adding visualization tools to an already existing environment and integrating the various components that define a scientific data analysis environment. As long as the software development process of each component is separate from all other components, users of data analysis software are constantly interrupted in their scientific work in order to convert from one data format to another, or to move from one storage medium to another, or to switch from one user interface to another. We also took an in-depth look at scientific visualization and its underlying concepts, current visualization systems, their contributions and their shortcomings. The role of data visualization is to stimulate mental processes different from quantitative data analysis, such as the perception of spatial relationships or the discovery of patterns or anomalies while browsing through large data sets. Visualization often leads to an intuitive understanding of the meaning of data values and their relationships by sacrificing accuracy in interpreting the data values. In order to be accurate in the interpretation, data values need to be measured, computed on, and compared to theoretical or empirical models (quantitative analysis). If visualization software hampers quantitative analysis (which happens with some commercial visualization products), its use is greatly diminished for astrophysical data analysis. The software system STAR (Scientific Toolkit for Astrophysical Research) was developed as a prototype during the course of the project to better understand the pragmatic concerns raised in the project. STAR led to a better understanding on the importance of collaboration between astrophysicists and computer scientists. Twenty-one examples of the use of visualization for astrophysical data are included with this report. Sixteen publications related to efforts performed during or initiated through work on this project are listed at the end of this report.

Brugel, E. W.↗
NASA NTRS1992

GRO/EGRET data analysis software: An integrated system of custom and commercial software using standard interfaces

The Energetic Gamma Ray Telescope Experiment (EGRET) on the Compton Gamma Ray Observatory has been in orbit for more than a year and is being used to map the full sky for gamma rays in a wide energy range from 30 to 20,000 MeV. Already these measurements have resulted in a wide range of exciting new information on quasars, pulsars, galactic sources, and diffuse gamma ray emission. The central part of the analysis is done with sky maps that typically cover an 80 x 80 degree section of the sky for an exposure time of several days. Specific software developed for this program generates the counts, exposure, and intensity maps. The analysis is done on a network of UNIX based workstations and takes full advantage of a custom-built user interface called X-dialog. The maps that are generated are stored in the FITS format for a collection of energies. These, along with similar diffuse emission background maps generated from a model calculation, serve as input to a maximum likelihood program that produces maps of likelihood with optional contours that are used to evaluate regions for sources. Likelihood also evaluates the background corrected intensity at each location for each energy interval from which spectra can be generated. Being in a standard FITS format permits all of the maps to be easily accessed by the full complement of tools available in several commercial astronomical analysis systems. In the EGRET case, IDL is used to produce graphics plots in two and three dimensions and to quickly implement any special evaluation that might be desired. Other custom-built software, such as the spectral and pulsar analyses, take advantage of the XView toolkit for display and Postscript output for the color hard copy. This poster paper outlines the data flow and provides examples of the user interfaces and output products. It stresses the advantages that are derived from the integration of the specific instrument-unique software and powerful commercial tools for graphics and statistical evaluation. This approach has several proven advantages including flexibility, a minimum of development effort, ease of use, and portability.

Laubenthal, N. A.↗
NASA NTRS1992

IRAF in the nineties

The Interactive Data Reduction and Analysis Facility (IRAF) data reduction and analysis system has been around since 1981. Today it is a mature system with hundreds of applications, and is supported on all the major platforms. Many institutions, projects, and individuals around the US and around the world have developed software for IRAF. Some of these packages are comparable in size to the IRAF core system itself. IRAF is both a data analysis system, and a programming environment. As a data analysis system it can be easily installed by a user at a remote site and immediately used to view and process data. As a programming environment IRAF contains a wealth of high and low level facilities for developing new applications for interactive and automated processing of astronomical or other data. As important as the applications programs and user interfaces are to the scientist using IRAF, the heart of the IRAF system is the programming environment. The programming environment determines to a large extent the types of applications which can be built within IRAF, what they will look like, and how they will interact with one another and with the user. While applications can be easily added to or removed from a software system, the programming environment must remain fairly stable, with carefully planned evolution and growth, over the lifetime of a system. The IRAF programming environment is the framework on which the rest of the IRAF system is built. The IRAF programming environment as it exists in 1992, and the work currently underway to enhance the environment are discussed. The structure of the programming environment as a class hierarchy is discussed, with emphasis on the work being done on the image data structures, graphics and image display interfaces, and user interfaces. The new technologies which we feel IRAF must deal with successfully over the coming years are discussed. Finally, a preview of what IRAF might look like to the user by the end of the decade is presented.

Tody, D.↗
NASA NTRS1999

Concept Mapping as a Support for Mars Landing-Site Selection

The NASA Ames' Center for Mars Exploration (CMEX) serves to coordinate Mars programmatic research at ARC in the sciences, in information technology and in aero-assist and other technologies. Most recently, CMEX has been working with the Institute for Human and Machine Cognition at the University of West Florida to develop a new kind of web browser based on the application of concept maps. These Cmaps, which are demonstrably effective in science teaching, can be used to provide a new kind of information navigation tool that can make web or CD based information more meaningful and more easily navigable. CMEX expects that its 1999 CD-ROM will have this new user interface. CMEX is also engaged with the Mars Surveyor Project Office at JPL in developing an Internet-based source of materials to support the process of selecting landing sites for the next series of Mars landers. This activity -- identifying the most promising sites from which to return samples relevant to the search for evidence of life -- is one that is expected to engage the general public as well as the science community. To make the landing site data easily accessible and meaningful to the public, CMEX is planning to use the IHMC Cmap browser as its user interface.

Cabrol, Nathalie A.↗
NASA NTRS1980

Integration of design information

The overall concepts of the integrated programs for aerospace-vehicle design (IPAD) from the user's viewpoint are discussed. Also a top-level view of what the user requires from such a system is provided, and the interactions between the system and user are described. The four major components discussed are design process; data storage, management and manipulation; user interface; and project management. Although an outgrowth of aerospace production experience, the basic concepts discussed, and especially their emphasis on integration, are considered applicable to all problem solving. Thus, these concepts may offer a broad base for exploitation by industry in general. This is the first in a set of three papers, the other two being Future Integrated Design Process, by D. D. Mayer, and Requirements for Company-Wide Management of Engineering Information, by J. W. Southall. In addition to tying the three together, how project management can be handled in a computing environment and also the user interface needs are discussed in detail.

Anderton, G. L.↗
NASA NTRSDate not supplied

RApid Blade and Blade-Vortex InTeraction (RABBIT) Reimagined: Algorithm Improvement and User-Friendly Interface Implementation

Rotorcraft noise source identification and reduction is crucial to the emergence of the Urban Air Mobility (UAM) market. One key rotor noise source is Blade Vortex Interaction (BVI), caused by the rotor blades interacting with the rotor wake. The low-fidelity RApid Blade and Blade-Vortex InTeraction (RABBIT) tool was created to predict the location and characteristics of BVI noise. RABBIT enables engineers to quickly design and simulate UAM configurations and understand BVI occurrences for a desired flight condition. Furthermore, RABBIT can also identify the time and location of blade overlap for coaxial rotors. RABBIT is not a general acoustic prediction tool, but instead utilizes vortex and wake parameters to visualize and predict BVI aerodynamics. RABBIT algorithm has been further developed including reduction of computational time, accounting for BVI source time arrival, improved vortex strength modeling, and BVI impulse factor. A user-friendly app is presented with the intent of bringing RABBIT to the masses to allow engineers from various educational backgrounds to design and begin to understand BVI. Furthermore, RABBIT capabilities are highlighted by a parameter study highlighting key parameters that impact BVIalong with highlighting RABBIT’s ability to identify BVI occurrences from other rotors.

RApid↗
NASA NTRS1995

Geometric modeling for computer aided design

The primary goal of this grant has been the design and implementation of software to be used in the conceptual design of aerospace vehicles particularly focused on the elements of geometric design, graphical user interfaces, and the interaction of the multitude of software typically used in this engineering environment. This has resulted in the development of several analysis packages and design studies. These include two major software systems currently used in the conceptual level design of aerospace vehicles. These tools are SMART, the Solid Modeling Aerospace Research Tool, and EASIE, the Environment for Software Integration and Execution. Additional software tools were designed and implemented to address the needs of the engineer working in the conceptual design environment. SMART provides conceptual designers with a rapid prototyping capability and several engineering analysis capabilities. In addition, SMART has a carefully engineered user interface that makes it easy to learn and use. Finally, a number of specialty characteristics have been built into SMART which allow it to be used efficiently as a front end geometry processor for other analysis packages. EASIE provides a set of interactive utilities that simplify the task of building and executing computer aided design systems consisting of diverse, stand-alone, analysis codes. Resulting in a streamlining of the exchange of data between programs reducing errors and improving the efficiency. EASIE provides both a methodology and a collection of software tools to ease the task of coordinating engineering design and analysis codes.

Schwing, James L.↗
NASA NTRS2020

Design of Autonomous Medical Response Agent (AMRA) Aggregate Information Dashboard (AID)

Future astronauts in deep space missions will rely on tools and technologies empowering them to self-diagnose and self-treat medical conditions. Given communications delays and limited bandwidth in future long-duration exploration missions (LDEMs), medical decision support technologies must empower the crew to manage routine medical activities, acute medical incidents, as well as emergency medical scenarios independently from ground support.The Autonomous Medical Response Agent (AMRA) is envisioned as a digital tool enabling crew to issue medical complaints and interact with a medical decision support algorithm which develops a differential diagnosis and recommends a treatment protocol for the condition. AMRA will draw from individual crew medical history in addition to crew symptoms to more efficiently identify high-risk medical conditions. A new symptom could be indicative of a chronic condition or a normal adaptation to long-duration spaceflight, but could just as easily be indicative of an adverse vehicle condition affecting the entire crew.While real-time communication with a flight surgeon may not possible, the crew will nonetheless require a means to communicate and document both routine and emergency medical incidents to ground support. Conversely, flight surgeons and medical specialists on the ground will need to understand information such as crew vitals or responses to medical check-ups and examinations within the larger context of crew schedule, mission activities, and vehicle performance. A user interface which establishes communication protocols between an individual crew member and AMRA, as well as ground support to the crew is a significant area of research demanding input and consideration.The design of AMRA AID is intended to: a) represent routine medical activities as well as new (unplanned) medical incidents within the larger context of crew schedule and mission activities, and b) increase confidence between ground support and crew members over the course of LDEMs. Maintaining situation awareness of unplanned medical incidents between ground and crew will be a critical element within LDEMs. Two medical incidents headache and difficulty breathing are being explored within a user interface prototype which captures communications protocols between crew members and mission control, human health monitoring, vehicle or environmental monitoring, as well as crew schedule and mission activities holistically.

Yashar, M.↗
NASA NTRSDate not supplied

Astrobee Operations on the Iss: Gui’S Impact on the Operators’ Cognitive Load

The Astrobee free-flying robots have completed their fifth successful year of operations housed in the Japanese Experimental Module (JEM) on the International Space Station (ISS). In this paper, we introduce two Graphical User Interfaces (GUI) used to operate and monitor in real-time the Astrobee free-flying robots onboard the ISS and report on the impact these GUIs have in the operator’s cognitive load. A review of the state-of-the-art GUI design for remotely teleoperated scenarios with minimal time delay is presented and the study’s conclusion used to determine the elements and recommendations to create an interface that minimizes its impact on the overall performance of an operator during an activity at the ISS. The Ground Data System (GDS) is one of the two GUIs in the study: it contains several tabs, each of which displays a different set of controls for specific tasks e.g. Overview, Run Plan, Teleoperate, Guest Science; some also display video and a three-dimensional (3D) representation of the ISS and robot based on the Astrobee’s telemetry. Most tabs enable a single operator-robot connection, however some of its tabs are capable to monitor and control up to three Astrobees simultaneously. The GDS Helper is a text-based user interface created to facilitate commanding and monitoring of an Astrobee robot directly from an SSH session. In full interactive mode it displays a maximum of 5 sections: general commanding, feedback/ack, telemetry, guest science commanding, and data, all in one view. In batch mode, it enables complex command scripting while retaining some interactive capabilities. A comparative analysis between these GUIs is carried out at an analogous ISS environment at the NASA Ames Research Center’s Granite Lab and its results presented. While GDS is able to provide an operator with control and situational awareness via its video and 3D displays, its several tabs may introduce an overwhelming amount of information confusing and delaying the operator especially during time-sensitive maneuvers where the operator may need to switch back and forth between them. GDS helper in the other hand does not provide video or 3D displays thus not allowing an operator to attain situational awareness, however it provides the operator with a design displaying commonly used data in a single window, enabling the operator to understand the state of the robot at a glance and control it through a commands entered via keyboard instead of a combination of mouse clicks and keyboard input. The results of the experiments measure the cognitive load across several operators maneuvering Astrobee to accomplish tasks ranging from fully manual to supervised activities. A GUI combining a single window displaying data along video and a 3D display is expected to reduce the operator’s cognitive load.

Astrobee↗
NASA NTRS1999

Space Adaptation of Active Mirror Segment Concepts

This report summarizes the results of a three year effort by Blue Line Engineering Co. to advance the state of segmented mirror systems in several separate but related areas. The initial set of tasks were designed to address the issues of system level architecture, digital processing system, cluster level support structures, and advanced mirror fabrication concepts. Later in the project new tasks were added to provide support to the existing segmented mirror testbed at Marshall Space Flight Center (MSFC) in the form of upgrades to the 36 subaperture wavefront sensor. Still later, tasks were added to build and install a new system processor based on the results of the new system architecture. The project was successful in achieving a number of important results. These include the following most notable accomplishments: 1) The creation of a new modular digital processing system that is extremely capable and may be applied to a wide range of segmented mirror systems as well as many classes of Multiple Input Multiple Output (MIMO) control systems such as active structures or industrial automation. 2) A new graphical user interface was created for operation of segmented mirror systems. 3) The development of a high bit rate serial data loop that permits bi-directional flow of data to and from as many as 39 segments daisy-chained to form a single cluster of segments. 4) Upgrade of the 36 subaperture Hartmann type Wave Front Sensor (WFS) of the Phased Array Mirror, Extendible Large Aperture (PAMELA) testbed at MSFC resulting in a 40 to 5OX improvement in SNR which in turn enabled NASA personnel to achieve many significant strides in improved closed-loop system operation in 1998. 5) A new system level processor was built and delivered to MSFC for use with the PAMELA testbed. This new system featured a new graphical user interface to replace the obsolete and non-supported menu system originally delivered with the PAMELA system. The hardware featured Blue Line's new stackable processing system which included fiber optic data links, a WFS digital interface, and a very compact and reliable electronics package. The project also resulted in substantial advances in the evolution of concepts for integrated structures to be used to support clusters of segments while also serving as the means to distribute power, timing, and data communications resources. A prototype cluster base was built and delivered that would support a small array of 7 cm mirror segments. Another conceptual design effort led to substantial progress in the area of laminated silicon mirror segments. While finished mirrors were never successfully produced in this exploratory effort, the basic feasibility of the concept was established through a significant amount of experimental development in microelectronics processing laboratories at the University of Colorado in Colorado Springs. Ultimately lightweighted aluminum mirrors with replicated front surfaces were produced and delivered as part of a separate contract to develop integrated segmented mirror assemblies. Overall the project was very successful in advancing segmented mirror system architectures on several fronts. In fact, the results of this work have already served as the basic foundation for the system architectures of several projects proposed by Blue Line for different missions and customers. These include the NMSD and AMSD procurements for NASA's Next Generation Space Telescope, the HET figure maintenance system, and the 1 meter FAST telescope project.

Ames, Gregory H.↗
NASA NTRS1998

Weather Avoidance Using Route Optimization as a Decision Aid: An AWIN Topical Study

The aviation community is faced with reducing the fatal aircraft accident rate by 80 percent within 10 years. This must be achieved even with ever increasing, traffic and a changing National Airspace System. This is not just an altruistic goal, but a real necessity, if our growing level of commerce is to continue. Honeywell Technology Center's topical study, "Weather Avoidance Using Route Optimization as a Decision Aid", addresses these pressing needs. The goal of this program is to use route optimization and user interface technologies to develop a prototype decision aid for dispatchers and pilots. This decision aid will suggest possible diversions through single or multiple weather hazards and present weather information with a human-centered design. At the conclusion of the program, we will have a laptop prototype decision aid that will be used to demonstrate concepts to industry for integration into commercialized products for dispatchers and/or pilots. With weather a factor in 30% of aircraft accidents, our program will prevent accidents by strategically avoiding weather hazards in flight. By supplying more relevant weather information in a human-centered format along with the tools to generate flight plans around weather, aircraft exposure to weather hazards can be reduced. Our program directly addresses the NASA's five year investment areas of Strategic Weather Information and Weather Operations (simulation/hazard characterization and crew/dispatch/ATChazard monitoring, display, and decision support) (NASA Aeronautics Safety Investment Strategy: Weather Investment Recommendations, April 15, 1997). This program is comprised of two phases, Phase I concluded December 31, 1998. This first phase defined weather data requirements, lateral routing algorithms, an conceptual displays for a user-centered design. Phase II runs from January 1999 through September 1999. The second phase integrates vertical routing into the lateral optimizer and combines the user interface into a prototype software testbed. Phase II concludes with a dispatcher and pilot evaluation of the route optimizer decision aid. This document describes work completed in Phase I in contract with NASA Langley August 1998 - December 1998. This report includes: (1) Discuss how weather hazards were identified in partnership with experts, and how weather hazards were prioritized; (2) Static representations of display layouts for integrated planning function (3) Cost function for the 2D route optimizer; (4) Discussion of the method for obtaining, access to raw data of, and the results of the flight deck user information requirements definition; (5) Itemized display format requirements identified for representing weather hazards in a route planning aid.

Source record↗
NASA NTRS2018

Tactical Surface Metering Procedures for Charlotte Douglas International Airport

NASA has been collaborating with the Federal Aviation Administration (FAA) and aviation industry partners to develop and demonstrate new concepts and technologies for the Integrated Arrival, Departure, and Surface (IADS) traffic management capabilities under the Airspace Technology Demonstration 2 (ATD-2) project. The primary goal of the ATD-2 project is to improve the predictability and the operational efficiency of the air traffic system in metroplex environments while maintaining or improving throughput by enhancing and integrating arrival, departure and surface prediction, scheduling, and management systems. In the Phase 1 Baseline IADS Demonstration, the tactical surface scheduling capability and the user interfaces for ramp controllers and ramp traffic managers were implemented for ramp operations. The purpose of the tactical surface scheduling capability is to provide the airline ramp controller with aircraft pushback advisories that prevent surface congestion and to respond to surface and airspace constraints that become known over relatively short time horizons. For this purpose, the tactical surface metering tool first estimates the capacity of current and near-future runway resources from flight schedule and surveillance data. With demand forecasts and predicted taxi trajectories, this tool computes an efficient runway schedule of aircraft in the planning horizon based on their readiness, Earliest Off-Block Times (EOBTs), and a ration by schedule (RBS) rule. Details on the implementation of the Tactical Surface Metering tool will be provided in the full paper. Both pushback and recommended hold times advisories provided by this surface metering tool are shown on the user interfaces for the ramp controller and the ramp traffic manager, called Ramp Traffic Console (RTC) and Ramp Manager Traffic Console (RMTC), respectively. There is excess queue time in the system due to demand capacity imbalance, this time can be taken as a hold on the runway queue or at the gate and was referred to as the Metering Value. This metering value can be adjusted by the Ramp Manager in collaboration with Air Traffic Controller-Tower Traffic Management Coordinator (TMC). They selected a set of metering values as default values for the tool during human-in-the-loop simulation. As the metering value increases, there is a decrease in the gate hold and increase in the queue time at the runway. Procedures and Information needs related to managing the surface metering procedures were researched in the simulated environment. These procedures will be compared to the procedures adopted at Charlotte Douglas International Airport when the tools were deployed and adopted in November 2017 for one departure push bank per day. Feedback regarding initial issues, information needs such as the need to see EOBTs on the flight data tags and how they compare to scheduled times will also be discussed in the full paper. Initial results will be provided regarding the choice of the metering value and how it was adjusted on a daily basis and what procedures evolved will also be presented in the paper.

surface metering↗
NASA NTRS1996

Air Traffic Complexity Measurement Environment (ACME): Software User's Guide

A user's guide for the Air Traffic Complexity Measurement Environment (ACME) software is presented. The ACME consists of two major components, a complexity analysis tool and user interface. The Complexity Analysis Tool (CAT) analyzes complexity off-line, producing data files which may be examined interactively via the Complexity Data Analysis Tool (CDAT). The Complexity Analysis Tool is composed of three independently executing processes that communicate via PVM (Parallel Virtual Machine) and Unix sockets. The Runtime Data Management and Control process (RUNDMC) extracts flight plan and track information from a SAR input file, and sends the information to GARP (Generate Aircraft Routes Process) and CAT (Complexity Analysis Task). GARP in turn generates aircraft trajectories, which are utilized by CAT to calculate sector complexity. CAT writes flight plan, track and complexity data to an output file, which can be examined interactively. The Complexity Data Analysis Tool (CDAT) provides an interactive graphic environment for examining the complexity data produced by the Complexity Analysis Tool (CAT). CDAT can also play back track data extracted from System Analysis Recording (SAR) tapes. The CDAT user interface consists of a primary window, a controls window, and miscellaneous pop-ups. Aircraft track and position data is displayed in the main viewing area of the primary window. The controls window contains miscellaneous control and display items. Complexity data is displayed in pop-up windows. CDAT plays back sector complexity and aircraft track and position data as a function of time. Controls are provided to start and stop playback, adjust the playback rate, and reposition the display to a specified time.

Source record↗