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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 469 records · Page 26

All sources NASA NTRS DOE OSTI

DOE OSTI2021

Bioinformatic teaching resources - for educators, by educators - using KBase, a free, user-friendly, open source platform

Over the past year, biology educators and staff at the Department of Energy Systems Biology Knowledgebase (KBase) initiated a collaborative effort to develop a curriculum for bioinformatics education. KBase is a free and easily accessible data science platform that integrates many bioinformatics resources into a graphical user interface built upon reproducible analysis notebooks. KBase held conversations with college and high school instructors to understand how KBase could potentially support their educational goals. These conversations morphed into a working group of biological and data science instructors that adapted the KBase platform to their curriculum needs, specifically around concepts in Genomics, Metagenomics, Pangenomics, and Phylogenetics. The KBase Educators Working Group developed modular, adaptable, and customizable instructional units. Each instructional module contains teaching resources, publicly available data, analysis tools, and markdown capability to tailor instructions and learning goals for each class. The online user interface enables students to conduct hands-on data science research and analyses without requiring programming skills or their own computational resources (these are provided by KBase). Alongside these resources, KBase continues to work with instructors, supporting the development of additional curriculum modules. For anyone new to the platform, KBase, and the growing KBase Educators Organization, provides a community network, accompanied by community-sourced guidelines, instructional templates, and peer support to use KBase within a classroom whether virtual or in-person.

59 BASIC BIOLOGICAL SCIENCES↗

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.↗

DOE OSTI2025

Automated qualification data tool for high temperature metallic materials

This report describes a framework for storing, processing, and displaying qualification data for high temperature mechanical properties. The framework automates the process of generating design data from mechanical test results, for example for a data qualification report for the ASME Boiler \& Pressure Vessel Code. The framework has three parts: a data storage model with common formats for several types of typical mechanical property tests, a backend based on the \pycreep Python library for correlating and extrapolating the data to generate design material properties and allowable stresses, and a demonstration user interface for displaying, sorting, and filtering the data and exploring different options for modeling the design mechanical properties. The report discusses the options available for data processing, with illustrations from real test data on Alloy 617, Alloy 709, Alloy 740H, and Laser-Powder Bed Fusion 316H. The framework is complete for ASME type data analysis and will be used to store test data generated by the Department of Energy, Office of Nuclear Energy, Advanced Materials and Manufacturing Technologies sponsored qualification programs. Future work could extend the tool to other types of material properties and/or expand the demo user interface to make it accessible across the AMMT program.

36 MATERIALS SCIENCE↗

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.↗

DOE OSTI2022

The waterSHED Model: User Guide

The ideal design and operation of small hydropower plants is a complex optimization problem with economic, social, and environmental objectives. The waterSHED (Water Allocation Tool Enabling Rapid Small Hydropower Environmental Design) model is a user-friendly tool that allows hydropower stakeholders to model the trade-offs among these objectives using the Standard Modular Hydropower (SMH) framework. The SMH framework employs modular technologies that can be represented as blackbox objects and combined within a river to create a hydropower facility. For a given site, the waterSHED model aims to determine which modules should be placed in a facility and how those modules should be operated. This user guide describes how to use the graphical user interface and related functionalities. This document also summarizes the background research and mathematical formulations that are explained indepth in the accompanying doctoral dissertation. This model is an early step toward a new hydropower design process that employs standardization and modularity to reduce costs, development timelines, and challenges regarding social and environmental mitigation measures for low-head, small hydropower development. The waterSHED model is a Python application that will require the ability to download a GitHub repository, import the necessary packages, and run a set of Python script files using an integrated development environment. The script produces a graphical user interface to coordinate inputs, simulate operation, and visualize results, so no coding experience is needed once the script is running. Additionally, the waterSHED Workbook is a Microsoft Excel file that works with the Python script to facilitate data entry

13 HYDRO ENERGY↗

DOE OSTI2025

Modern control system applications at Fermilab with Dart and Flutter

The control system at Fermilab is undergoing an unprecedented modernization effort. Hundreds of legacy applications originally developed with technology from the early nineties will be replaced with a suite of modern web applications. The selection of an user interface framework is a key technology decision that will impact on all the applications developed over the next decade. The Controls department at Fermilab has decided to use Google’s Dart language and Flutter framework for future application development. In this paper we will discuss the decision process that selected Dart/Flutter and the development of early general purpose control system applications with the framework.

Diamond, John [Fermilab]↗

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.↗

DOE OSTI2024

Collection And Analysis Of Telemetry For The Cyote Heuristic

CATCH CLI focuses on gathering telemetry data, storing it in the Neo4j database, querying for Mitre ATT&CK patterns, and creating STIX 2.1 reports. Key Components: Analysis Modules: Analyze data to detect attack patterns. GoSTOTS Collection Engines: Collect telemetry data. These tools can be used together or individually. Analysis modules rely on data from specific engines to identify attack patterns. Source Code Organization: Engines: CATCH/catch/cmd/collection Modules: CATCH/catch/cmd/analysis CGUI Overview CATCH Graphical User Interface (CGUI) offers a graphical shell to execute CATCH CLI, allowing easy editing of: Analysis Modules Database configurations Profiles (collection and device settings) Neo4j Overview Neo4j is a graph database using the Cypher query language, storing data in JSON. It seamlessly integrates with STIX 2.1 data for: Data Submission: CATCH Collection Engines Data Querying: Analysis Modules CATCH modifies STIX 2.1 data for Neo4j submission and reverts it back during querying. STIG Overview Structured Threat Intelligence Graph (STIG) is a tool for creating, editing, querying, analyzing, and visualizing threat intelligence using STIX 2.1 and storing data in Neo4j. Usage Tools can be run: Manually (CLI): Refer to CATCH documentation User Interface: Run ./cgui/CGUI or go run ./cgui/ Additional Information Logging System: Detailed in the config documentation Further Documentation: Available for CATCH and CGUI

Madsen, MichaelJ. [Idaho National Laboratory (INL)↗

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↗

DOE OSTI2020

FASTSim™ (Future Automotive Systems Technology Simulator) [SWR-20-101 and SWR-12-07]

The Future Automotive Systems Technology Simulator (FASTSim™) provides a simple way to compare powertrains and estimate the impact of technology improvements on light-, medium-, and heavy-duty vehicle efficiency, performance, cost, and battery life. This extremely fast simulation tool features a streamlined user interface and can rapidly perform a variety of tasks using basic computing resources: • less than 0.1 second to simulate second-by-second standard duty cycles • less than 10 seconds to estimate vehicle efficiency, fuel economy, acceleration, battery life, and cost • less than 5 minutes to perform powertrain comparisons of efficiency and cost. FASTSim models a variety of vehicle powertrains and fuel converter types: • Conventional vehicles - spark ignition, Atkinson, diesel, and hybrid diesel • Electric-drive vehicles - hybrid, plug-in hybrid, and all-electric • Hydrogen fuel cell vehicles. The default model includes a variety of vehicles and duty cycles and an option for adding additional vehicles and custom cycles: • Packaged with more than 20 vehicles • User interface enables addition of more vehicles • Includes standard U.S. drive cycles as well as European and Japanese cycles. FASTSim is available for download in Microsoft Excel and Python formats here: https://www.nrel.gov/transportation/fastsim.html

Baker, Chad↗

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↗

DOE OSTI2022

Upgrade of Core Conduction Cooldown Test Facility Control System

The CCCTF was designed and installed at ORNL in the 1990s for high-temperature gas-cooled reactor accident simulation. It is located within a modular hot cell housed in the IFEL facility. In 2008 and 2009, modifications were made to the CCCTF in preparation for AGR safety testing. A new airlock was designed and installed to better support periodic exchange of the fission product deposition cups while maintaining the fuel at safety test temperature, and modifications were made to add routines to the existing user interface software for computer-controlled automation of the He sweep gas flow and liquid nitrogen supply to the 85Kr cold traps. However, the furnace control hardware and software remained essentially unchanged. At the conclusion of the AGR-1 and AGR-2 PIE campaigns, continued use of the CCCTF was in question because of the gradual obsolescence of the hardware and software used to control the furnace and ancillary systems that make up the CCCTF. Therefore, an effort was undertaken to replace all the obsolete components with new hardware and update the software to increase system reliability and ensure this capability’s maintenance for future research and fuel qualification efforts. The modifications included creating a new National Instruments (NI) LabVIEW-based control system with a graphical user interface (GUI).

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

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↗

NASA NTRS1990

Space Station module Power Management And Distribution (PMAD) system

This project consists of several tasks which are unified toward experimentally demonstrating the operation of a highly autonomous, user-supportive power management and distribution system for Space Station Freedom (SSF) habitation/laboratory modules. This goal will be extended to a demonstration of autonomous, cooperative power system operation for the whole SSF power system through a joint effort with NASA's Lewis Research Center, using their Autonomous Power System. Short term goals for the space station module power management and distribution include having an operational breadboard reflecting current plans for SSF, improving performance of the system communications, and improving the organization and mutability of the artificial intelligence (AI) systems. In the middle term, intermediate levels of autonomy will be added, user interfaces will be modified, and enhanced modeling capabilities will be integrated in the system. Long term goals involve conversion of all software into Ada, vigorous verification and validation efforts and, finally, seeing an impact of this research on the operation of SSF. Conversion of the system to a DC Star configuration is now in progress, and should be completed by the end of October, 1989. This configuration reflects the latest SSF module architecture. Hardware is now being procured which will improve system communications significantly. The Knowledge-Based Management System (KBMS) is initially developed and the rules from FRAMES have been implemented in the KBMS. Rules in the other two AI systems are also being grouped modularly, making them more tractable, and easier to eventually move into the KBMS. Adding an intermediate level of autonomy will require development of a planning utility, which will also be built using the KBMS. These changes will require having the user interface for the whole system available from one interface. An Enhanced Model will be developed, which will allow exercise of the system through the interface without requiring all of the power hardware to be operational. The functionality of the AI systems will continue to be advanced, including incipient failure detection. Ada conversion will begin with the lowest level processor (LLP) code. Then selected pieces of the higher level functionality will be recorded in Ada and, where possible, moved to the LLP level. Validation and verification will be done on the Ada code, and will complete sometimes after completion of the Ada conversion.

Walls, Bryan↗